Posted as the call ends
The same summary that goes out by text and email is posted into Teams through a Power Automate flow the business sets up once. New enquiry, booking made, urgent call, message taken: each arrives as the call finishes.
Microsoft Teams
The call lands where the team already is.
A business that runs on Teams finds out about phone calls by walking past the front desk. Two things change that: every call the agent takes can be posted into a Teams channel the moment it ends, available now, and a meeting agent that joins a Teams meeting from the calendar and takes the notes, in early access.
Call notifications into Teams are available now and included with every agent. The meeting agent is in early access and is not yet switched on for clients.
Available now
Call notifications in a Teams channel
Within seconds of a call ending, a post in the channel the business chooses: who rang, what they wanted, what the agent did. The team reads it where it already reads everything else.
Routing in plain English
Per destination, the business writes what should go where: urgent calls to the on-call channel, bookings to the front desk channel, everything else to a general one. Slack and any webhook take the same routing.
Posts only, reads nothing back
The platform writes into the channel and never reads it. Nothing in Teams is read by the agent, and a reply in the channel does not reach the caller. Replies to a customer are the job of the phone or texting agent.
Early access
A meeting agent that joins the Teams meeting and takes the notes
The same agent that answers the phone can sit in a meeting. It joins from a connected Microsoft 365 calendar, takes notes, and files the transcript, recording and summary on the matching lead.
Joins from the calendar
A meeting on the connected Microsoft 365 calendar with a Teams link is enough. The agent joins from the calendar entry; nobody has to add it to the meeting by hand.
Notes, summary and recording filed
After the meeting the transcript, recording and summary are filed on the matched lead, next to the calls and texts for the same person, so the whole relationship reads in one place.
Answers when spoken to
Addressed by name, the agent answers from the same knowledge base as the phone agent. Otherwise it listens. Anything beyond that is still being tested and is not promised.
Stated plainly
- The meeting agent is early access. It is built and in testing with the platform's own team, and it is not yet switched on for clients or on sale. Sell it as a conversation for later, not a feature for today.
- Meetings are not covered by the data-centre statement that applies to calls. Calls, transcription and recordings are handled in New Zealand and Australian data centres and nowhere else; a Teams meeting the agent joins is processed differently, and a client who needs that residency should not be offered the meeting agent until that changes.
- It is Microsoft Teams only, from a Microsoft 365 calendar connected to the platform.
How it goes for the team
A call at 10.14, read in Teams at 10.15
- The agent takes a call. A customer books a service for Thursday. The agent writes it into the diary and texts the customer a confirmation.
- The summary is posted. The routing says bookings go to the front desk channel, so the post appears there: who, what, Thursday at ten, with a link to the call on the dashboard.
- An urgent call goes elsewhere. A fault report after hours matches the urgent rule and lands in the on-call channel, alongside the escalation ladder that is already ringing somebody.
- Nothing comes back. A teammate who replies in the channel is talking to the team, not the caller. The record stays on the dashboard, and the channel stays a feed.
Sold through partners
For the clients whose Microsoft 365 you already run
If you manage a client's Microsoft 365, call notifications into Teams are a one-off flow you can set up for them, and the Microsoft 365 calendar connection that books appointments is the same one the meeting agent will use. Sold through partners: you set the price, Talkgate runs the platform. Notifications are included with every agent. The meeting agent is early access and is described that way, every time. See the partner programme.
Works with
Teams, the calendar behind it, and the other places a call can be posted
Direct connections, built and run by Talkgate. See all integrations.
Next step
See a call summary land in a Teams channel
A partner briefing shows the routing being written and the post arriving, and is straight about where the meeting agent is up to. See also call records.