🔄 Sequence Diagrams: Dedicated WABA
In the Dedicated WABA model, the Client natively owns their WhatsApp Business API (WABA) configuration through Meta's Embedded Signup (MES). Meta charges the client directly. Kloyst acts entirely as an integration SaaS.
1. Meta Embedded Signup (MES) Flow​
Explanation: Eliminates manual setup. Client injects permissions safely to the Kloyst backend database enabling routing directly to their individual Facebook Business Account.
2. Dedicated Template Approval​
Explanation: Same structure as shared, except the Rest Client utilizes the embedded System User tokens stored belonging to their tenant environment rather than the root Kloyst tokens.
3. Dedicated Campaign & Webhook Flow​
Explanation: Completely bypasses the pre-payment Wallet deductions. We simply dispatch via their WABA ID and increment a raw performance counter locally. No complex transactional locking over wallets required.
4. Usage Tracking & Monthly Invoicing​
Explanation: The SaaS usage is aggregated via PostgreSQL sums run as a scheduled CRON job mapping volume limits per their tiered plan directly onto invoices.