Start with a useful reason
Recovery can help continue an eligible abandoned enquiry. Decide what the follow-up offers: a way to resume the conversation, clarify a need, or take a relevant next step.
Do not assume that everyone who leaves your website should receive a message.
Configure permission and wording
Review the consent settings and the wording presented in the chat. Configure recovery message templates that describe the real reason for contact.
Providing an email address and agreeing to optional follow-up are different decisions. Respect the recorded consent state.
Understand the stop conditions
The recovery flow includes eligibility and stop rules. Test cases where a visitor resumes, declines contact, or no longer needs the conversation.
Recovery depends on the separately hosted API, worker, and email configuration. Publishing a website alone does not activate a functioning follow-up service.
Review the whole experience
Read the actual message a visitor receives and follow its links on a test enquiry. Check that a resumed conversation contains the right context.
Keep follow-up deliberate and relevant. Ask our team about the available settings if you need a specific business process.
Features depend on your connected services and tenant configuration. Ask our team about your setup.