E-commerce
July 1, 2026
A account merger can resolve a duplicate, but it can also create a problem if orders, loyalty points, subscriptions, or personal data seem to disappear or get mixed up.
The chatbot must identify the affected accounts, explain what can be merged, verify identity, and escalate cases where history, privacy, or an ongoing order is at stake.
This guide shows how to handle account merger errors without exposing customer data.
Summary
Why is a account merger delicate?
Two accounts can belong to the same customer, but they can also share a name, an address, or a phone number without being the same person. Merging too quickly can expose orders or private data.
The chatbot must therefore remain cautious. It can help understand the issue, but it must not merge or reveal histories without verification.
Merging accounts is merging trust, not just emails.
Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion
Empowering 200+ e-commerce merchants
Which situations to recognize?
Common cases are two accounts with two emails, a guest account, an account created via social media, a typo, separate loyalty points, a subscription on the old email, or a missing order after merge.
The bot must also recognize an already completed merge that has moved or hidden important information.
What information should be collected?
The bot can collect the relevant emails, order numbers, loyalty program, subscription, creation channel, approximate date, and the observed issue.
It must avoid asking for passwords, sensitive documents, or payment information in the chat.
How to explain what can be merged?
Depending on the system, it may be possible to merge order history, addresses, loyalty points, or preferences. However, some data may not be automatically mergeable.
The chatbot must explain that the merge depends on technical and security rules. A human verification is often necessary.
How do you manage errors after merging?
If the customer reports a missing order, lost points, a missing subscription, or incorrect data, the bot must collect the evidence and transfer it with an accurate summary.
It must avoid promising a full restoration before the team has verified the logs and the affected accounts.
Which flow to follow?
The flow must protect the data before correcting.
Identify the accounts, emails, orders, subscription, loyalty, and the issue found.
Verify if the request concerns a desired merge or an error after merging.
Explain the possible limitations: non-mergeable data, verification, and processing times.
Collect useful proof without asking for unnecessary sensitive data.
Transfer missing orders, lost points, mixed data, and sensitive merges.
Which messages should be used?
As a precaution: "Before any merger, it must be verified that the accounts indeed belong to the same person."
As a limitation: "Some information may require manual correction or may not be automatically mergeable."
For transfer: "I am forwarding both emails, the relevant orders, and the observed issue to support."
When to transfer?
Transfer is necessary if a merge is requested, if a merge has created an error, if orders or loyalty points are missing, if data seems to be mixed up, or if identity needs to be verified.
The bot must transmit emails, orders, desired main account, relevant history, evidence, requested action, and privacy risk.
Which KPIs should be monitored?
Track merge requests, post-merge errors, missing orders, recovered points, duplicate accounts, resolution times, and avoided privacy incidents.
These indicators show whether account management is understandable and secure.
Which mistakes should be avoided?
Avoid merging without verification, revealing the existence of a third-party account, promising a full recovery, or treating a mixture of data as a simple display bug.
The chatbot must protect privacy before seeking convenience.
How can Qstomy help?
Qstomy can connect the chatbot to quotes, orders, customer accounts, security rules, privacy procedures, email changes, account merges, and support teams to answer clearly, then transfer sensitive cases with an actionable summary.
The chatbot helps the customer move forward without inventing a custom price, an effective deletion, an identity verification, a proof of hacking, or a data merger that still needs to be confirmed by a reliable and secure source.
Explore AI support, the AI sales agent, or request a demo.
Key takeaways
Key Takeaways
Account merge errors must verify identity, emails, orders, loyalty, subscriptions, and the risk of mixed data.
What the customer must understand
The customer must understand what can be recovered, corrected, or submitted for human validation.
The chatbot's correct limit
The chatbot can collect the context, but it must transfer any merge, history error, mixed data, and sensitive verification.
Enzo
July 1, 2026
