Microsoft Teams setup and support

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 Microsoft Teams 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.
On a short call, your Microsoft 365 admin creates a Teams workflow that starts when a webhook request arrives and posts to the channel you pick.
We add the workflow's address on the Webhooks page in the app and pick the events you want.
We send a test call through, check the post in Teams, and confirm on your ticket.

What the AI can do

Nothing changes on the call: Teams gets the details after the call, voicemail or message.
Each post 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.
It uses a Teams workflow (Power Automate) that receives our signed webhooks. Someone who can create workflows in your Microsoft 365 tenant joins the setup call.
Posts are one-way. Replying in Teams doesn't call or text the caller back.
Microsoft retired the old Office 365 connectors in Teams, so we use workflows instead.

Troubleshooting

Do I need a paid Microsoft 365 plan?

You need Teams with workflows (Power Automate) turned on, which most Microsoft 365 business plans include. We check yours on the setup call.

Posts stopped arriving.

Check the workflow is still on in Teams and that its owner still has a license. If the workflow was recreated, its address changed: send us the new one or update it on the Webhooks page.

Does it work on the Phone package?

Yes. Teams posts 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 Microsoft Teams straight away.

The workflow's webhook address, stored like any webhook.
A delivery log for each event: time, event type and response code.
Removing the webhook stops the posts straight away.

Still stuck?

Get help: it opens an Integration support ticket. Include the time of the call and what you expected to happen.

Microsoft is a trademark of its owner; TimberSwitch is not affiliated.