What this guide covers
Everything to verify before going live.
Workspace setup Business profile is accurate. Timezone is correct. Admins and agents have the right roles. WhatsApp setup Connection status is healthy. Phone number is connected. Webhook is subscribed or healthy. Templates sync successfully. Content and contacts Campaign templates are approved. Contacts include country code phone numbers. Opt-outs are excluded. Audience size matches campaign intent. Team readiness Confirm who owns Inbox replies, campaign monitoring, and support ticket escalation after launch. Billing and limits Review AyuChat plan limits and Meta WhatsApp/WhatsApp Business Platform charges before sending high-volume campaigns. Meta policies, pricing, and limits can change, so use the live provider dashboard for final provider billing decisions. Final test Go live only after: one internal template send, one reply, one campaign draft, and one support ticket flow have been tested.
Before you begin
- Sign in to AyuChat and confirm the correct workspace is selected.
- Use a role with access to Start here.
- 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 Start here area at /admin/dashboards. 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. |