E-commerce
June 30, 2026
"I ordered as a guest, I can't find my order anymore." "Why do I have to create an account?" "I have two accounts with the same email." These messages arrive every week. They are not product bugs: they are guest vs. customer account frictions poorly routed to support.
Baymard estimates that 19 to 26% of checkout abandonments come from a forced account creation (Baymard, checkout abandonment 2025). Shopify documents merging duplicate profiles and new customer accounts with a 365-day persistent session (Shopify, customer accounts).
This guide #293 covers guest vs. account operational support: taxonomy, macros, profile merging, guest lookup. It complements the customer account glossary, checkout bot (#292), and login errors (#294) from a daily customer service process angle, not AI automation.
Summary
Why does guest vs customer account generate so many tickets?
Guest checkout converts the first order. The customer account serves recurrence. In between, support receives misunderstood requests: the customer does not know if they have an account, where to view their order, or why they are being asked for a password.
Three common customer profiles
Pure guest: purchase without an account, looks for tracking via email
Latent account: Shopify profile created at checkout, never activated
Duplicate: 2 profiles (guest + account, or 2 emails)
Support cost
Ecomhint points out that about 19% of buyers abandon if an account is mandatory; hybrid guest + optional account stores limit this risk while capturing 20% to 30% of guest-to-account conversion post-purchase (Ecomhint, guest vs account 2026). Without a support process, every "I can't find my order" becomes 8 to 12 minutes of agent time.
DTC Example
Cosmetics, 680 orders/month of which 54% are guests: 89 tickets/month "account / order not found". After ACCT taxonomy + guest lookup: −38% volume, CSAT +0.4 pts.
How does it differ from the glossary, bot #292, and login #294?
Four related contents, four depth levels.
Customer Account Glossary
The glossary defines the customer account. Issue #293 deals withguest vs. account real tickets: verbatims, macros, admin merge.
Checkout Bot (#292)
Checkout Bot (#292): chk_acct_* in-funnel intents. Issue #293: post-purchase human support and processes, duplicates, account activation.
Login errors (#294)
Login (#294): password, OTP, locked history. Issue #293 sets the guest vs. account framework before these auth incidents occur.
General self-service
Self-service Guide: global portal. Issue #293 zooms in on guest lookup and Shopify profile merging.
Promise #293
ACCT taxonomy, guest lookup protocol, macros, duplicate merging, post-purchase activation, account ticket KPIs.
Which guest vs. account request taxonomy should be mapped?
Name each type with a stable code for Gorgias tags, macros, and reporting.
Guest (`acct_guest_*`)
acct_guest_wismo: order tracking without an accountacct_guest_return: guest purchase returnacct_guest_invoice: invoice or receiptacct_guest_edit: edit address post-orderacct_guest_create: create account after guest purchase
Account (`acct_reg_*`)
acct_reg_activate: activate account created at checkoutacct_reg_duplicate: 2 profiles for the same personacct_reg_merge_request: merge historiesacct_reg_email_change: change account emailacct_reg_delete: GDPR account deletion
Checkout (`acct_checkout_*`)
acct_checkout_forced, acct_checkout_confused, acct_checkout_shop_pay (Shop vs store account). Cross-reference with tagging conversations.
How to handle guest order lookup in 5 steps?
The guest order lookup is the most cost-effective process: 70% of "order not found" tickets are resolved without escalation.
ACCT-LOOKUP-01 Protocol
Collect: order email + number # or amount + date (min. 2 criteria)
Search Shopify admin Orders: email, status, guest tag
Verify light identity: last 4 digits of card or delivery zip code if sensitive data
Respond: tracking link, fulfillment status, ETA delay
Offer account: "Create an account with this email to find your orders" + activation link
ACCT-GUEST-WISMO Macro
"Hello {{first_name}}, order #{{order_number}} found ({{order_date}}, {{order_total}} €). Status: {{fulfillment_status}}. Tracking: {{tracking_url}}. For your future purchases, activate your account here: {{account_activation_link}}."
Limit cases
Guest email typo: verify amount + date before forwarding to another address. PayPal email ≠ checkout: search for both. See digital support for access to guest files.
What are the CS macros for guest, activation, and duplicate?
Six macros cover 80% of the guest account volume on a typical DTC store.
ACCT-* Library
ACCT-GUEST-WISMO: lookup + tracking + optional account link
ACCT-GUEST-RETURN: guest return portal (order # + email) + policy period
ACCT-ACTIVATE-01: "Your profile exists, click to set password / magic link"
ACCT-POST-PURCHASE: confirmation page "Create an account in 1 click to track without email"
ACCT-DUP-EXPLAIN: "2 profiles detected, merge in progress, history unified under {{email_kept}}"
ACCT-CHECKOUT-GUEST: "Order without an account: Continue as guest. Optional account after purchase."
Tone of Voice
Never make them feel guilty ("you should have created an account"). Validate: "That's normal as a guest, here is how to find your order."
Checkout Link
For questions during the analysis funnel, redirect to checkout bot (#292) or CHK-ACCT-01 macro.
How to merge duplicate customer profiles on Shopify?
A guest customer who later creates an account can have 2 Shopify profiles. Merging unifies orders, addresses, and tags.
Admin merge process
Open main profile (email to be kept)
Customers → Merge customer → select duplicate
Review Merged customer section: email, addresses, tags
Confirm → verify unified orders
Tag
acct_merged+ internal note with date and agent
Shopify details the rules: the profile with the kept email remains; conflicts cancel the merge (Shopify, merge customers). GraphQL API customerMerge for high volumes (Shopify Dev).
Merge limitations
Profiles with an active subscription, vaulted card, or B2B link: merge impossible. Escalate to ops or subscription app support.
Prevention
Guest checkout by default. Account activation post-purchase only. Magic link rather than password at checkout (MojoAuth, passwordless 2026).
How do I activate an account after a guest purchase?
Guest-to-account post-purchase conversion targets 20 to 30% of guests within 30 days if the journey is frictionless (Online Store News, 2026 A/B tests).
Recommended activation flow
Thank you page: "Track your order #1234" + CTA "Create my customer account"
Confirmation email: same CTA, benefits (history, returns, addresses)
Magic link or unique password: no long form
First login: current order pre-displayed
Ticket acct_guest_create
Customer writes after guest purchase: order lookup → confirm email → send Shopify Customer Accounts activation link or legacy account invite.
Shop Pay and Shop account
Customer logged into Shop Pay may confuse Shop account with shop account. Macro: "Your order is on {{store_name}}. Shop account speeds up checkout; order tracking: {{guest_lookup_url}} or customer account {{account_url}}."
Post-purchase onboarding
Link to post-purchase onboarding for first-time buyers with an activated account.
What self-service options are available for guests versus registered clients?
Self-service reduces tickets if both pathways are visible starting from the footer and the contact page.
Public guest lookup
Minimal form: order number + email → status + tracking. No password. Align with mobile-first support: responsive page, tap tracking link.
Shopify customer accounts
New customer accounts: 365-day session, self-service returns, reorder, auto-fill checkout addresses (Shopify). Support must understand the difference between legacy vs new accounts.
Pathway matrix
WISMO: guest lookup OR account login
Return: Loop guest portal OR account return
Order modification: often account + Order Editing app; guest = ticket. See order modification
Help center
Two distinct articles: "Track an order without an account" and "Access my customer space". Avoid a single vague article.
When to escalate and how to verify identity?
Guest and duplicate touch personal data: lightweight but consistent identity protocol.
Bot / L1 auto OK
Explain guest mode, send ACCT-CHECKOUT-GUEST macro, public guest lookup link, post-purchase activation help article.
Human required
Profile merge, order email change, third-party order access (gift), GDPR account deletion, conflict between 2 active emails, chargeback dispute.
Identity verification (3 levels)
N1: email + order number (standard WISMO)
N2: + delivery postal code or exact amount
N3: + last 4 digits of card (email change, merge)
Prohibited
Send order details to an unmatched email. Merge without explicit customer consent. See bot-to-human handoff.
Which KPIs should be tracked for guest account tickets?
Measure the ACCT process ROI, not just the overall ticket volume.
Monthly KPIs
Acct ticket rate: acct_* tickets / total orders
Guest lookup success: ACCT-LOOKUP-01 resolved without escalation
Merge volume: biennial merges / month + average agent time
Post-purchase activation: % guests → account within 30 days
Repeat rate guest vs account: 2nd order at 90 days
FCR acct: first contact resolution tags acct_bot_resolved
Quarterly review
Top 5 intents without macro → draft ACCT-*. Cross-reference weekly friction report. If acct_checkout_forced spikes: audit prominent guest checkout UX.
How does Qstomy reduce guest vs. account tickets?
Qstomy routes acct_* intents, runs guest lookup, and prepares merge with pre-filled profiles.
Capabilities
Intents acct_guest_wismo, acct_reg_duplicate, acct_checkout_confused. ACCT-* macros auto-filled from Shopify. Guest lookup bot (order # + email). Human handoff with duplicate profiles listed. Tag acct_bot_resolved.
DTC Scenario Case Study
DTC mode, 920 orders/month, 58% guest, 102 acct tickets/month (11% of orders). Qstomy deployment + 6 ACCT macros + optimized guest lookup page. After 10 weeks: acct tickets 102 → 64/month (−37%), guest lookup bot resolution 71%, duplicate merges −22 min/agent, post-purchase activation 18 → 26%, repeat rate of activated accounts +8 pts vs pure guest at 90 days.
See Shopify, AI support, demo.
Which playbooks should be used to structure guest vs. account customer service?
Playbook 1: ticket audit (2 h)
Export 90 days of "account", "guest", "order not found" tickets. Group into taxonomy section 3. Count volume by intent.
Playbook 2: ACCT macros (3 h)
Draft ACCT-GUEST-WISMO to ACCT-DUP-EXPLAIN. Test with 20 real verbatims. Shopify variables: order_number, tracking_url, account_activation_link.
Playbook 3: public guest lookup (1 d)
Order lookup page or app # + email. Footer link, confirmation email, bot macro. Mobile testing.
Playbook 4: duplicate merging (2 h)
Document process section 6. Train 2 lead agents. Systematic acct_merged tag.
Playbook 5: post-purchase activation (1 d)
Thank you page CTA + Day+0 email. Measure 30-day activation. A/B test benefit copy vs. dry "create an account".
Useful links
This week: export 15 "I can't find my order" tickets from this month. How many would have been resolved by ACCT-LOOKUP-01 in less than 3 minutes? If more than 10, deploy the macro before any other project.
Enzo
June 30, 2026
