Backoffice prototype lab for the WhatsApp channel: connect a customer-facing business number,
preview future team notification settings, and run the simulator from one place before the real UI is split.
Customer-facing channel
Business WhatsApp number, Meta identifiers, response mode, and visitor entry points.
Target: HEA Editor > WhatsApp
Team connections & notifications
Email accounts (Gmail, Microsoft, IMAP), notification preferences (when & how), phone/email verification.
Target: Town Hall > Connectors
📱
Customer-facing WhatsApp channel
Prototype target: HEA Editor > WhatsApp
ℹ️
This section is for the WhatsApp Business number visitors message. It is separate from the
personal or staff numbers used by the sales team for notifications.
WhatsApp Business number
Checking…
Connect the public business number that customers will see on the website and use to chat
with this HEA on WhatsApp.
Business phone—
Meta phone ID—
WABA ID—
Display Name—
Connected—
Phase 0 response mode
The current backend pipeline supports direct auto-reply. The product target is still to make
co-pilot the safer default, with auto enabled intentionally by the creator.
Prototype note: this selector documents the roadmap. Only Auto is wired in this admin page today.
What HEA accesses:
WhatsApp messages sent to the connected business number are processed by the HEA chatbot to generate replies.
Message content is used for real-time conversation and may be stored in session state for context continuity.
HEA does not access a sales person's personal WhatsApp account or contacts.
Token storage:
Your WhatsApp access token is encrypted using AES-256-GCM before storage.
The plaintext token is never persisted and cannot be recovered from storage.
Revoke access:
You can disconnect at any time from this page. Disconnecting removes the encrypted token
and clears the KV routing index. Existing relationships from WhatsApp conversations are kept.
🔗
Town Hall Connectors prototype
Target: Town Hall > Connectors
ℹ️
This previews the full Town Hall Connectors page: email accounts that feed the pipeline,
plus per-user notification preferences. Each team member configures their own.
My Email Accounts
Connect your email to feed leads into the Town Hall pipeline. You can connect Gmail and Microsoft simultaneously.
📧
Gmail
Sync emails from your Google Workspace or personal Gmail.
Not connected
📬
Microsoft 365 / Outlook
Sync emails from your Microsoft or Outlook account.
Not connected
✉️
IMAP COMING SOON
OVH, Infomaniak, Fastmail, mailbox.org, and other providers.
Soon
My Notification Preferences
Choose when and how you want to be notified about HEA conversations.
Each team member sets their own preferences.
Notify me when
✓
💬 Visitor messages on WhatsApp
A customer starts or continues a WhatsApp conversation with this HEA.
On
🌐 Visitor starts web chat
When a visitor chats on the website widget.
Soon
Notify me via
✓
📱 WhatsApp
Receive a WhatsApp alert with a link to the conversation.
→ +31621303845
✓ Verified
On
✓
✉️ Email
Receive an email summary when a conversation needs attention.
→ nicolas@60000rebonds.com
✓ From Gmail
On
Verify your contact details
📱 Phone number
We'll send a verification code via WhatsApp to confirm this is your number.
✉️ Email address
Auto-filled from your connected email account. No extra verification needed.
✓ From Gmail
How it works:
the visitor chats with the HEA through the business WhatsApp number or website widget;
you receive an alert through your verified phone or email.
Each team member verifies their own number and chooses their own notification preferences.
🧪
Quick Test
ℹ️
Send a simulated WhatsApp message to verify the adapter pipeline end-to-end. This uses the mock buffer in dev/preview.
This modal provisions the HEA's customer-facing WhatsApp channel. Staff phone numbers belong in Town Hall Connectors later.
The access token is encrypted with AES-256-GCM before storage; plaintext is never persisted.
Future creator flow after Meta Tech Provider / Embedded Signup approval