Build handoff into the flow.
Some questions need a decision, an availability check or a conversation with your team. Make that route explicit. A handoff pauses automation and presents the support route configured in the saved flow, such as a phone number, email address or booking link.
Explain the next step.
Tell customers how to reach the right person and what they need to do. Do not say that someone has been notified unless your actual setup provides that behaviour. The website’s fictional example demonstrates a support route without contacting anyone.
Use captured messages for visibility.
The workspace provides a read-only view of captured messages. It is not a manual reply composer and does not import a complete historical WhatsApp conversation archive. Agree the team’s actual support process as part of setup.
Understand the visibility window.
Captured messages are visible for 30 days. Expired records are cleaned up during later inbox or webhook activity, so that visibility window is not a promise that every stored record is physically erased at an exact deadline. The privacy policy describes retention and provider limitations.
Keep control of automation.
Review the flow when customer questions or support arrangements change. Each business has its own assignment and controls, including the ability to pause replies. For questions about retained data, contact Spreadle using the data-deletion instructions.