Where your customers actually live isn't your website.
AI Concierge handles every question that lands on your chat widget. But customers who prefer messaging apps don't visit your site first — they message you where they already are. That conversation never reaches your AI until you bridge the gap.
Your AI already handles these questions. It just can't hear them yet.
AI Concierge answers every one of these — once the customer reaches your site. AI Messaging gets your AI to them where they already are.
Not three bots. One agent, three channels.
AI Messaging is a thin bridge plugin — not a parallel chatbot. Every message from WhatsApp, SMS, or Messenger flows through your existing AI Concierge instance: same indexed content, same RAG pipeline, same escalation state machine. The channel classes only handle platform plumbing.
{channel}_{digits-only-phone} and looks up or creates the AIC session. Same key every message from the same customer.The AIC chat engine, session system, and escalation state machine are reused unchanged. No duplicate content index. No second bot to train. No drift between what AIC says on your site and what it says on WhatsApp.
A messaging bridge that treats your AI as the source of truth.
No parallel knowledge base. No second bot config. No platform-specific tuning. AI Messaging adds three webhook handlers and a chip mapper — everything else is AI Concierge doing what it already does.
WhatsApp + SMS + Facebook Messenger CORE
WhatsApp via Meta Cloud API, SMS via Twilio, Facebook Messenger via the Meta Platform API. All three answered by the same AI Concierge instance — same indexed content, same answers, same escalation.
Webhook endpoints register automatically. Paste your platform credentials in the admin and the channels go live.
- WhatsApp (Meta Cloud)
- SMS (Twilio)
- Messenger (Meta)
- One AIC Backend
- Auto-Register Webhooks
One Session Per Customer, Forever ALL CHANNELS
Sessions are keyed by {channel}_{digits-only-platform-id}. A returning WhatsApp customer's full history is loaded on every message — no re-introduction, no "what was that order number again?".
The session key format is locked — conversations don't get orphaned when you upgrade. Same architecture AIC has used for the web widget since 1.0.
- Locked Session Key Format
- Full History Per Message
- No Re-Introduction
- VARCHAR(100) AIC Native
- Upgrade-Safe
No "Reply 1) Yes 2) No" Hacks PER PLATFORM
AIC follow-up chips map to each platform's native interactive UI: WhatsApp interactive buttons (max 3, 20-char titles), Messenger quick_replies (max 13), SMS numbered list with single-digit reply resolution.
Excess chips are silently truncated to the platform limit — never errors, never breaks the response. The SMS bridge resolves "1" / "2" / "3" replies back to the chip text before passing to AIC.
- WhatsApp Buttons (max 3)
- Messenger quick_replies (max 13)
- SMS Numbered List
- Single-Digit Resolution
- Silent Truncation
Same Handover. Every Channel. ALL CHANNELS · ★ KEY
When a customer asks for a human on WhatsApp, the same name-capture → email-capture → admin-notify state machine fires. Same as the web widget. Your admin gets the same email, in the same format, with the channel and platform ID appended.
No new code paths to debug. No "but escalations from SMS work differently" surprises. The state machine has zero HTTP request dependencies — it just works.
- Same State Machine
- Same Admin Email
- Channel Tagged in Notify
- Zero AIC Code Changes
- No Channel-Specific Logic
Tokens Encrypted. Signatures Verified. ALL CHANNELS
Every access token, app secret, and Twilio auth token stored AES-256-CBC encrypted in wp_options. Zero plain text. Platform webhook signatures validated with constant-time comparison to prevent timing attacks.
HTTP 200 returned on every webhook in under 2 seconds — well under Meta's 5-second retry threshold — so you never trigger retry storms.
- AES-256-CBC Encryption
- HMAC Signature Validation
- Constant-Time Compare
- <2s Webhook ACK
- No Retry Storms
Paste Credentials. Save. Done. ZERO CODE
A 4-tab settings page in WordPress admin: WhatsApp, SMS, Messenger, and a status overview. Paste your WhatsApp Cloud API token, your Twilio Auth Token, your Messenger Page Access Token, hit Save. The REST webhooks register themselves.
No code changes, no developer required. If AI Concierge is on the site and licensed Pro, you're ready to go live.
- 4-Tab Settings Page
- Per-Channel Toggle
- Auto-Register Webhooks
- No Code Changes
- Status Overview Tab
One tier. Every channel.
Pick monthly to start or annual to save two months. Same feature set on both. Bring your own platform credentials — speak2web doesn't sit between you and Meta or Twilio, and doesn't mark up your message volume.
- WhatsApp + SMS + Messenger
- One AIC backend, all channels
- Native interactive chip mapping
- Escalation works on every channel
- AES-256-CBC encrypted credentials
- 4-tab admin -- no code changes
- Requires AI Concierge >= 2.4.0
Coming sooncontact us for BETA access
- Same full feature set
- 2 months free ($20 saved)
- Locked-in price for the term
- Priority email support
- Priority channel feature requests
Coming sooncontact us for BETA access
Real specs. No vague claims.
Get Started in Under Five Minutes.
Buy the license, download the plugin, upload to WordPress, paste your platform credentials. The webhooks register themselves. Requires an active AI Concierge Pro license.