Q.active — AI WhatsApp Assistant

Q.active

Simulates a WhatsApp conversation

How it works

Add your business information in Knowledge Base.
Tune tone & rules in Bot Settings.
Test here — replies use exactly the same engine as WhatsApp.
Open Inbox to view real conversations and take over as human.

Last reply details

—

Try

Knowledge Base

Everything the AI is allowed to tell your customers. Products, prices, hours, policies, FAQs…

No information yet. Click Add information to teach the bot about your business.

Contacts

Open Inbox

Select a contact

AI Engine

Business name Model

Temperature Max tokens History turns

System prompt (personality & rules) — use {{business_name}} Bot enabled (uncheck to pause all auto-replies)

Messages

Welcome message (first "hi") Fallback message (AI error) Human hand-off keywords (comma separated) Hand-off message

Meta / WhatsApp Cloud API

Phone Number ID WhatsApp Business Account ID Webhook verify token Default country code (used when a number is typed in local format, e.g. 880 for Bangladesh)

Access token is stored as a Cloudflare secret WHATSAPP_TOKEN (never in the browser).

Set/rotate it with: npx wrangler pages secret put WHATSAPP_TOKEN --project-name q-active

Webhook configuration

In Meta for Developers → your app → WhatsApp → Configuration:

Callback URL

Verify token

Subscribe to the messages webhook field.

Send a test message

Free text Template (works outside the 24h window)

Why does "✓ Sent" not always arrive on the phone?

Test/unverified number: while the Meta app is in Development mode, the phone number can only message recipients added to the allowed recipient list (Meta → WhatsApp → API Setup → "To").
24-hour window: a free-text message is only delivered if the customer wrote to you in the last 24h. Otherwise you must use an approved template.
Wrong format: numbers must be international without "+" or leading 0 (e.g. 8801785466804, not 01785466804). The form fixes this automatically.
Payment method / business verification missing on the WABA.
The real reason is reported by Meta in the delivery status shown above and in the Logs tab.

Event log

Every webhook call from Meta (incoming messages, delivery statuses), every send attempt and every error — newest first.