The engine
Eight modules.One engine underneath.
Each module does one job well. The engine underneath makes them one system: the same person, the same thread, the same consent, whichever module is in use.
01 / 08AC Voice
Answer every call.
Hosted numbers, call routing and an AI receptionist that picks up when your team can't. Every call is recorded and transcribed as it happens, and the transcript lands on the caller's thread.
What it does
- Hosted numbers per business
- IVR and call routing
- AI receptionist
- Call recordings
- Live transcription
- Post-call transcripts and summaries
On the thread
A call becomes an entry on the thread, with its recording, transcript and outcome attached.
“Is there anything Saturday morning?”
Answered by the AI receptionist · recorded · transcribed
02 / 08AC Messaging
Reach people where they are.
Text, rich messages, WhatsApp, Instagram and social inboxes, all in one conversation. Schedule sends ahead and cancel them if plans change, and consent is checked before every message leaves.
What it does
- SMS
- RCS
- Social channels
- Scheduled sends
On the thread
Every channel writes into the same conversation, so a reply on WhatsApp follows a text from yesterday.
“Reminder: see you tomorrow at 10:30.”
Sends Friday 10:30 · cancelled automatically if she reschedules
03 / 08AC Mail
Own your email.
Hosted domains and real mailboxes for the business, plus marketing and transactional sending, all under your brand. Each business sends from its own domain and keeps its own sending reputation.
What it does
- Hosted domains
- Mailboxes
- Marketing sends
- Transactional sends
- Per-business sending domains
On the thread
Replies to any email thread back to the person who wrote them, next to their calls and texts.
“Could my son come along too?”
Threaded to Maya, not a new ticket
04 / 08AC Calendar
Get booked.
Availability, booking pages and external calendar sync. A booking creates or finds the contact, starts or extends their thread, and sends confirmations and reminders through the channels they've agreed to.
What it does
- Availability rules
- Public booking pages
- Hold, confirm, reschedule, cancel
- External calendar sync
- Reminders
On the thread
Bookings, reschedules and reminders appear on the thread the moment they happen.
Saturday, 10:30 · two chairs
Synced to the staff calendar · reminder queued
05 / 08AC CRM
Know your customers.
Contacts, forms, lead capture and pipeline, plus reviews and reputation. Each contact shows everything that happened with that person, on every channel.
What it does
- Contacts
- Forms and lead capture
- Pipeline
- Reviews and reputation
- Contact timeline
On the thread
The contact record is the thread: one person, with their whole history and consent in one place.
Maya Tremblay
Phone, email and consent on one record
06 / 08AC Commerce
Get paid.
Products, inventory, estimates, invoices, contracts and payments, online or in person. A quote sent by text and paid a week later is one story, not two systems.
What it does
- Products and inventory
- Estimates
- Invoicing
- Contracts
- Online payments
- In-person payments
On the thread
Estimates, invoices and payments sit on the thread next to the conversation that led to them.
Paid in person on Saturday
Receipt emailed · linked to the booking
07 / 08AC Team
Run the floor.
Internal rooms, discussions that can be resolved, and tasks assigned to the right person. Staff talk about a customer beside the customer's thread, never inside it.
What it does
- Internal rooms
- Resolvable discussions
- Task assignment
- Internal notes on threads
On the thread
Internal notes attach to the thread without the customer ever seeing them.
“@Jordan, can we fit a second chair?”
Never visible to Maya
08 / 08AC Analytics
See what's working.
Insights and reporting across every module, plus visitor behaviour on the sites your businesses run. Because there's one thread, there's one version of what happened.
What it does
- Insights
- Reporting
- Visitor behaviour
- Cross-module views
On the thread
Analytics reads every thread, so reporting covers every channel, not just one.
Where this week’s bookings started
Calls, texts, email and the booking page, side by side
Beneath the modules
Anyone can wire five vendors together. This is the layer that makes them one system.
Twelve capabilities run through every module. They're why a text, a call and an invoice can belong to the same person, and why a STOP means stop everywhere it should.
Identity
Contact identity and resolution
The caller, the texter and the emailer are the same person.
Phone numbers, email addresses and social handles resolve to one person inside a business. When someone calls from their mobile and replies from their work email, AutoChat links them. It never merges people on a guess.
Across every module
Every module reads and writes the same person, not its own copy.
01 / 12. Use the arrow keys to move between capabilities.
Identity
Who someone is, what they've agreed to, and everything that's happened.
- Contact identity and resolution
- Phone numbers, email addresses and social handles resolve to one person inside a business. When someone calls from their mobile and replies from their work email, AutoChat links them. It never merges people on a guess.
- Consent and compliance
- Every opt-in, opt-out, STOP, bounce and complaint is recorded with who, when, how and on which channel. Every outbound message checks consent first, and if consent can't be checked, it doesn't send. A STOP ends a person's relationship with one sender, while a hard bounce protects every sender in the workspace.
- Unified conversation threading
- Calls, texts, emails, bookings, invoices and internal notes join a single ordered thread per person. Your staff and your AI agents read the same thread, so nobody starts from zero.
Delivery
How messages leave: once, on time, and only when they should.
- Send governance
- Idempotent sends mean a retry never double-texts anyone. Scheduled messages can be cancelled by ID or by attribute. A scheduled message that misses its moment is skipped rather than sent late.
- Notifications
- New messages, missed calls, bookings and payments reach the right staff member by their preferred route, and signed webhooks tell your own systems.
Content
The documents, files and templates every channel shares.
- Documents and signing
- Estimates, agreements and forms go out for signature, and the signed copy comes back to the person's history with a record of how and when it was signed.
- Media and storage
- Call recordings, images sent by message, email attachments and uploaded files are stored per business and linked to the thread they belong to.
- Templating
- Messages, emails and notifications are built from templates with merge fields drawn from the contact, the booking or the invoice, and styled per business.
Intelligence
Agents that work the thread with context, and search that spans it.
- Agent runtime
- AI receptionists and assistants run inside the engine with the same permissions model as staff. They read the thread, follow consent and hand off to a person when they should.
- Intelligent context and retrieval
- Each business's knowledge (services, hours, policies, past conversations) is retrievable at the moment an agent needs it, scoped strictly to that business.
- Cross-module search
- Search one index for people, conversations, transcripts, invoices, bookings and notes, always within the business and permissions of whoever is searching.
Operations
Usage, measured per business so each one is billed separately.
- Metering and billing
- Messages, minutes and every other unit of usage are metered per client. You decide how to package and bill your own customers, and each business's usage stays separate.
Tenancy
A workspace for you. A client for each business you serve.
Data, numbers, sending domains, consent and billing are scoped to each client. Access is scoped to people: your team sees everything, and a contractor sees only what you give them.
Workspace
Your agency or platform
- Your own leads and operations
- Your team
- Every client you serve
- Your brand
Workspace members see every client. You decide who gets which role.
Client A
A dental clinic
- Contacts and threads
- Numbers and domains
- Usage and billing
- Consent records
Client B
A barbershop
- Contacts and threads
- Numbers and domains
- Usage and billing
- Consent records
Client C
A law office
- Contacts and threads
- Numbers and domains
- Usage and billing
- Consent records
Invite a contractor to one client, and one client is all they'll ever see. Each client's sending reputation, numbers and records stay its own.
Two ways to build
The standard app, or your own product on the API.
Use the operator app under your name, build your own interface on the API, or run both side by side. The engine underneath is the same.
A complete operator app, under your name.
Inbox, contacts, calendar, pipeline, invoices and team, ready for your clients on day one. Try it: name your product and pick its colour.
Preview shows Your product in Cobalt, light appearance.
Your product entirely. The engine underneath.
Build your own interface, or none at all. Keep contacts in your own system if you’d rather: AutoChat keeps only what it needs to route, thread and respect consent.
- Every request scoped to one client
- Idempotent sends, safe to retry
- Signed webhooks for every event
- Test keys run the real pipeline in a sandbox
- Consent enforced before every send
// Every call is scoped to one of your clients.
const client = autochat.client(clinic.autochatClientId);
// Find the person, not the phone number.
const maya = await client.contacts.resolve({ phone: "+14035550142" });
// Consent is checked before it sends. A retry never double-texts.
await client.messages.send({
to: maya.id,
channel: "sms",
template: "booking.confirmed",
data: { when: booking.startsAt },
idempotencyKey: `booking-${booking.id}`,
});
Build your product on one thread.
We're working with a small number of partners while the engine grows. Tell us what you're building, and we'll tell you honestly whether AutoChat fits.