Can an AI receptionist send text messages?

The caller's text is short and tied to the call they placed. They asked for an appointment, and the assistant booked it and read the time back. The confirmation lands on their phone, where they can check it against their own calendar.

A caller who didn't settle on a time gets the booking link instead. The next step is one tap away rather than a second phone call.

Texting a consumer is outbound contact and comes with opt-out obligations. That's why the caller's message is a single text about the thing they asked for, with an opt-out word that works. Reminder campaigns and marketing texts run from the system that holds each customer's written consent.

The booking confirmation confirms the appointment the assistant booked on the call. The same booking lands in your Google Calendar or Outlook, so you and the caller are reading the same slot.

The booking link goes to a caller who wanted to choose a time later, and it lets them pick one when they're ready.

A reply with the opt-out word stops further texts to that number, and GreetKeeper honors it. One message follows a call; nobody gets a sequence from your phone line.

The text goes to the number the assistant captured on the call. A caller on a landline or an office switchboard still hears the name, number and time read back before the booking is made. The confirmation isn't the only record.

Your webhook payload carries the caller-text details alongside the booking, so whatever receives the booking.created event knows a confirmation went out.

A text to your own staff is a different thing. When the assistant texts your on-call person with a caller's details, it is alerting someone inside your business. That text fires only on calls that match a rule you wrote.

Say you run a physical therapy clinic. A patient calls at 7pm about a shoulder that's been stiff since a fall. The assistant books her for Thursday at 9, reads the day and time back, and the call ends. A moment later her phone shows one text with the booking confirmation, and the appointment is already sitting in your Google Calendar.

The next caller wants to check his work schedule before he commits. The assistant takes his name and number and, after the call, he gets the booking link instead. He picks Friday afternoon from his sofa, and that booking lands in the same calendar.

Your existing reminder sequence from the clinic's own scheduling software keeps running as it always did, from the system that holds each patient's written consent. GreetKeeper's text is the one message about the call the patient just made.

Start with the number itself. The text goes to the number the assistant captured on the call. A caller from an office switchboard still hears the time read back before the booking is made, so the calendar entry stands on its own.

Test the opt-out. Book a slot from your own cell, reply to the confirmation with the opt-out word, and book again the next day. The second confirmation stays away, because GreetKeeper honors the opt-out for that number.

Then watch the webhook. The caller-text details travel in the payload with the booking, so the record in your CRM shows that the confirmation went out. Your on-call texts run in parallel and go to your staff, with the caller's name, number and reason attached.

GreetKeeper texts the caller once after the call. The caller gets the booking confirmation when the assistant booked, or the booking link when they wanted to pick a time later. A reply with the opt-out word stops further texts.

It texts the on-call person with the caller's details when a call meets the rule you set. An emergency at 2am reaches a phone rather than the morning's inbox.

Every call also arrives as a transcript and a short summary with the caller's number. The webhook posts the booking, the message and the caller-text details to any URL you set. Booking is on every plan, starting at $49 a month for 200 answered calls.