Guided setup.
Our team connects it with you, usually within 1-2 business days. Connect opens a short form: what you want it to do, the
best time to reach you, and who your Jira Service Management admin is. We schedule the setup with you, test it
on your account, and then turn it on for callers.
Setup steps
- Choose Connect. A short guided-setup form opens, and our team takes it from there.
- Tell us the service project and request type voicemails should go to.
- On a short call we build the Zap with you, signed in to your own Zapier and Atlassian accounts.
- We leave a test voicemail, check the request, and confirm on your ticket.
What the AI can do
- Nothing changes on the call: Jira gets the details after the call or voicemail.
- Each request carries the caller's number, the time and, for voicemail, the transcript.
What it can't do, and limits
- Guided setup: our team connects it with you and tests it on your account before callers rely on it.
- We connect it through Zapier, using the same signed events as our webhooks. Your Zapier plan's task limits apply.
- Requests are created after the call. Callers can't hear a request's status on the phone with this setup.
Troubleshooting
Who is the reporter on the request?
The account the Zap connects with, unless you'd like us to match callers to customers by phone number first.
Does it work on the Phone package?
Yes. Requests only need our call events, which every package has.
Disconnecting, and the data we keep
An owner or admin can disconnect at any time from Phone, then Connectors, in the app. Disconnecting stops TimberSwitch using Jira Service Management straight away.
- The Zapier subscription that feeds Jira, stored like any webhook.
- A delivery log for each event: time, event type and response code.
- Turning the Zap off stops new requests straight away.
Still stuck?
Get help: it opens an Integration support ticket. Include the time of the call and what you expected to happen.
Atlassian is a trademark of its owner; TimberSwitch is not affiliated.