Boni CRM
Keep organizations, people, opportunities, activities, and next actions connected to the conversations and work that produced them.
Relationship memory
Boni CRM connects organizations, contacts, opportunities, activities, owners, stages, source references, and next actions. It is designed to preserve why a relationship or opportunity exists—not just a row in a sales list.
Every record belongs to exactly one workspace. Switching workspace changes the CRM you see, and no query crosses that boundary.
In this section
| Page | What it covers |
|---|---|
| Contacts and companies | How people and organizations enter the CRM, how Boni decides two records are the same person, and what protects a name you typed |
| Opportunities and pipeline | Deals, stages, owners, values, and the next action that keeps a pipeline truthful |
| Conversations in CRM | Connecting a messaging account so conversations and their contacts appear on the relationship record |
| Automation settings | Every workspace setting that controls what conversations do when they arrive |
| Activities and next actions | The activity timeline, where typed events come from, and where Boni Tasks takes over |
Developers integrating directly should start at the CRM API.
Connected operations
Conversation, email, voice, campaign, meeting, payment, commerce-order, and workflow events can become typed CRM activities while their source products remain authoritative for their own data. Boni Tasks owns actionable follow-up.
For a connected Bino commerce source, Boni resolves the buyer onto the existing CRM contact by phone or email and records a minimized order activity. The commerce system remains the order authority; CRM does not copy checkout, address, payment-reference, or chat payloads.
This boundary is deliberate. CRM holds the relationship and the deal; each channel keeps its own history where your team already works.
Message contacts
Selecting Message contacts hands the chosen CRM audience to the same Messaging CPaaS campaign composer used in Bow Chat. Sender selection, suppression, scheduling, delivery, and replies remain in that one campaign record.
AI-native use
The Assistant can summarize allowed CRM context, prepare next actions, and perform enabled CRM actions through tenant-scoped APIs. It does not receive broad database access or another workspace's customer records.
Current product shape
CRM modules are enabled per workspace. Available views and actions depend on the installation and role in that selected context.