Choose one clear trigger.
Begin with an inbound message, an approved campaign, a booking event, or an event from a connected system. That trigger should start one traceable journey with the correct workspace, sender, contact, and business reference. Duplicate events should not create duplicate messages.
Match the message format to the customer's decision.
Use text and media for context, quick replies for a short choice, lists for a longer set of options, link buttons for a verified destination, and WhatsApp Flows for structured form input. Keep the customer's selection visible after they respond.
Decide what happens when a reply does not match.
An unexpected reply should lead somewhere useful. Ask a clearer question, take a safe configured branch, stop the journey, or route the conversation to a person with the active step and customer context.
Hand off without resetting the conversation.
The team inbox should preserve the thread, current flow state, structured answers, and the reason the workflow stopped. A person accepts ownership, replies, and resolves the exception in the same customer conversation.
Keep outbound messaging controlled.
Use approved templates, retain opt-in evidence, stop marketing after an explicit opt-out, respect quality and sender state, apply rate controls, and prevent retries from sending the same message twice. If the provider state is unsafe or unknown, the send should stop.
Add AI only where interpretation helps.
Deterministic flows can run without an AI provider. Optional AI can help interpret an open question or choose an approved next step, while fixed rules still handle consent, limits, handoff, and actions that must be repeatable.
Verify every external interface.
Check the connector page for supported actions, setup requirements, and limits. Connect your account and test the full task before using it with customers.