Setup guide · BoondManager
Connect BoondManager to Bloom AI
From preparing BoondManager to your first synced calls: install the app, connect your team, then choose your rules.
Set up
Before you start
Two checks on each side, and most blockers are out of the way.
In Bloom AI
- You are an owner or an admin of the organization.
- The organization has a paid plan or an active trial.
In BoondManager
- A BoondManager administrator installs the Bloom app; a manager whose scope covers the whole team’s contacts and reps connects it.
- Your BoondManager database is not linked to any other Bloom AI organization.
BoondManager receives calls as actions on contacts. Meetings and contact creation are not supported.
Set up
Prepare BoondManager
Done in
BoondManager
An administrator prepares BoondManager once. Nothing else to create: no field, no property.
-
Install the Bloom app
In Administration › Apps / Marketplace, Marketplace tab, install the Bloom app. An installation code is requested? Our team provides it.
-
Enable the app for the connecting account’s role
In Administration › Managers / Roles › Roles, open the role of the account that will connect Bloom AI, enable Bloom in the Apps tab, then save. Without it, BoondManager refuses the authorization.
-
Keep an action type for calls
In Administration › Global settings › Contact actions, keep your calls’ type enabled (by default “Appel abouti”). You will pick it in Bloom AI; do not archive it afterwards.
An account that can see the whole team
Bloom AI acts with the connecting account’s permissions. Limited access may prevent finding contacts or assigning activities to the right rep.
Need help preparing your CRM?
Contact our team before connecting: they can help with installation and permissions.
Set up
Connect BoondManager
Done in
Bloom AI
BoondManager
Start in Bloom AI, then authorize access in BoondManager.
-
Open Integrations
Bloom AI
BoondManager
In your dashboard, open Integrations, then click Connect BoondManager.
-
Authorize Bloom AI
Bloom AI
BoondManager
BoondManager opens: sign in with the prepared account, review the requested access and accept.
-
Check the connection
Bloom AI
BoondManager
Back in Bloom AI, check the Connected status and the name of your BoondManager database.
-
Choose the action type
Bloom AI
BoondManager
The return page announces “one more step”: in the Action type card, pick the calls’ type, then save. Bloom AI picks it alone when exactly one enabled type is named “Call”. Until one is picked, calls wait without being lost.
-
Check your reps
Bloom AI
BoondManager
In Reps and BoondManager users, each rep is linked by email. Link by hand those still “Not linked”.
-
Choose your rules
Bloom AI
BoondManager
In Rules, choose what gets sent and how to handle missing information.
Only conversations supported by your CRM that happen after connecting are synced. Your history stays in Bloom AI.
Set up
Set your rules
Done in
Bloom AI
Available settings are in Rules in the Integrations section. Only owners and admins can change them.
-
Sync calls
Each answered call reaches the right record with its AI recap.
Default On
-
Also sync unanswered calls
Also keeps a trace of unanswered calls, under the same action type, if call sync is on.
Default Off
-
Rep not linked to BoondManager
Hold calls, or assign them to the account that connected BoondManager.
Default Hold
Who can pick a contact?
Owners and admins handle the whole queue. A rep can also pick the contact for one of their own blocked calls.
Understand
How Bloom AI finds the right contact
Bloom AI searches for the number among BoondManager contacts. Candidates are not supported.
-
The rep, by email
The rep is linked to their BoondManager user by email. An admin can adjust this link.
-
The contact, by phone number
Bloom AI files the call on the contact holding that number. When several contacts hold it, the rep picks in the app, or an administrator in To handle.
-
An unknown number
Bloom AI creates no contact in BoondManager: the rep picks an existing contact in the app, or an administrator in To handle. That choice holds for the number’s next calls.
Understand
What Bloom AI creates in BoondManager
The conversation details and recap, on the right record.
-
One action per call
On the right contact’s record, under the chosen action type, with the rep as owner: direction, duration, outcome and AI recap.
-
A reference that prevents duplicates
The Bloom reference in brackets, at the end of the text, keeps a call from being sent twice. Do not remove it, and do not copy it into another action.
-
Deletion when you delete the call
A call deleted in Bloom AI deletes its action in BoondManager. No contact is deleted.
Recordings, transcripts and scores stay in Bloom AI.
Keep permissions and references
If a right or the Bloom reference is removed, sending may wait. Fix the cause, then click Retry in To handle.
Understand
Requested access
The requested access is used to put recaps on the right records.
-
Actions: read and write
Find, create and delete a call action.
-
Contacts: read
Find the contact for a number and offer records to choose from.
-
Resources, accounts and roles: read
Link each rep to their BoondManager account.
Bloom AI never has more permissions than the account that connects it. Your database is never copied.
Fix and manage
If a call doesn't arrive in BoondManager
Done in
Bloom AI
A blocked call shows up in the To handle card of the Integrations section, with its reason and a button. Fix the cause, then retry: nothing is created twice, nothing gets lost. Find the message you see in the app below and open it to know what to do.
In the “To handle” card
Button in Bloom AI Find the contact
What to do Choose the right record in Needs attention.
Button in Bloom AI Find the contact
What to do Choose the right record: Bloom AI never guesses.
Button in Bloom AI Find the contact
What to do Search by name and choose the record.
Button in Bloom AI Link the rep
What to do Link the rep to their CRM user.
Button in Bloom AI Retry
What to do Restore the connecting account’s permissions, then retry.
Button in Bloom AI Retry
What to do Check the chosen action type and the contact’s record in BoondManager, then retry.
Button in Bloom AI Retry
What to do Retry; contact our team if the issue persists.
Button in Bloom AI Stop watching
What to do Bloom AI is checking deletion. Stop monitoring only after checking the activity in your CRM.
Button in Bloom AI Choose the action type
What to do Choose an active type in the BoondManager action type card. Calls wait for this choice without being lost.
When connecting
Why The authorization was cancelled, or the Bloom app is not enabled for the account’s role: BoondManager then shows “insufficient rights”.
What to do Enable Bloom in the role’s Apps tab (Administration › Managers / Roles › Roles), then restart the connection.
Why The account did not grant a requested access.
What to do Connect with a manager or administrator whose role has the Bloom app enabled, and accept every access.
Why This BoondManager database is already linked to another Bloom AI organization.
What to do Disconnect it from the other organization, or contact us.
Why The reconnection targets another BoondManager database than the connection’s.
What to do Reconnect with an account of the same database. To change databases, disconnect first.
Why Another CRM is already connected to your organization.
What to do Disconnect it in Integrations, then connect BoondManager.
Why You are neither an owner nor an administrator of the Bloom AI organization.
What to do Ask an owner or an administrator to connect BoondManager.
Why The CRM integration is not part of your plan, or was turned off.
What to do Contact us.
Why The Bloom app was uninstalled or disabled for the role, or its access expired.
What to do Re-enable the app if needed, then click Reconnect BoondManager: waiting calls are sent right away.
Why The reconnection was not done within 30 days.
What to do Connect BoondManager again from Integrations. Only calls after the new connection are sent.
Fix and manage
Disconnect BoondManager
-
From Bloom AI
In Integrations, click Disconnect. Bloom AI revokes and forgets its access. Existing activities remain in BoondManager; pending operations are abandoned.
-
If the app is removed in BoondManager
If the app is uninstalled or disabled for the role, Bloom AI notices at the next send: it shows Reconnection required and emails you. Calls keep being collected: re-enable the app, then reconnect from Integrations.
-
After a disconnection
Syncing restarts from the new connection. Conversations during the gap are not sent.
A question about your setup?
Our team helps you connect BoondManager and set your rules.