What this guide covers
Understand the two separate cost components.
AyuChat subscription Your AyuChat plan covers platform access, workspace features, team seats, automation, inbox, analytics, API access, and support according to plan limits. Meta message charges WhatsApp Business Platform charges are controlled by Meta. AyuChat may show estimates where current provider data is available, but Meta remains the authority for provider message charges. Categories and rates Meta policy, pricing categories, free tiers, and regional rates can change. Review Meta Business Manager and current Meta documentation before high-volume campaigns. Tracking invoices Review AyuChat subscription invoices in Billing & Usage and Meta WhatsApp charges in Meta Business Manager. These records are separate and may have different billing windows. Common questions If AyuChat usage and Meta charges differ, compare message counts, recipient countries, template categories, failed sends, and Meta's billing windows.
Before you begin
- Sign in to AyuChat and confirm the correct workspace is selected.
- Use a role with access to Billing and subscriptions.
- Keep real customer data, API keys, payment details, Meta tokens, OTPs, and passwords out of screenshots and support messages.
Where to find it in AyuChat
Open the customer SaaS app and navigate to the Billing and subscriptions area at /admin/billing. If the page is unavailable, review your role permissions, active workspace, and plan access.
Recommended workflow
- Start with a small controlled test in the active workspace.
- Review the visible status, validation messages, and saved data before using the feature for real customers.
- Check related logs, analytics, or delivery state when the action depends on WhatsApp, automation, integrations, billing, or webhooks.
- Document any non-secret identifiers needed for support, such as record id, invoice number, campaign name, or timestamp.
Verify the result
- The expected record, status, or configuration appears after refresh.
- No page shows a blank screen, auth loop, CORS error, or unexpected server error.
- The result belongs to the selected workspace only.
- Any customer-facing message uses approved templates and consented contacts where required.
Common problems
| Problem | What to check |
|---|---|
| Feature is missing or disabled | Confirm role permission, plan entitlement, and active workspace. |
| Data looks incomplete | Refresh the page and verify the workspace switcher before assuming records are missing. |
| Action fails validation | Review required fields, connected WhatsApp state, template approval, file type, or billing state depending on the feature. |
| External provider behavior differs | Check the current provider dashboard or official provider documentation for policy, billing, or review-state changes. |