iMessage API use case
iMessage API for lead qualification.
Turn an inbound text into a useful sales conversation. Your agent can ask the questions your team uses, write the answers into your CRM and pass qualified people to a human.
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.
- Ask qualifying questions in a natural, one-at-a-time conversation.
- Create or update a lead in your CRM through a tool or API.
- Send a concise handoff with the context a sales rep needs.
A practical path
Build it in three steps.
- 01
Define the questions, qualification rules and CRM actions.
- 02
Test short answers, incomplete answers and requests to speak with a person.
- 03
Invite prospects to text your Flow number or use a dedicated line where appropriate.
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 Flow send cold iMessages to leads?
A Flow line only replies by default. Writing first comes with the $40 a month Outbound add-on on a dedicated line, bought in the dashboard, and only to people who expect to hear from you, never bought or scraped lists. The new conversations a line starts ramp from 2 a day to 40 a day over 21 days.
Does the same agent work on other channels?
Yes. Flow is designed for one agent across iMessage, WhatsApp, Telegram and MCP, so the qualification logic does not need a separate rewrite per channel.
One agent, more places
Bring this use case to iMessage.
Build and test with Flow, then give customers a number they can text.