Multi-tenant WhatsApp SaaS

Growth, support, and automation in one WhatsApp workspace

This greenfield implementation ships the platform foundation: agency-aware tenancy, shared inbox, campaigns, automations, analytics, admin support tooling, and Cloud API primitives under one monorepo.

Delivery rate

0%

Read rate

0%

Contacts

0

Open threads

0

Launch control

The workspace is wired around the production plan: official WhatsApp onboarding, full encrypted history, campaign scheduling, and role-aware operator experiences.

Workspace health

WABA connected with webhook verification, template sync, and phone throughput monitoring.

not connected
Retention policy

Full encrypted conversation history is enabled with legal hold overrides and admin audit coverage.

not configured
Billing posture

Razorpay subscription hooks are planned into the backend, while message billing remains direct with Meta.

no plan plan

Campaign readiness

Approved templates, audience segments, and CTA tracking are already modeled across the shared domain packages.

No campaigns yet

Create a campaign after a WABA connection, templates, and opted-in contacts are available.

What this scaffold already covers

These are the major implementation slices present in the repository foundation.

Tenant-aware domain model
Agency and business workspaces, workspace membership roles, billing plans, CRM records, conversations, and admin audit shapes live in shared TypeScript packages.
Official WhatsApp runtime primitives
The backend includes centralized Graph API versioning, webhook verification, normalized event parsing, connection lifecycle endpoints, and queue-friendly webhook intake.
Product-facing surfaces
The web app includes dashboard, inbox, contacts, campaigns, automations, analytics, onboarding, and settings pages so the implementation direction is visible immediately.