Bonzo
Aila reads calls made in Bonzo and writes notes, tasks, stage moves, and tags back to the prospect. The writes are part of the Intake Agent.
What syncs
| Direction | What |
|---|---|
| Bonzo to Aila | Call messages and their recordings, sent by Bonzo event hooks. |
| Aila to Bonzo | Call summary as a note. Full transcript as a note, if you turn it on. A follow-up task. Custom field values. Pipeline stage moves. Prospect tags. Appointments from your appointment rules. |
What you need
- A Bonzo API key. Create it in Bonzo with these permissions: Messaging, Conversations, Prospects, Public access, and Authenticated access.
- Access to Settings > Integrations > Event Hooks in Bonzo.
Connect
- In Aila, go to Settings > Connections and click Connect.
- Select Bonzo.
- Paste your Bonzo API Key and click Connect.
- Open the connection's settings and copy the Webhook URL.
- In Bonzo, go to Settings > Integrations > Event Hooks and click New event hook. Paste the URL and subscribe to: Messages incoming, Messages outgoing, Messages outgoing updated, Task created, Task updated, Prospect notes created, Prospect notes updated, and Prospect notes deleted.
Settings
| Setting | Options | Default | What it does |
|---|---|---|---|
| Call Summary | In Notes, Off | In Notes | Posts the call summary as a Bonzo note. |
| Post Transcript | Off, In Notes | Off | Posts the full transcript as a note. |
| Create Follow-up Task | On, Off | Off | Creates one follow-up task after each processed call. |
Field mapping
- Custom Field Mapping maps extracted data to Bonzo custom fields.
- Pipeline stage rules move the prospect to a stage when an extracted value matches your rule.
- Tag rules add a tag when an extracted value matches your rule.
How calls are matched
Bonzo includes the prospect and the Bonzo user on each call event. Aila links the call to that prospect and to the Aila user with the same email as the Bonzo user.
Troubleshooting
- No calls arrive: Check that the event hook uses the exact Webhook URL from the connection and subscribes to all eight events above.
- The connection fails: Check that the API key has the five permissions listed above.