E-commerce
July 1, 2026
Changing an account's email seems simple, but it is a sensitive action. If a fraudster takes control of the login address, they can access orders, personal data, or loyalty benefits.
The chatbot can guide the customer, explain the procedure, and collect useful information. However, it must not modify the email without robust verification.
This guide explains how to automate help without compromising account security.
Summary
Why is changing the email address sensitive?
Email is often the primary identifier for the customer account. It is used to log in, receive order confirmations, reset the password, and prove the relationship with the store.
An poorly managed modification can lead to account takeover. This is why support must handle this request with greater caution than a simple change of delivery address.
The right balance is to help the real customer quickly, without opening an easy door to identity theft.
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
What is the difference with a forgotten password?
A forgotten password can often be resolved by an automatic link sent to the existing address. An email change is trickier, as the old address may be lost, hacked, or inaccessible.
If the customer still has access to the old email, the procedure can remain simple: confirmation sent to the old address, then validation of the new one. If they no longer have access, support must verify identity using other details.
The chatbot must therefore start with a clear question: "Do you still have access to the email address currently linked to your account?"
Which cases should the bot recognize?
The bot must distinguish between common situations: correcting a typo, changing a personal address, losing access to the old email, suspicion of hacking, or a request made by another person.
A typo right after an order does not have the same risk level as a customer who can no longer access their account and asks to replace the address. The chatbot must adapt the subsequent steps according to this risk.
If in doubt, it is better to transfer to a human rather than speeding through a sensitive modification.
What information should be collected?
The chatbot can prepare the file without requesting excessive data. It can collect the current address, the newly desired address, a recent order number, and a description of the issue.
It must not ask for a password, a bank code, or an identity document if this request is not provided for by a secure procedure. The information collected must be used solely to verify the account and forward the file.
The message must remain simple: "To forward your request, I need the current email of the account, the newly desired email, and a recent order reference if you have one."
Which security rules should be applied?
The bot must never change the email autonomously if the identity is not confirmed. It must also refuse requests made for a third party, except where explicitly provided for by procedure.
If the old email is accessible, confirmation via a link or code sent to that address is preferred. If the old email is inaccessible, a human must verify the request using additional elements.
Security must be explained without accusing the customer: "We must verify your identity before changing the email, as this address allows access to your account."
Which flow to follow?
The flow must be short and focused on security.
Ask if the customer still has access to the old email.
Identify the reason: typo, normal change, loss of access, or suspicion of hacking.
Collect the old email, the new email, and an order reference if necessary.
Explain that verification is mandatory.
Transfer to the human team if the old email is no longer accessible or if the risk is high.
Which messages should be used?
For a standard request, the bot might write: "I can help you prepare the modification of your email. To protect your account, we first need to verify that you are indeed the account holder."
If the customer still has access to the old email: "A confirmation can be sent to your current address before registering the new one."
If the customer no longer has access to it: "I will forward the request to our team so they can verify your identity using the available order information."
When to transfer to a human?
Human handoff is necessary if the old email is inaccessible, if the customer reports a hack, if the request concerns a high-value account, or if the information provided does not match.
The bot must transmit the full context: old email, new email requested, order number if applicable, reason for the request, and risk level.
A proper handoff prevents the customer from having to repeat the whole story and allows the agent to make a quick decision.
Which KPIs should be monitored?
Track the rate of requests resolved without unnecessary back-and-forth, the number of cases transferred for verification, the average modification time, and reports of suspected fraud.
An important indicator is the rate of incomplete files. If it is high, the bot is not collecting the right information or is explaining it poorly.
Which mistakes should be avoided?
The worst mistake is to modify the email solely because the customer requests it in the chat. You must also avoid asking for a password, giving details about anti-fraud checks, or confirming that an account exists to an unverified person.
Safe response: "I am forwarding your request for verification." Risky response: "Give me the new email, I'll change it right away."
How can Qstomy help?
Qstomy can recognize email change requests, collect useful information, and apply safeguards before any transfer.
The bot can distinguish a typo from a loss of access, prepare the case, and send sensitive cases to a human agent with the right context.
Explore AI support or request a demo.
ACCTEMAILbot Checklist (8 steps)
Sync ACCTEMAIL-MAP #825: RAG bot email account embed
Policy ACCTEMAILBOT-SUP: 6 rules NO-CHANGE VERIFY SCOPE NO-MERGE NO-THIRD
8 intents bot_acctemail_*: flow AEB-1 to AEB-8
4 templates TPL-ACCTEMAILbot-*: SCOPE VERIFY N3 TAKEN
Block edit API: bot role read-only customer no write permission
Red team 15 prompts: change now without third-party verification checkout typo auto merge
Account settings proactive: bot_acctemail_scope before form
Dashboard KPI: acctemail_bot_* section 9 auto_change_violations scope_cite handoff
FAQ
Difference #825?
#825 = agents execute change sync marketing. #826 = bot verification collect escalate tier 1.
Does the bot change the email?
No. ACCTEMAIL-NO-CHANGE-BOT. ACCTEMAIL825-HANDOFF-BOT humans AE-5 only.
Checkout typo?
bot_acctemail_order_confused ORDER358-REROUTE distinct account change.
No longer have access to old email?
bot_acctemail_n3 TPL-ACCTEMAILbot-N3 collect last4 before handoff.
Going further
This week: deploy ACCTEMAIL-MAP RAG account embed, red team auto_change_violations audit, sync bot_acctemail_verify proactive scenario N2 collect test.
Enzo
July 1, 2026
