The people recordLive
One person, one record, whichever agent picks up.
A CRM written for agents rather than for a sales team. Every worker AI3 sells writes to it — the receptionist first — so the caller who booked on Monday is known by name on Friday without anybody filing anything.
The contract The agent that fills it
On your own organisation it is at /o/<slug>/customers.
- Matched on the number
The last nine digits, so a number typed any way finds the same person. One person is one record.
- Everything writes to it
Calls, enquiries from your page, marketplace orders, the assistant’s notes. A business that hires four agents does not end up with four address books.
- Mirrored, never trapped
HubSpot, or one signed POST to a system of your own. The AI3 copy stays the one the agents read.
Why it exists
A business hires a receptionist and the receptionist takes a name. Then it hires an assistant, and the assistant has never heard of that name. That is the failure this record exists to stop: it is the one place the people go, it is there on the day the organisation is created, and nothing has to be connected for it to work.
How it works
Somebody arrives
A call, an enquiry from your page, an order, a message. The agent handling it looks the number up before it speaks.
The record is found, or made
By phone or by email. A fuller field wins over a thinner one, and a placeholder like “Caller” never overwrites a real name.
A line goes on the timeline
Dated, and it says who did it: an agent by name, the owner, the customer, or the system. Calls, bookings, messages, enquiries, notes, orders, invoices, quotes, visits.
What is owed becomes an open item
A callback, a booking, a quote, a job, a follow-up, an invoice — each with a due time, closed as done or cancelled by whoever did it.
It is mirrored out
A HubSpot contact with the timeline as notes, or a signed webhook to anything that takes JSON. A mirror that fails is reported and never loses the write that caused it.
A Tuesday, from a missed call
- 08:14The phone rings and nobody is there
Ivy answers. The number is unknown, so she asks. Dana Ortiz, blocked drain, Bay Ridge. A customer record exists by the time the call ends.
- 08:16Booked
Thursday at two. That is a line on Dana’s timeline and an open item due Thursday.
- 08:16Mirrored
A contact appears in HubSpot with the call as a note. Nobody typed it.
- 11:02She calls back
Ivy greets her by name and says what is booked before Dana has finished her first sentence.
- Thu 16:40The job is done
The open item closes. The invoice raised against it is the next line on the same timeline.
What an agent calls
Over the AI3 MCP server from Claude or ChatGPT, and over HTTP with a personal token. Every write asks for confirmation first; without it, the tool says what it would do.
list_customersEveryone the organisation has dealt with, or a search across them.get_customerOne person by id, phone or email, with what happened last and what is still open.upsert_customerFind or create. The matching is the point: it will not make two people out of one number.add_customer_noteA dated line in the name of whoever did it, with an item to open if something is now owed.list_open_itemsWhat is still to do for whom, and when it is due.close_open_itemDone, or cancelled, by name.
What it will not do
- It will not make two people out of one phone number.
- A placeholder never overwrites a real name, and a thinner field never overwrites a fuller one.
- A mirror that fails is shown on the connector with its last result. It never fails, and never hides, the AI3 write.
What it connects to
The systems this record mirrors to or draws on. Each row says whether it is switched on for this server, because a wall of logos that all look connected is the one thing these pages must not be.
- HubSpotEach organisation connects its own
Each customer a contact, each call, booking and message a note. A private app token per organisation.
Customers → Where the record lives - Your own CRM (webhook)Each organisation connects its own
One signed POST per write to any system that can take JSON. Salesforce, Pipedrive and Zoho fit here today.
Customers → Where the record lives - ElevenLabsConnected on this server
The receptionist’s voice, hearing and telephony bridge.
Hire → Receptionist - TwilioConnected on this server
The phone number the receptionist answers on, bought per organisation.
Phone → Your number - ResendNot switched on here
Every email the platform sends: enquiries, call notes, invoices, reminders.
Server
Customers is one of 5.
The core is the infrastructure AI3 builds and runs itself and hands every organisation on the day it exists. Read the rest, or see what your own systems plug into.