E-commerce
July 1, 2026
A customer who believes their account has been hacked is often anxious: an unknown order, a changed password, a modified email, used loyalty points, or a suspicious delivery address. In this moment, a slow or confusing response increases fear.
The chatbot must help secure the situation without exposing further data. It can recognize warning signs, guide toward initial actions, and quickly transfer to the authorized team.
This guide explains how to manage a suspected hacked account with an AI chatbot, combining reassurance, caution, and escalation.
Summary
Why is this topic urgent?
A hacked account can allow an unauthorized person to view personal information, place an order, modify an address, or use store credit. The risk is therefore both financial and personal.
The chatbot must treat these requests as high priority. It must not ask the customer to wait without a clear action, nor display account details before verification.
When a customer reports an intrusion, the chatbot's first mission is to limit the risk, not to resolve the entire investigation in the chat.
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 signals should be recognized?
Frequent signals are an unknown order, an unrecognized login email, a modified address, a password that no longer works, a used gift card, or expired loyalty points.
The bot must also recognize less technical formulations: "someone is using my account," "I did not place this order," or "my address changed on its own."
How do you respond without exposing the account?
The chatbot must avoid displaying the full address, recent orders, or payment information until identity is verified. Instead, it can confirm that a securing request is being handled.
A good response clearly states what to do: change the password if access is still possible, check the email, do not share any codes, then wait for support for sensitive actions.
What actions should be proposed immediately?
The bot can advise to change the password, check the account's email address, check confirmation emails, secure the personal email address, and contact the bank if an unknown payment appears.
It must remain factual. It must not accuse, confirm fraud without proof, or cancel a sensitive order without a planned rule.
When should you block or transfer?
The transfer is essential if an unknown order exists, if the account email has changed, if a value has been used, if the customer no longer has access to the account, or if personal data appears to be exposed.
The summary must be precise: customer ID, reported issue, actions already attempted, concerned order, date, and urgency level.
Which flow to follow?
The flow must secure before investigating.
Recognize the suspicion of hacking or unauthorized access.
Avoid displaying personal data in the conversation.
Guide towards the first security actions.
Collect only the elements useful for verification.
Transfer quickly to the authorized team for blocking, investigation, or cancellation.
Which messages should be used?
To reassure: "I will help you secure the situation. To protect your account, I will not display any sensitive information here."
For an unknown order: "I am forwarding this order as suspicious so that the team can verify it quickly."
For lost access: "If you can no longer log in, I will direct your request to the secure recovery procedure."
How to manage evidence?
The customer may provide an email capture, an unknown order, or a bank alert. The bot should only ask for what really helps and avoid full banking details.
If proof contains sensitive information, the chatbot must direct to a secure channel or transfer to an agent.
Which KPIs should be monitored?
Track detected suspicions, security transfers, suspicious orders, recovered accounts, false positives, and conversations where the bot avoided exposing data.
These indicators show whether the chatbot spots risks quickly enough and if the procedure actually protects the customer.
Which mistakes should be avoided?
Avoid displaying account details, asking for a password, confirming fraud without verification, or processing a suspicious order as a simple delivery follow-up.
The chatbot must be reassuring, but above all, it must be cautious and quick to escalate.
How can Qstomy help?
Qstomy can connect the chatbot to support rules, customer context, and useful data to respond clearly, then transfer sensitive cases with an actionable summary.
The chatbot helps the customer move forward without exposing unnecessary data or making a decision that must remain human.
Explore AI support, the AI sales agent, or request a demo.
Key takeaways
Key Takeaways
A suspected hacked account must be treated as a priority and sensitive issue.
What the customer must understand
The customer must know what first steps to take and why some data is not displayed in the chat.
The chatbot's correct limit
The chatbot can guide and gather context, but it must transfer blocks, investigations, suspicious orders, and account recoveries.
Enzo
July 1, 2026
