Messaging — SMS & email
Your number, your domain, every message logged to the customer record.
Confirmations, reminders, campaigns, and one-to-one conversations ride the same rails: your own phone number and sending domain, delivery tracking, and a message center where every thread is attached to the contact it belongs to.
How it helps you
Nothing falls through the cracks
Every inbound and outbound message is on the contact timeline — anyone on the team can pick up the thread.
The system does the routine sends
Booking reminders, event confirmations, waitlist wins, receipts — automatic, and delivery-tracked.
Deliverability done right
Your own domain and number mean your reputation is yours; failures surface instead of vanishing.
The walkthrough
Connect email and SMS once
Settings walks you through your sending domain and number; a banner tells you if a channel still needs setup.
Automatic sends go live
Bookings, events, orders, and sequences use your channels immediately.
Work conversations in the message center
Reply from the dashboard; the thread stays on the contact forever.
Shipped features behind this
From the same machine-readable catalog we publish at /features.json — what your AI reads to learn the platform.
Messages — org-wide log, compose, opt-out list
One place for everything sent to contacts across email/SMS/push: the org-wide message log with channel filter, a compose modal for direct sends, and the opt-out (suppression) list — visibility only, since the platform refuses suppressed recipients at send time. Per-contact threads stay on the contact page.
Notifications inbox
Updates from your team and your work in one list (GET /comms/notifications), mark-as-read per item. The bell in the shell header deep-links here.
Common questions
Do messages come from your brand or mine?
Yours — your sending domain for email, your number for SMS. The platform is invisible to your customers.
What happens when a message fails to deliver?
Failures are recorded on the message and surfaced — including to the built-in coach, which watches for delivery problems and tells you.
See it, then build on it
This whole site runs on the same platform — fork the template, or point a front end you built with Lovable, v0, Bolt, Claude, or Cursor at the backend.