# Messaging Integration Go Live Readiness Checklist > Source: https://netray.co/tools/messaging-integration-go-live-readiness-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A launch checklist for ERP to WhatsApp, Teams or Slack integrations covering consent, throughput, failure handling, monitoring and support. ## Category developer ## Audience - IT manager - Integration developer - Project manager ## Tool **Kind:** checklist **Scoring Note:** Every critical item must be done before go live. Aim to complete at least 85 percent of the rest or record an owner and date for each gap. **Groups:** #### Accounts, templates and consent **Items:** **Text:** Business account verified and display name approved **Critical:** true **Text:** Dedicated sending number or identity, not a personal one **Critical:** true **Text:** All templates approved in the correct category and language **Critical:** true **Text:** Opt in captured, stored with timestamp and source **Critical:** true Opt out keyword handled and applied within one day Template variables tested with long, empty and special character values Messaging limit tier known and campaign schedule planned #### Throughput and failure handling **Items:** **Text:** Messages queued outside the ERP transaction **Critical:** true **Text:** Retry with backoff and jitter on 429 and 5xx only **Critical:** true **Text:** Idempotency key or message ID prevents duplicate sends **Critical:** true Dead letter queue with an owner and alert Burst test run at the largest expected batch size Digest mode available when many alerts arrive together Timeouts set on every outbound call #### Security and data **Items:** **Text:** Access tokens kept in a secrets store and rotated **Critical:** true **Text:** Webhook signatures verified on every inbound call **Critical:** true **Text:** Chat users mapped to ERP users before any action is allowed **Critical:** true No sensitive ERP data in message text beyond what is needed Write back to the ERP checks authority and is logged Message logs retained per your retention policy and access controlled #### Monitoring and support **Items:** **Text:** Delivery, failure and latency dashboard live **Critical:** true Alert when failure rate or queue depth crosses a threshold Template quality rating monitored Named support owner and escalation path Runbook for token expiry, template rejection and provider outage Users told how to stop messages and who to contact #### Launch and rollback **Items:** **Text:** Pilot group tested in production with real devices **Critical:** true **Text:** Kill switch to stop all sends without a code change **Critical:** true Fallback channel defined for urgent messages Cost alerts set against monthly budget Post launch review scheduled after two weeks Business owner has signed off on message wording ## Content **Intro:** Chat integrations look finished in a demo and fail in production on throttling, duplicate sends, missing consent or an expired token. This checklist covers the items that usually decide whether a WhatsApp, Teams or Slack integration survives its first month. **Sections:** #### How to use it **Body:** Run the list as a go live review with the developer, the ERP owner and the business owner in the same meeting. Tick items only when you can show evidence, such as a test log, a screenshot of the dashboard or a signed approval. Critical items are those where a miss causes a policy breach, a security exposure or a message flood. Export the result and attach it to your change record. **Bullets:** - Require evidence for each tick - Assign an owner and date to each gap - Repeat the review after major template or API changes #### What the groups cover **Body:** Accounts and consent keep you within platform and privacy rules. Throughput and failure handling prevent duplicate or lost messages when the provider throttles or has an outage. Security covers tokens, signature checks and identity mapping, so a chat button cannot be used to approve something the person has no authority for. Monitoring ensures that you hear about failures before users do. Launch and rollback gives you a way back. #### Common mistakes **Body:** The most common gap is no kill switch, so a looping ERP event sends thousands of messages before anyone can stop it. The second is storing opt in as a flag without a timestamp or source, which is useless if challenged. The third is testing only on emulators and not on real phones with poor connectivity. None of these takes long to fix before launch and all of them are painful after. **Bullets:** - Test the kill switch before launch - Store consent with time, source and wording shown - Test on real devices and slow networks **Cta:** If you want a second pair of eyes on an ERP to chat integration before launch, or a build that already covers these items, Netray can help. **Faq:** #### Is this specific to WhatsApp? **Answer:** Most items apply to any chat platform. WhatsApp specific items such as templates and messaging limits can be skipped for Teams or Slack, while consent and security items still apply. #### Which items are really critical? **Answer:** Consent, duplicate prevention, secret handling, signature verification, identity mapping and a kill switch. A miss on any of these can cause legal, financial or operational harm quickly. #### How long does the review take? **Answer:** About an hour if evidence is ready. If you spend longer, that usually means the monitoring or runbook items were not built yet. #### Should I repeat it? **Answer:** Yes, after any change of provider, template category, API version or approval flow, and at least yearly. ## Search terms whatsapp integration go live checklist, teams bot launch checklist, slack integration readiness checklist, chat integration testing checklist, erp notification go live, messaging api production checklist --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json