01
Answers at 11pm
Texts arrive after close, which is exactly when nobody is at the desk. Your agent replies in seconds with the same tone at 11pm as at 11am, and the request is on your list before you open.
Your agent, on iMessage
AI agents for iMessage
The thread they already have open.
Your customers would rather text than call, and they text at 11pm. Your agent answers in the same thread, in seconds: it captures complete booking requests, sends day-before reminders, answers questions from your own profile, and knows which messages need a person instead of a queue.
What it handles
Ten things it handles in the thread, without being asked twice.
02
Booking requests, complete
It collects name, service, preferred day and window, and whether they are new, then hands you one request you can confirm — not a fragment you have to chase across three messages.
03
Reminders in the same thread
The day-before reminder lands in the thread the booking was made in, so a reply confirms, moves, or cancels without anyone dialling.
04
Read receipts, group threads, tapbacks
iMessage habits carry over. The agent reads a "👍" as a confirmation, keeps its answer short when the thread is a group, and never sends the wall of text people ignore.
05
Answers from your own information
Hours, pricing, parking, insurance, what to bring: it answers from the profile you wrote, in your words. Nothing you did not put there gets invented.
06
Triage instead of a ticket
Some texts are urgent and need a phone call. The agent recognises them, says so plainly, and escalates the thread to you rather than filing it behind twelve routine ones.
07
Reschedules without a phone tree
"Can we push Thursday?" becomes a change request with the original booking attached. You approve; the customer gets the new time in the thread.
08
Remembers the person
The number is the identity. Returning customers do not restate what they told you in March, and the agent picks the thread back up where it stopped.
09
Follows up once, then stops
One nudge on an unanswered question, then it goes quiet. Nobody is going to buy from a number that texts them four times.
10
Hands over cleanly
When you take the thread, you get the whole conversation and what it already promised — so your first message is not "sorry, can you repeat that?".
A real thread
This is the entire product surface.
No dashboard for your customer, no widget, no app install. They text the number you already put on your door, and the answer arrives where every other message in their life arrives.
iMessage · +1 (415) 555-0134An iMessage agent vs a chat widget
A widget waits for a visit. A thread does not.
Website chat only works while someone is on your site, in a tab, during the ten minutes they thought about you. iMessage is a conversation that stays open for years and is read within minutes.
| Capability | Your iMessage agent | Website chat widget |
|---|---|---|
| Where it lives | The thread on their phone, next to their family and their dentist. | A bubble in the corner of a page they have to be on. |
| After hours | Answers in seconds and books, all night. | "Leave your email and we will get back to you." |
| Reply rate | Texts get read. A reminder in the thread gets answered. | The follow-up email lands in Promotions. |
| Identity | The phone number is the customer record, message one. | An anonymous session until they fill in a form. |
| Handover | You take the same thread, with the full history. | The visitor is gone by the time an agent joins. |
| What the customer installs | Nothing. Messages is already on the phone. | Nothing — but they also have to be on your site. |
Start from a complete template
Dental Front Desk
The complete template for a practice that would rather text than answer the phone: booking requests, reminders, insurance answers, and real triage — all in iMessage.
What comes with it
- Booking requests captured complete: name, service, day and window, new or returning
- Day-before reminders in the original thread, with reply-to-move
- Insurance and pricing answers from your practice profile, never invented
- Urgency triage that escalates to a phone call instead of a queue
- Patient memory across threads, keyed to the phone number
- A morning digest of everything the night shift handled
Questions
What people ask about running an agent on iMessage.
- Does this work with iMessage or only SMS?
- Both. The agent runs on the number, so blue-bubble iMessage and green-bubble SMS land in the same conversation. Your customer does not think about which one they used, and neither does the agent.
- Do my customers need to install anything?
- No. They text the number you already publish, from the Messages app that shipped with their phone. There is no app, no link to click, and no account to create.
- Can I take over a conversation myself?
- Yes. Any thread can be handed to a person, and you get the full history plus everything the agent already committed to, so you are not restarting the conversation.
- What stops it from making things up about my business?
- It answers from the profile you write — hours, services, pricing, policies. When a question falls outside it, the agent says it will check rather than guessing, and the thread goes to you.
- What happens with something urgent?
- Urgency is triaged, not queued. The agent recognises the messages that need a phone call, says so in plain language, and escalates the thread immediately instead of filing it behind routine requests.
- How long does setup take?
- Start from the Dental Front Desk template and you have a working agent in minutes: it arrives with the booking flow, reminders, triage rules and memory already wired. You edit the profile, not the plumbing.
Answer every text tonight.
Start from a complete template, point it at your number, and let the thread do the work your phone line was never going to do after 6pm.