iMessage API use case
iMessage API for appointment booking.
Let people book without leaving Messages. Flow gives your booking agent the conversation layer while your calendar or scheduling API remains the source of truth.
The job
Make the conversation useful.
The channel is only valuable when the agent can do the work behind the reply. Start with the narrow set of actions your team can verify, then expand from what customers actually ask.
- Check real availability before the agent offers a time.
- Confirm, change or cancel a booking through your own scheduling tools.
- Keep the booking conversation going when the customer returns later.
A practical path
Build it in three steps.
- 01
Expose availability and booking actions to the agent.
- 02
Test reschedules, no availability and changed minds with simulated conversations.
- 03
Put the agent on a shared or dedicated iMessage line for customers to text.
Start small, scale cleanly
Free for your first 25 people.
Move to a $25 shared line for 300 people a month and 200 a day, then to a $100 a month dedicated line for 1,000 people a day (a new line starts at 250 a day and ramps to 1,000 over its first 14 days). The same agent can also serve WhatsApp, Telegram and MCP.
Common questions
Before you put it live.
Can the agent book an appointment directly?
Yes, when you connect the calendar or booking action it is allowed to use. The agent should read and write through that system, rather than guessing availability.
Can we start with a shared line?
Yes. The free trial on the shared line is for 25 people, and the $25 shared line is built for 300 people a month and 200 a day.
One agent, more places
Bring this use case to iMessage.
Build and test with Flow, then give customers a number they can text.