Settingsbeginner

What is Returning Customer Detection?

When a customer who already has an open or recent conversation reaches out again, Atender asks whether it's the same issue or new — and either appends to their thread or starts a new one.

6 min read

What is Returning Customer Detection?

Returning Customer Detection prevents the most expensive failure mode in customer support: the same person, the same issue, three different conversation threads. When a customer who already has an open or recently resolved conversation contacts you again, Atender recognises them, asks one short clarification, and either joins the contact to their existing conversation or creates a new one. On Phone, an agent always confirms that join.

The result: one issue, one thread. Agents see the full history. Customers don’t repeat themselves. Conversation counts reflect real issues, not duplicate contacts.

How a returning contact is handled

  1. Detection — the customer is identified by phone number (Phone / SMS) or email address (Email, and Web chat, where it is the email address the visitor gives in the chat).
  2. Match — Atender looks for the customer’s unanswered or snoozed conversations, and for conversations resolved within a configurable lookback window (default: the last 24 hours).
  3. Clarification — the customer is asked, in their channel’s appropriate format: Is this about the same issue, or something new? On Phone this is a press-1 / press-2 prompt, and on SMS a text asking them to reply 1 or 2; on Email it’s a message asking them to choose. On Web chat, Atender asks only when the chat is handed to the team to answer by email: when it arrives outside the team’s opening hours, or when an Agent Stack hands it over. It sends the customer an email, and they choose by a link in it.
  4. Action — what a “same issue” answer does depends on the channel:
    Email and forms — the new conversation is merged into the matched one. With Auto-merge without asking on (Email tab), this happens without the question.
    Web chat — choosing “same” by the link in the email merges the chat into the earlier conversation.
    SMS — replying 1 adds the message to the matched conversation.
    Phone — the call always keeps its own conversation. Pressing 1 only records the earlier conversation as a merge suggestion: the agent sees Same issue as #… on the call. During the call, the agent can queue the merge with Merge… in the call popup; it runs when the call ends. After a call that an agent answered, the agent chooses Merge into #… on the marker. A call is never merged automatically.

A “new” answer starts a new conversation. If the customer doesn’t answer in time, the configured timeout action applies.

On Email, forms and Web chat, a “same issue” answer never merges into a conversation that an Agent Stack handles. On SMS, a reply of 1 adds the message to the matched conversation even when an Agent Stack handles it.

Cross-channel by design

Detection works across channels per identifier. A customer who emailed yesterday and calls today about the same issue is recognised, because the phone caller ID matched the email contact. The call runs on its own conversation, and the agent sees Same issue as #… with the email conversation. The agent merges the two after confirming it is the same issue.

  • Phone — Caller ID (phone number)
  • SMS — Phone number
  • Web chat — Email address the visitor gives in the chat
  • Email — Email address

What “recent” means

Each channel has its own Lookback window (default 1 day, set in days and hours). Conversations resolved within the window are eligible to match; older ones aren’t. Unanswered and snoozed conversations match while they are still active or snoozed, whatever the window is. The window is per channel because the right one is different — 1 day might make sense for phone and SMS, while some teams want 7 days for email.

Configurable triggers

You decide which previous-conversation states count as “the customer is returning.” Per channel, you can include:

  • Unanswered — they reached out before, didn’t get a response, and are reaching out again
  • Recently resolved — they got a response, the conversation was marked Done within the lookback window, and they’re following up
  • Snoozed — they have an open conversation that’s currently snoozed

Most teams enable all three for chat and email, and tune phone separately.

What happens if they don’t respond to the prompt

Real customers sometimes don’t answer the question. The timeout action decides what happens when the Response timeout passes without an answer:

  • Do nothing — The new contact stays a conversation of its own. On Phone, the call takes the no-match path of the phone menu.
  • Add to existing conversation — Treated like a “same issue” answer: on Email and Web chat the new conversation is joined into the matched one (never when an Agent Stack handles either), and on SMS the first text goes into the matched conversation. On Phone, the earlier conversation is only suggested to the agent as a merge, and the call takes the same-issue path. Safer when most returning customers are following up on the same issue.
  • Create new conversation — Treated like a “new” answer: the contact stays its own conversation, and on Phone the call takes the new-issue path. Safer when most contacts that look “returning” are actually unrelated.

Pick whichever default best fits your team’s pattern. You can change it per channel.

Why it matters

For high-volume teams with longer resolution times — anywhere a case can take days to resolve — customers naturally follow up. Without detection, every follow-up creates a new conversation, fragmenting context across threads. With detection:

  • One issue, one thread — agents see the full picture
  • No “can you explain again?” — the customer doesn’t have to retell their issue
  • Conversation metrics reflect real issues, not contact volume
  • Cross-channel handoffs are seamless — when a customer emails and then calls about the same thing, the agent sees the earlier conversation on the call and merges the two

Where to start

Tags

ConceptGetting Started