Configure Returning Customer Detection
Detection is configured per channel because each channel asks differently — Phone with a press-1 / press-2 prompt, SMS with a reply of 1 or 2, Email and Web chat with a choice email — and the right time window is rarely the same across all of them.
Before you start
- A user role with admin access
- A clear sense of how long a typical conversation in your team takes to resolve — that’s roughly the lookback window you want
Steps
- Open Settings → Returning customers.
- You’ll see a tab for each channel that supports detection: Phone, SMS, Email, Web chat. Click the channel you want to configure.
- Set the per-channel options:
- Enable for this channel — Master switch for this channel. — Off
- Unanswered conversations — Matches when the customer has an open conversation that no agent has replied to yet. — On
- Recently resolved conversations — Matches when the customer had a conversation that was resolved within the lookback window. — On
- Snoozed conversations — Matches when the customer has a conversation that an agent has snoozed. — On
- Lookback window (days and hours) — How far back to look for a recently resolved conversation. Unanswered and snoozed conversations match while they are still active or snoozed, whatever this window is. — 1 day
- Response timeout (minutes) — How long Atender waits for the customer’s answer before it runs the timeout action. On Web chat, it is how long the link in the choice email can still join the chat to the earlier conversation. — 60
- Timeout action — What happens if the customer doesn’t answer in time: Do nothing, Add to existing conversation or Create new conversation. See What the timeout action does. — Do nothing
- Custom prompt message — The clarification message the customer sees on this channel. On Email and Web chat it replaces only the first sentence of the choice email; the subject and buttons stay fixed. Not shown on the Phone tab: callers hear the prompt set on the Returning Customer node in the IVR flow. — (channel-specific default)
- Auto-merge without asking — Email tab only. Skip the prompt and merge email and form contacts automatically when there’s a clear match. — Off
-
Phone has two extra options:
Skip IVR for returning callers — when the caller presses “same issue”, skip the rest of the phone menu and send them straight to the first queue on the same-issue path. If that path has no queue step, the menu runs as built.
Priority queue placement — needs Skip IVR for returning callers. Callers who skip the phone menu go to the top of that queue, ahead of every caller who did not. -
Customize the prompt message if your default voice would say it differently. The defaults are sensible starting points but the customer reads this — make it sound like you. On Phone, change the prompt on the Returning Customer node in the IVR flow instead.
- Click Save.
What the timeout action does
The timeout action runs when the customer doesn’t answer within the response timeout.
- Phone (the caller presses nothing) — Records the earlier conversation as a merge suggestion on the call and takes the same-issue path. The call is not merged automatically, and Skip IVR for returning callers does not apply. — Create new conversation takes the new-issue path; Do nothing takes the no-match path. The phone menu then goes on as built.
- SMS (no reply of 1 or 2) — Puts the customer’s first text in the earlier conversation. — Puts the first text in a new conversation.
- Email and Web chat (the choice email is not answered) — Joins the new conversation into the earlier one, as a “same issue” choice would. Never when an Agent Stack handles either conversation. — The new conversation stays its own conversation.
Verify it worked
For each channel you enabled:
- Make a test contact from a customer record that has a recent conversation
- Confirm the prompt appears in the channel-appropriate format
- Pick “same issue” — on Email, SMS and Web chat, confirm the contact joins the existing conversation. On Phone, confirm the call keeps its own conversation and shows Same issue as #…; during the call the agent can queue the merge with Merge… in the call popup, and after the call the agent merges it with Merge into #…. A call is never merged automatically.
- Repeat with “new issue” — confirm a new conversation is created
If the customer doesn’t see a prompt at all, check the lookback window (a resolved conversation might be older than the window) and the trigger toggles (the previous conversation’s state — unanswered / resolved / snoozed — has to match an enabled trigger).
Choosing the right defaults
A few patterns most teams converge on:
- Phone: lookback window 1 day, Unanswered conversations on, Skip IVR for returning callers and Priority queue placement on. Returning callers usually mean “I called before about this” and getting them past the IVR is high-value.
- Email: lookback window 7 days. Email cases stay open longer and “the same issue, days later” is the most common returning case.
- Web chat: Atender asks only when a chat is handed to your team to answer by email, with a link in a choice email. The response timeout is how long that link can still join the chat to the earlier conversation; after it passes, the timeout action runs.
- SMS: lookback window 1 day. Mirrors phone but the prompt has to fit in an SMS, so keep the message short.
Disabling for a channel
Turn the Enabled toggle off and save. New contacts on that channel always create new conversations until you turn it back on. Configuration values are preserved, so re-enabling restores everything.
Troubleshooting
-
Symptom: No prompt appears for any returning customer. Fix: Check that Enable for this channel is on in Settings → Returning customers and that at least one trigger is on (unanswered / recently resolved / snoozed). Without an enabled trigger, no previous conversation matches.
-
Symptom: The lookback window is set but customers from longer ago still get prompted. Fix: The lookback window limits only Recently resolved conversations. An unanswered or snoozed conversation matches however old it is, while it is still active or snoozed. If the match is a resolved conversation older than the window (for example 3 days old with a 1-day window), capture the customer ID and a sample conversation and escalate.
-
Symptom: Auto-merge without asking is merging unrelated emails into old conversations. Fix: Turn Auto-merge without asking off on the Email tab. Auto-merge skips the customer’s own clarification — only safe when your thresholds are tight and false positives are rare.