Pick your plan & sign in
Register, sign in through the browser, and attach a payment method or plan where your signup flow asks for it. Trial is capped and does not open the HTTP API or webhooks.
Governed WhatsApp for growing teams
Governed system for WhatsApp operations and automation
Link numbers you control with persistent sessions (including QR onboarding and reconnect). Operators work in the signed-in product; developers use authenticated HTTP routes and outbound webhooks on tiers that unlock them. We do not position Chattu as the official WhatsApp Business API.
Plan-checked limits · Starter: dashboard only (no API/webhooks) · Pro+: HTTP API & outbound webhooks · Session-linked WhatsApp
When WhatsApp is critical—but unmanaged
Sales, support, and notifications live on personal devices instead of accountable systems. Scripts break, SLAs slip, and growth adds more lines with no shared limits, billing alignment, or security posture. You still want the channel—without the chaos.
One hub for WhatsApp—in the browser and in your integrations
Persistent linked sessions (QR onboarding and reconnect), plans that enforce sends, automation budgets, contacts, webhook eligibility, and API access—operators use the signed-in product; integrations call authenticated endpoints only where tiers allow. Automation (rules within caps, personalization-aware templates, schedules, imports) aligns with those same sessions.
-
5,000+ production integrations
-
4.8/5 stick after trial
-
Your QR appears right after sign-in — no waiting, no confusion.
-
Rate limits & session reliability
How it works
Choose a plan, connect WhatsApp, set up automation—then work in the web app or plug in HTTP tools on the tiers that allow it.
Link WhatsApp
Create your client entry, scan the QR code when prompted, or restore an existing linked session—so WhatsApp reconnects cleanly after downtime.
Add automation
Build templates, import contacts where allowed, schedule messages, and set auto-reply rules inside your quotas. HTTPS webhooks to your URLs are optional and only appear on tiers that include them.
Dashboard—or your backend
Staff use chats, broadcasts, attachments, groups, and logs in the signed-in web experience. Developers call the authenticated HTTP endpoints when your subscription includes API access—both use the same linked WhatsApp session.
Keep it within limits
Your tier caps messages, linked numbers, automation, contacts, HTTP access, and webhooks—so expectations stay clear. Administrators get oversight and optional summaries; queued text sends are documented for setups where that option is enabled.
Inside the product
QR, templates, and status — laid out the way you’ll actually use them.
Scan to connect
Your QR appears right after sign-in — no waiting, no confusion.
Template builder
Hi {{name}}, your order is ready for pickup!
Variables, preview, send — your team speaks in one voice.
Inbox & status
Connected
Search chats
All
Unread
Mariana Costa
10:38
New lead · WhatsApp
Thanks! When can we talk?
James Okonkwo
Yesterday
Support queue
We’ll ship it tomorrow morning.
Priya Nair
Mon
Campaign · Blast
Opened: 842 · Replied: 61
Connection state stays visible so you’re never guessing.
What Chattu includes
HTTP tools where plans unlock them, operator automation, and clarity in your dashboard—all grounded in shipped capabilities.
Integrations (tier-gated)
REST send/receive pathways, client/profile style routes, API keys (account vs per-client on supported paths), validation, rate limiting, optional background text sends with job references when your environment enables the queue path.
Automation layer
Auto-reply rules within plan caps, templates with variable personalization, scheduled messages and contact storage within tier ceilings, optional bulk flows behind feature flags.
Operator experience
Signed-in access to settings, chats, messaging, clients, logs, templates, schedules, contacts; billing or subscription views when checkout is connected; API documentation access aligned with Professional-style entitlements; realtime session signals for linked numbers.
In-product visibility
Connection status, usage, and plan context your operators see in the dashboard; subscription summaries when billing is on; optional usage digests by email if you enable them.
Documentation reflects real routes
HTTP integrations use authenticated requests and per-route validation; availability depends on your plan.
- Routes, headers (including API keys), payloads, and rate limits are spelled out in the docs—not invented on this landing page.
- Starter and Trial plans do not include API access or webhooks; upgrade paths unlock those integration surfaces.
- Optional queued text sends and webhook behavior are documented for environments where they are enabled.
Plans that match shipped limits
Monthly message allowances, linked clients, automation caps, contacts—and where API keys & webhooks unlock.
Listed prices are examples; confirm totals at signup or checkout. Free tier is intentionally restrictive (no outbound quota); Trial excludes API/webhooks.
Free Trial
7-Day Free Trial
₪
0
/7 days
7-day onboarding window with bounded caps
- Up to 100 messages / month
- 1 linked client
- Up to 3 auto-reply rules
- Up to 10 scheduled messages
- Up to 50 contacts
- HTTP API access
- Outbound webhooks
Starter
₪
50
/month
Two numbers, predictable quotas—dashboard & automation only
- Up to 5,000 messages / month
- 2 linked clients
- Up to 10 auto-reply rules
- Up to 100 scheduled messages
- Up to 500 contacts
- HTTP API access
- Outbound webhooks
Most Popular
Professional
₪
150
/month
Adds HTTP API keys, outbound webhooks & priority support
- Up to 25,000 messages / month
- 5 linked clients
- Unlimited auto-reply rules
- Up to 1,000 scheduled messages
- Up to 2,500 contacts
- HTTP API access
- Outbound webhooks
- Priority support
Enterprise
₪
250
/month
Highest ceilings for sends, automation, contacts & linked clients
- Unlimited monthly messages (per plan encoding)
- Unlimited linked clients
- Unlimited auto-reply rules
- Unlimited scheduled messages
- Unlimited contacts
- HTTP API access
- Outbound webhooks
- Priority support
API routes and outbound webhooks require Professional or Enterprise. Trial mirrors product caps (no API/webhooks). Cancel policy follows your signup terms.
Questions teams ask first
- Is Chattu the official WhatsApp Business API?
- No—Chattu operates linked WhatsApp sessions and is upfront about that model. Messaging stays credible when you explain it plainly to stakeholders.
- Can I integrate on Starter or Trial?
- Programmatic routes and outbound webhooks unlock on Professional and Enterprise tiers. Trial inherits the bounded trial quotas and excludes HTTP API/webhooks unless you graduate plans.
- What happens for high outbound volume?
- Plan limits gate monthly throughput; optional background text enqueue is available only when documented infrastructure toggles are on. Check the docs for queue behavior and payloads.