Joins from the calendar
A meeting on a connected calendar with a Teams, Google Meet or Zoom link is enough. The agent joins from the calendar entry; nobody has to add it by hand.
Meetings
The meeting ends with the notes already sent.
The agent that answers your clients' phones also joins their meetings in Microsoft Teams, Google Meet and Zoom. It takes the notes, sends the actions, and files the lot next to the calls and texts for the same person.
Every call the agent takes can also be posted into a Microsoft Teams or Slack channel as it ends, included with every agent.
Meeting agent
Joins the meeting, takes the notes, sends the actions
Microsoft Teams, Google Meet or Zoom: the agent joins from the meeting on a connected calendar, listens, and writes up what was agreed and who is doing what.
Notes and actions sent
When the meeting ends, the notes and the actions go out, and the transcript, recording and summary are filed on the matched lead, next to the calls and texts for the same person.
Answers when spoken to
Addressed by name, the agent answers from the same knowledge base as the phone agent. Otherwise it listens and takes the notes.
Stated plainly
- Meetings are not covered by the data-centre statement that applies to calls. A client who needs that residency for meetings should talk it through in the briefing before the meeting agent is switched on.
- It joins meetings in Microsoft Teams, Google Meet and Zoom, from a calendar connected to the platform.
Call notifications
Every call posted into a Teams or Slack channel
Within seconds of a call ending, a post in the channel the business chooses: who rang, what they wanted, what the agent did, where the team already reads everything else.
Posted as it ends
The same summary that goes out by text and email is posted into Microsoft Teams through a Power Automate flow the business sets up once. New enquiry, booking made, urgent call, message taken.
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 webhooks take the same routing.
Posts only, reads nothing
The platform writes into the channel and never reads it. A reply in the channel does not reach the caller; replies to a customer are the job of the phone or texting agent.
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. Bookings go to the front desk channel, so the post appears there: who, what, Thursday at ten.
- An urgent call goes elsewhere. A fault after hours matches the urgent rule and lands in the on-call channel while the escalation ladder rings.
- Nothing comes back. A teammate who replies in the channel is talking to the team, not the caller. The record stays on the dashboard.
Sold through partners
For the clients whose meetings and Microsoft 365 you already look after
The meeting agent is the same agent your client already has on the phone, so the notes and actions from a meeting sit beside every call from the same person. If you manage a client's Microsoft 365, call notifications into Teams are a one-off flow you can set up for them. You set the price; Talkgate runs the platform, and notifications are included with every agent. See the partner programme.
Works with
The meeting rooms, the calendars behind them, and the places a call can be posted
Direct connections, built and run by Talkgate. See all integrations.
- Microsoft Teams
- Google Meet
- Zoom
- Microsoft 365
- Google Calendar
- Slack
- Webhooks
Next step
See a meeting written up and a call land in a channel
A partner briefing shows the agent in a meeting, the notes and actions it sends afterwards, and a call summary arriving in a Teams channel. See also call records.