WhatsApp Business Account - Conversational Automation API | Developer Documentation

Find where a WhatsApp prompt stops working

An ice breaker or command configured in WhatsApp Manager gives a customer a way to start a request. The reply or business action is configured separately in the connected CRM, help desk or custom service. Use this checklist when a prompt appears but the expected response does not follow.

Check the prompt and the selected number

1. Open WhatsApp Manager for the account and number connected to ChatArchitect. Compare the saved component with the exact prompt you are testing. The component setup guide covers configuration.
2. Open a direct new chat from a suitable test WhatsApp account and check the component there. A link with prefilled text can change the starting screen; test the direct chat separately.
3. Use the component and record the text actually sent, the business number and the time. A visible prompt and a completed business action are different checkpoints.

Follow the incoming message

Look for that request in the connected tool's conversation. For your own service, use the inbound-message example in the ChatArchitect API Quick Start. Check the receiver and conversation selected by your implementation; a delivery-status event for an outgoing message is a different event.

• If the request does not appear, verify the selected business number, connection and receiver before changing the reply rule.
• If it appears but no rule runs, compare the actual received text and conversation with the rule's conditions. Menu text, a command label and the conditions in a CRM are not automatically the same configuration.
• If the rule runs but the reply does not arrive, keep its outgoing message reference and check the sending result. Check the message type and service window used for that reply.

Retest the complete path

Change one relevant setting at a time, then repeat the same permitted test. Verify the request in the connected tool and the actual reply on the customer's phone. Confirm any automatic action with the owner of that workflow; saving a WhatsApp component does not establish a CRM automation.

For support, provide the component, selected number, test time, exact stage that failed and the available message reference. The supported rules and actions depend on the connected tool; this guide does not introduce a new Meta or ChatArchitect API endpoint.