A CRM bolted onto a business is a second copy of that business. It has its own customer list, its own definition of "active", and its own answer to how much someone is worth — and none of them match what accounting or the shop would tell you.
Here the CRM is a set of surfaces over records the rest of the platform already owns.
What it covers
- Leads — pipelines, stages, scoring and enrichment
- Forms — capture that writes straight into those pipelines
- Tickets — support work with owners and history
- Reservations — bookings and appointments
- Signed documents — agreements against a customer record
- Campaigns and audiences — segments built from real behaviour
- Inbox — conversations across channels in one thread
- Communications — unified call, SMS and voicemail history
Why the shared model is the feature
Consider a segment like "customers who bought in the last 90 days, have an open ticket, and have not been contacted since". In a stack of separate tools that is an export, a spreadsheet and an afternoon. Here it is a query, because purchases, tickets and contact history are attributes of the same record.
The same applies in reverse. A missed call can create a lead. A paid invoice can advance a pipeline. A check-in at an event can update the audience a campaign is targeting — without an integration between two products, because there are not two products.
Where the AI sits
The assistant is not a chat box off to one side. It works against the same records and the same permissions you do, which means what it can see is what your role can see, and what it changes is audited the same way.
Read next
- CRM API — leads, tickets, campaigns and the rest
- CRM in Studio Manager
- AI CRM