"Is my appointment still on?" "Can we move the showing to Saturday?" "How many shares do I own?" Our AI can't know that — your system can. Connect your own reply bot to your line and it answers every text from your database, booking system or spreadsheet.
The same automation your dentist and your realtor use — on blue bubbles.
Appointment reminders with "Reply Y to confirm, R to reschedule" — the answer updates your calendar or booking system directly.
Confirm, decline or move a showing, and notify everyone involved the moment the client replies.
"What's my balance?" "When does my order ship?" "How many shares do I have?" — answered from that customer's own record.
We POST it to your bot within seconds — who sent it, the message, any photo or voice memo, and that contact's columns from your list.
It finds the customer in your data and writes the answer — with your own AI account or ours.
Through our send API, from the same number the conversation is on. You watch it all in your Inbox and can jump in anytime.
Every option needs a sending line. Prices are one-time setup — no demo call required to see them.
Whose AI writes the answers? By default your own Claude account — you pay the AI company directly, usually pennies per reply, and nothing extra to us. Rather not deal with it? We run it on our managed AI for +$49/line/mo (the same price as our Inbound AI).
Where does it run? On your own website or server. No website? We can host it for you.
Paste this into Claude, ChatGPT or your developer's chat. Fill in the [brackets].
I use iBlueText (https://ibluetext.com) to text my customers by iMessage and SMS. Build me a reply bot on my website that:
1. Receives every incoming text from iBlueText's webhook (docs: https://ibluetext.com/docs/#webhooks). Verify the ?key= secret in the URL, answer HTTP 200 right away, and ignore duplicate message_id values.
2. Looks up the texter by phone number (the "from" field) in my customer data: [describe it — e.g. my appointments database / a spreadsheet / my booking system].
3. Writes a short, friendly answer using that data and my business info: [paste your FAQ, hours, policies].
4. Sends the answer back with POST https://ibluetext.com/api/v1/send (Authorization: Bearer MY_IBLUETEXT_API_KEY, JSON {"to": from, "body": answer}).
5. Hands off to me (no reply, plus an email alert) when it isn't sure, and never answers "message.optout" events.
Keep my API key in server config, never in the page. When the bot is live, connect it yourself with my API key: GET https://ibluetext.com/api/v1/webhooks for my signing secret and line IDs (verify X-IBT-Signature with it), then POST https://ibluetext.com/api/v1/webhooks with {"url": <the bot's webhook URL>, "lines": "account", "replies_handled_by_webhook": true, "test": true} (docs: https://ibluetext.com/docs/#webhooks-api). Don't reply to message.test events.
Confirmations, reschedules and account questions — handled from your own data, on blue bubbles.
Start free