A sponsor books a slot, the call happens, the transcript is summarised, and the action items are on the timeline before anyone opens a notes app. Every step lands on the contact's timeline, next to the emails.
CommsOperator gives each workspace public booking pages backed by Outlook calendars, with collective booking, approval flows, and email reminders. A meeting bot joins externally hosted calls to record and transcribe them; internally hosted Teams meetings use native transcripts, with no bot in the room. Calls, transcripts, participants, and AI summaries land on the contact's timeline with the action items already extracted. Google Calendar is not supported.
Send one link instead of five emails about availability. Public booking pages per workspace read free slots from Outlook, find a time everyone on the invite is free for, and can hold the booking for your approval before it is confirmed.
Fewer no-shows without a person chasing. Confirmations and reminders go out by email, with time zones handled on the server so nobody shows up an hour early.
A bot joins the external call and writes the summary onto the contact's timeline. You decide, per workspace, which meetings it may join, and its webhooks are signature-verified so nothing forged reaches your records.
Internal calls are transcribed without a bot in the room. Native Microsoft Teams transcripts are pulled through Microsoft Graph for internally hosted meetings.
Walk out of the call with the follow-up already written. AI summaries, participants, sentiment, action items, and next steps land on the CRM timeline.
Numbers from the production instance and behaviour checked against the code. No projections, no testimonials.
What this module does not do today, and what to do about it. If one of these is a blocker, you know before you commit, not after.
Only if you leave the rule open. Set the meeting-type rule to externally hosted calls and the bot stays out of internal meetings, which use native Teams transcripts instead.
For booking links on an Outlook calendar, including collective booking and approval before confirmation, yes, and the booking lands on the contact's timeline. There is no Google Calendar support, so a Google-first team should keep its current tool.
Tell us what you run and we will be straight about the fit. Private beta. A person reads every request.