WhatsApp (Twilio)

Q: How does inbound WhatsApp work?

Inbound WhatsApp messages are authenticated, mapped to your workspace identity, and processed by the same assistant experience used in the dashboard.

Q: What are proactive WhatsApp sends and how are they limited?

Proactive WhatsApp sends follow opt-out rules and plan-based monthly limits. See the pricing page and in-app usage panels for your current allowance.

Q: How do STOP, START, and related keywords work?

Standard opt-out keywords are supported for compliance. START can re-enable proactive messaging where your policy allows.

Q: What compliance records exist when I link WhatsApp?

CloudyBot tracks consent, opt-out status, and usage events needed for channel operations and policy support.

CloudyBot’s WhatsApp channel supports secure inbound messaging, outbound delivery, and user-linked conversations from your workspace.

Use cases

Chat from your phone: Ask your assistant on WhatsApp and continue work across channels.
Scheduled updates: Send reminders, reports, and task outcomes when proactive delivery is enabled.
Operational alerts: Pair with scheduled duties or internal workflows that should ping a human on a known WhatsApp thread (subject to plan limits and opt-out).

WhatsApp is not on the Free tier for product positioning on the public pricing page; paid tiers include a published monthly proactive send allowance.

Setup flow

Operator: Enable WhatsApp and channel credentials in your deployment.
Connect: Link your sender and validate channel setup in dashboard integrations.
User: Complete the in-app flow to claim and link a WhatsApp number to an account.
Auditability: Consent and channel state are tracked for operations and troubleshooting.

Plan-based proactive send cap

Proactive outbound WhatsApp is metered per user and billing period by your plan. Refer to Pricing and in-app usage for your current limits.

Compliance, opt-out, and inbound keywords

Proactive footer: Proactive sends include clear opt-out language.
Opt-out keywords: Standard unsubscribe commands are supported for compliance handling.
Policy controls: Opt-out state is enforced before proactive delivery.
Metering: Proactive usage is counted toward your monthly channel allowance.

For legal and policy requirements, apply your organization’s compliance review before production rollout.

FAQ

How does inbound WhatsApp work?

Inbound WhatsApp messages are authenticated, linked to your CloudyBot workspace identity, then processed through the same assistant experience used in the dashboard.

What are proactive WhatsApp sends and how are they limited?

Proactive messages are controlled by opt-out rules and plan-based limits. Use Pricing and in-app usage to confirm your current allowance.

How do STOP, START, and related keywords work?

Standard unsubscribe keywords are supported, and START can re-enable proactive messaging where policy permits.

What compliance records exist when I link WhatsApp?

CloudyBot stores consent, opt-out state, and usage records required for channel operations and troubleshooting.

Link WhatsApp from the dashboard when your workspace has the channel enabled.

Open dashboard

Review plan limits before relying on proactive volume.