AI and integrations

Run WhatsApp reception with a clear human handoff

Set a safe boundary between automated replies and staff handling, then verify the displayed conversation state.

7 min readReviewed 2026-09-12

Key takeaways

• WhatsApp setup, message delivery and human handoff are separate observable states.
• Handoff policy should match the controls and role permissions actually shown in the inbox.
• Unknown delivery results require inspection before retrying.

Connect the intended channel

Open WhatsApp and follow the setup route displayed for the account. It may show Connect with WhatsApp or request provider credentials. Read the prerequisites, enter only requested information and wait for the connection state. A saved credential or a setup screen is not evidence that a customer message can be delivered.

• Keep provider credentials out of examples, tickets and shared notes.
• Read the number and connection state shown before any test.
• Use one allowed, clearly identified test number only after the owner approves it.

Define the handoff moment

A human handoff is an operational decision. Agree what staff should recognise in the conversation, such as a direct request for a person, an unresolved question or a situation your business has chosen to review manually. Use the handoff control shown in the inbox and respect role limits. Do not describe an unavailable control as if it were guaranteed for every channel.

• Review enough of the transcript to understand what the customer needs before taking over.
• Use a concise staff reply that acknowledges the request and states the next action you can actually take.
• Keep the automated and manual portions of the transcript distinguishable.

Test one controlled handoff

With permission, send one test message from the allowed number. First confirm that the conversation reaches the intended WhatsApp inbox. Then use the available handoff or manual reply control and confirm that the latest message or handling state changes. Record the conversation identifier or other safe reference, the state you saw and the time of the test.

• Check the correct inbox before assuming the message is missing.
• Wait for an observable state before sending another test.
• Review the customer-facing text before any reply that leaves the system.

Recover without creating duplicates

If the connection is saved but the test does not appear, recheck the displayed number, provider state and inbox. If a message is delayed, do not resend while delivery is unknown. If staff cannot take over, record the role, channel and displayed control state before changing credentials. Use Support with safe context rather than pasting secrets or a full customer transcript.

• Capture expected result, actual result and time in the support request.
• Do not infer delivery from a connected label alone.
• Keep the first conversation open while checking its state.

Examples

Example: the test reaches WhatsApp but the manual handoff control is absent for a staff role. Record that access boundary and ask an authorised owner to review it.
Example: the connection is saved and a test is delayed. Check the displayed status and inbox once; repeated sends could create duplicate customer messages.