AI SMS customer support

SMS is constrained in ways email and chat are not: 160-character segments, no rich formatting, strict carrier compliance rules. The Guru's SMS adapter handles these constraints so the conversation still feels useful and natural.

How it connects: you own the number

SMS runs on the same Bring Your Own Credentials model as voice. You create and own your Twilio account, provision your number under it, and pay Twilio directly for messages. instantAIguru never sits between you and the carrier and adds no per-message markup; it charges only a flat per-channel SaaS fee.

1. Create a Twilio account and provision your SMS number under it.
2. Before the number can send on US carriers, you must submit and pass an A2P/SMS Campaign application. This is your own approval to obtain; it registers your business and your use case with the carriers, and you must clear it before sending.
3. Enter your Twilio Account SID and Auth Token in the admin panel and go live.

Because the number and the carrier billing live in your own Twilio account, if you ever disconnect, your number and your customers come with you.

Built for the SMS format

A single SMS is short, and very long messages get split into multiple segments and feel awkward. The Guru keeps replies brief and conversational, summarizing long answers and offering a link for the full version rather than dumping a wall of text.

A worked example

Inbound from +14155550123: "hours today?"

1. The message arrives via Twilio webhook.
2. Conversation memory loads (new contact, no prior history).
3. Retrieval pulls /hours: "Mon-Fri 8a-6p, Sat 9a-1p, Sun closed."
4. Current date is Thursday, so the formatter generates a context-aware reply.

Reply: "We're open today 8am to 6pm. Anything I can help with?"

The reply is one segment and answers the implicit question (today's hours) rather than dumping the full week.

A worked example with handoff

Inbound: "I want to cancel my subscription."

If your policy is to require human approval for cancellations:

1. The Guru recognizes the intent and confirms politely.
2. It collects key info (account email, reason if offered).
3. It creates a ticket in your helpdesk with full context.
4. It replies: "Got it. I've notified our team and Sam will text you back within the hour to confirm. Anything else in the meantime?"

The conversation stays on SMS for the customer even though a human picks it up on your side.

Compliance

US SMS compliance is real and enforced. The adapter handles:

• STOP/UNSUBSCRIBE/CANCEL/QUIT keywords: immediate opt-out and the required confirmation reply.
• HELP keyword: automatic informational reply with business name and contact.
• The A2P/SMS Campaign approval you obtained for your own Twilio number governs your traffic on US carriers.

These are not optional; carriers will block your traffic if you ignore them.

Two-way conversation, not blast marketing

SMS is treated as a true conversation channel. The same knowledge base, brand voice, and conversation memory used on web chat apply here. A customer who texted yesterday is recognized today; their prior thread loads as context.

Trade-offs

• Voice tone is more compressed than chat; replies are factual and brief.
• Rich elements (buttons, carousels) are not part of SMS. WhatsApp is the better channel if you need interactive UI.
• Carrier message charges are billed to you by Twilio directly. The summarize-and-link strategy keeps replies short, which keeps that carrier cost predictable.

When SMS is the right channel

Status updates, appointment reminders, quick FAQ, two-factor codes, and short transactional replies are SMS-native. Long form (multi-paragraph explanations, attachments, formal communication) belongs on email. The Guru picks the natural format for the channel automatically.