Integrate Callingly With Brivity
Callingly automatically connects to your Brivity account, allowing you to instantly trigger calls when new leads come in. The call results and recordings are then synced back to Brivity.
Owners and Admins can set up integrations. Approx. reading time 5 min.
Connect Callingly to Brivity
- 1.
- Navigate to the New Integration page.
- 2.
- Click Connect next to Brivity.
- 3.
-
Paste your Brivity API key.
Note: To get your API key, log in to Brivity and go to Settings > API. If you don't see it, ask Brivity support to turn on API access for your account. - 4.
- Click Install. Callingly sets up a webhook in Brivity to receive your new leads.
Choose Settings
Open the integration from the Integrations page. Its Settings tab has these options:
Name
The integration's name in Callingly.
Sync Lead Owner
When Callingly assigns the lead to a user, set the same owner in Brivity. Each user must be matched to their Brivity user (see below).
Sync Calls
Log each of your reps' calls with a lead in Brivity.
What starts a call: a new lead in Brivity. Brivity sends each new lead to Callingly, and your routing rules decide which team calls it.
Two more tabs finish the setup:
- Routing decides which team calls each lead, and which sequence it follows. See Understanding Call Routing.
- Fields matches Brivity fields to Callingly's lead fields, including your own custom fields.
Sync Lead Owner
With Sync Lead Owner on, match each Callingly user to their Brivity user:
- 1.
- Go to the Users page and click Edit next to the user.
- 2.
- Under Integrations, pick their account in the Brivity User dropdown.
- 3.
- Save, and repeat for each user.
How It Works
When a new lead comes into Brivity, the following happens automatically:
- Brivity sends the lead information to Callingly via webhook
- Callingly checks the routing rules to determine which team should receive the call
- Your AI Agent calls the lead, asks any qualifying questions you've set, and warm-transfers the lead to one of your team members while the lead is still on the line, or offers a callback if nobody's free.
- When a team member talks with the lead, that call is logged back to Brivity (if Sync Calls is enabled)
- If lead ownership changes in Callingly, it's synced back to Brivity (if Sync Lead Owner is enabled)
Next Steps
- Test the integration. During your team's call hours, create a test lead in Brivity with a phone number that isn't one of your users' numbers. Have a rep ready to take the transfer, then answer the AI's call like an interested lead.
- Configure your Teams. Set up your Callingly Teams so the right people receive calls for different lead sources.
- Set the Call Schedule. Configure your availability schedule so nobody receives calls outside of work hours.
Common Questions
How do leads get from Brivity to Callingly?
When you install the integration, Callingly automatically creates a webhook in Brivity. Whenever a new lead is created in Brivity, it's automatically sent to Callingly.
Can I route different lead sources to different teams?
Yes! Use the Routing tab in your integration's settings to route leads based on their source in Brivity. Each source can be directed to a different team.
Do call recordings sync back to Brivity?
Yes, when you enable "Sync Calls", Callingly creates a call event in Brivity that includes a link to the call recording.
Why does a lead show as disconnected from Brivity?
When Callingly tries to sync a lead back to Brivity and Brivity no longer has a matching contact record (for example, a contact was deleted in Brivity), Callingly automatically disconnects the lead from the CRM and logs a crm_disconnected activity on the lead. This prevents repeated sync errors.
To reconnect the lead, recreate the contact in Brivity, then email support@callingly.com to link it to the lead in Callingly again.
Callingly also handles the case where a lead's email in Callingly has drifted from the email on file in Brivity (e.g. a typo at lead creation). In that situation, Callingly automatically re-syncs the lead's email from Brivity so future updates go through correctly — no action is needed on your part.