Connecting a call recorder
Connect the platform that records your calls and Kai starts learning from what prospects actually say, not just from what your team sends. This is what turns on Market Intel, adds real conversations to Coaching Corner, and feeds the objections and language your buyers use back into the copy Kai writes.
Why connect one
Everything else Kai reads is outbound: what you sent, what was opened, what was replied to. A call recorder is the only source that carries what the buyer said in their own words, at length, unprompted. That is where the objection you keep losing on, the phrase that keeps landing, and the competitor nobody told you about actually live.
Once calls are flowing, three surfaces change:
- Market Intel appears in Reporting, merging what prospects said across every recorded call into themes you can rank and filter.
- Coaching Corner gains recorded calls as a work type, so a manager can coach the conversation, not just the email.
- What Kai writes improves, because real objections and real language become part of the evidence it draws on.
Supported platforms
Six, in two modes. Pull means Kai calls the platform on a schedule. Push means the platform calls Kai when a transcript is ready.
| Platform | Mode | What it takes to get access |
|---|---|---|
| Zoom | Pull | Comes with your Zoom account, nothing to buy. Create a Server-to-Server OAuth app and grant it the meeting transcript and summary scopes. |
| Gong | Pull | The API is a paid add-on module, not part of the base subscription, typically quoted around $10-30k a year. If your API settings screen has no keys on it, that is why, and it is a conversation with your Gong rep. |
| Microsoft Teams | Pull | Needs an app registration with admin consent. Transcript export is application-permission only, so a normal sign-in cannot read them. Your tenant admin can also switch Graph access to transcripts off entirely. |
| Chorus by ZoomInfo | Pull | Token is issued per user in Personal Settings and inherits that user's visibility, so connect it with an account that can see the calls you care about. |
| Airspeed | Pull | Enterprise plans only. The key it issues can read every non-private call in the organisation; there is no narrower scope to grant, so use Kai's call scoping to limit what is stored. |
| Fireflies | Push | Business plan or above. Nothing to poll, but you do need to point Fireflies' webhook at Kai and set a webhook secret. |
Connecting one
For Fireflies, there is one extra step: set the same webhook secret in Fireflies' own webhook settings. Until that value is set on both sides, Kai rejects incoming webhooks rather than trusting an unsigned payload. An unauthenticated endpoint would let a stranger write calls into your conversation history, which then feeds your themes and your campaign arguments.
Choosing which calls Kai reads
Scope is set per connection, not per workspace. That matters if you run Gong for the enterprise AEs and Zoom for the SDR team: those two want genuinely different scopes, and they get them.
The defaults
Out of the box, scope is permissive but not total: all users, all external calls, internal-only meetings excluded, and anything under two minutes excluded. That gives real coverage on day one without ingesting every standup and every no-show.
What you can change
- Only calls after a date. Useful for a backfill you want bounded, or for skipping a period before your positioning changed.
- Longer than a duration. Raise it if two-minute connects are noise for you.
- Attendees. Three settings: someone outside the company was on it, a contact Kai already knows was on it, or every call including internal.
- These people. Either an allowlist of users whose calls to pull, or a blocklist of users to skip.
- Skip titles containing a word. The cheapest way to drop recurring internal meetings by name.
A note on attendee lists
Zoom and Microsoft Teams do not return a real attendee roster; they name the host or organiser and little else. Kai knows this and does not apply the attendee rules to those two, because a call that structurally cannot report who was on it looks exactly like an internal-only meeting. If it judged them on the roster, every call from those platforms would be dropped with a reason that read like the filter working correctly. For Zoom and Teams, use the title filter and the user allowlist instead.
Backfilling history
Every supported platform can backfill. How far depends on the platform: Zoom is limited by your cloud recording retention, which varies by account, and the rest generally reach back about a year.
Backfill is worth doing before you look at Market Intel for the first time. Themes are ranked by how much supports them, so a week of calls produces a thin and slightly misleading picture. A quarter produces something you can act on.
Checking it worked
- The connection shows as Connected in Settings, not just saved.
- A sync has run, and the connection reports when it last ran.
- Market Intel has appeared under Reporting.
- Coaching Corner shows calls when you filter the work type to calls.
If the connection is live but nothing has arrived, the scope is the first place to look, and the attendee rule is the usual culprit. Widen it to "every call, including internal", sync again, and narrow back down once you can see what is being matched.
Privacy and what to tell your team
Kai reads transcripts your recording platform has already produced. It does not join calls, does not record anything itself, and cannot see a call your platform did not record. Consent and recording notices remain your platform's job and your legal team's call.
That said, "the AI reads our calls now" is a sentence worth saying out loud to a sales team rather than letting them discover it. The scope controls exist partly so you can give a precise answer: which calls, from which people, from which date.