Docs
Going live with the Udghatan SDK: pre-launch checklist
Pre-launch checklist for products built on the Udghatan SDKs: auth, error handling, the 10 messages per second default, opt-in, templates and monitoring.
Your frontend works in testing. Before real users arrive, run through this checklist. It covers the things that most often go wrong in the first weeks of a product built on the @ab-ecosystem SDKs and the Udghatan backend.
Copy the headings below into your issue tracker and assign an owner to each. A launch is ready when every item has been checked by someone other than the person who built it.
1. Authentication and access
- Sign-in, sign-up, 2FA, password reset and sign-out all work on every platform you support. If you use
@ab-ecosystem/sso, test each of its flows end to end. - Expired sessions are handled gracefully: the user is asked to sign in again, not shown a blank screen.
- Users can only see their own workspace's contacts, conversations and data. Test this with two separate test workspaces.
- No secrets are bundled into the web or mobile app. Search your build output for tokens and keys.
- You've checked the licence of every package you ship.
2. Error handling
- Every SDK call has a visible failure state. Users see a clear message and, where it makes sense, a retry option.
- Network loss and slow connections are handled, especially on mobile.
- Errors are logged with enough context to debug (what was attempted, when, for which workspace), without logging personal data or tokens.
- WhatsApp-specific failures are explained in plain language: template not approved, contact outside the 24-hour window, insufficient recharge balance.
3. Sending speed and volume
Accounts send at 10 messages per second by default.
- Bulk sends and campaigns are queued and paced, not fired all at once.
- Your UI sets expectations for large sends. At 10 messages per second, 36,000 messages take about an hour.
- If your customers need more speed, discuss it with the partnerships team before launch.
- Remember Meta also applies messaging limits per WhatsApp number, based on quality rating and history. Pacing alone doesn't raise them.
4. Opt-in and compliance
- Your product makes it easy for businesses to record where and when each contact opted in.
- Contact import screens remind users to import only opted-in contacts.
- Marketing messages include a way to opt out, and opt-outs are respected.
- Your marketing and in-app copy avoid claims you can't support, such as compliance certifications, "no ban" guarantees or that Udghatan grants the verified badge (Meta grants it).
5. Templates and the 24-hour window
- Business-initiated messages outside the 24-hour customer service window can only be sent with an approved template. Your UI prevents or clearly explains anything else.
- Users can see template status (pending, approved, rejected) and the reason for a rejection.
- Template variables are validated before sending, so customers never receive a message with an empty placeholder.
6. Charges and billing
- Your pricing page explains that WhatsApp message charges are separate from your subscription. You get B2B flat Meta rates, so you can set and publish your own per-message prices.
- Your billing to your own users is set up and tested.
- You've chosen your partner fee (monthly or one-time) and the per-account plan for your customers. See SDK pricing.
7. Monitoring
- You have error tracking on your frontend and server, and alerts reach a person.
- You can see key numbers daily: sign-ins, messages sent, send failures, active workspaces.
- You have a status or announcement channel to tell users about problems.
- You know how you'll roll back a bad release, including app store releases if you ship mobile apps.
8. Support handoff
As an SDK partner, you provide first-line support to your users.
- Your support channel, hours and response times are published.
- Your support team has a help page covering sign-in, connecting channels, templates, recharge and campaigns.
- You know how to escalate to Udghatan and what to include: workspace, what was expected, what happened, timestamps with time zone, error messages and screenshots.
- Your team understands which issues only Meta can resolve, such as template rejections and business verification.
9. Launch plan
- Soft launch with a handful of friendly customers.
- Watch closely for a week: errors, support questions, send failures.
- Fix and document what you learn.
- Open up to everyone.
Next step
Tell the partnerships team your launch date on WhatsApp so they know what's coming. Need a refresher? Revisit the SDK overview or the SDK catalog.