iMessage API use case
iMessage API for concierge services.
A concierge needs context, reliable actions and an easy handoff. Flow connects the same agent to your information and operational tools so it can help without making promises it cannot keep.
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.
- Answer common requests using the information your team maintains.
- Use connected tools for availability, reservations or status checks.
- Escalate sensitive or unusual requests with the full conversation attached.
A practical path
Build it in three steps.
- 01
Choose the requests the concierge can safely complete on its own.
- 02
Connect the systems that provide live availability and confirmations.
- 03
Test edge cases with simulated people before customers use the line.
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 a concierge use more than one channel?
Yes. One Flow agent can serve iMessage, WhatsApp, Telegram and MCP, with the same tools and operational rules behind it.
How do we start?
Use the Telegram sandbox or simulated contacts to test the agent, then start with a free trial on the shared iMessage line for 25 people.
One agent, more places
Bring this use case to iMessage.
Build and test with Flow, then give customers a number they can text.