Once your Telavox integration is connected, Garba automatically processes your phone calls — transcribing and summarizing them without any manual work. Here's how it all works.
When a call ends in Telavox, Garba picks it up on its next check and runs it through the full pipeline:
Call ends in Telavox with a recording
Garba checks for new recordings every 5 minutes
Recording is downloaded and transcribed using AI
AI summary is generated based on your configured templates
Email notification is sent to the user (if enabled)
[Image: garba-meeting-from-telavox-call — A Garba meeting record created from a Telavox call, with the recording, participants, and AI summary.]
Calls appear in Garba as meeting records with the title "Incoming call from [number]" or "Outgoing call to [number]". If the number matches a contact in your connected CRM, the contact's name is used instead.
Garba imports calls that meet these criteria:
The call was answered and has a recording — a call that goes to voicemail is never recorded and never reaches Garba
The Telavox user has the Recorded calls add-on active in Telavox
The Telavox user's email matches a Garba user with a Recording license
Both incoming and outgoing calls are imported. Unanswered and unrecorded calls are automatically skipped.
Every imported call gets an AI-generated summary, just like your video meetings, following your account's settings for calls. You can customize the summary template under Setup > Meeting Summaries to tailor the output to your workflow — whether that's a sales discovery format, support ticket summary, or general meeting notes.
[Image: garba-telavox-call-summary — An AI-generated summary of a Telavox call, with executive summary, action items, key takeaways, and topics.]
After each call is processed, the user who made or received the call gets an email with the summary and key takeaways, if your account's call settings enable it. Each user controls this in their own notification settings:
Go to Setup > Notification Settings
Under Post-Meeting Summary Notifications, select Call under Meeting sources.
[Image: garba-notification-settings-call-source — The Notification Settings page with Call selected in the Meeting sources group.]
This setting applies to calls from all connected phone integrations (Telavox, Lynes, Aircall, HubSpot calls).
Garba matches Telavox users to Garba users by email address. For calls to be attributed to the correct person, the user's email in Telavox must match their email in Garba.
If a user's email doesn't match any Garba user, or the matching Garba user has no Recording license, the call is stored but not turned into a meeting. As soon as the match is fixed, the call is picked up and processed.
Here's what Garba captures from each Telavox call:
Field | Description |
|---|---|
Title | "Incoming call from [number]" or "Outgoing call to [number]" |
Direction | Inbound or outbound |
Duration | Length of the call |
User | The Garba user matched by email |
Recording | Full audio recording |
Transcript | AI-generated transcription |
Summary | AI-generated summary using your templates |
Source | Marked as "Telavox" |
Participants | External phone number(s) on the call |
Why isn't my call showing up in Garba?
Check that the call was answered and recorded in Telavox (the Recorded calls add-on must be active for that user), that the Telavox user's email matches a Garba user, and that the Garba user has a Recording license.
Can I choose which calls get imported?
All recorded calls from Telavox users with the Recorded calls add-on are imported automatically. There is no per-call toggle — if the integration is connected and the user's email matches a Garba user with a Recording license, their calls will be processed.
How far back does the initial import go?
When you first connect, Garba imports up to 30 days of recent recorded calls.
Why does a call show a phone number instead of a name?
Garba shows the contact's name when the number matches a contact in your connected CRM. If there's no match, the bare phone number is shown instead.
What happens if I disconnect and reconnect?
Previously imported calls remain in Garba. After reconnecting with a new token, new calls resume importing.
If you have any questions, feel free to reach out to our support team!
