E-commerce
July 26, 2026
"I paid but I didn't receive anything." "Where is my confirmation email?" "I checked everywhere, nothing in my inbox." Three phrasing variations for the same ticket: the customer doubts that the order exists, even though the payment went through.
Shopify automatically sends the confirmation as soon as an order is paid (Shopify, order notifications 2026). Omnisend notes that these transactional emails have very high open rates when deliverability is correct, but a message in spam or an incorrect address immediately triggers a support contact (Omnisend, Shopify confirmation 2026).
This guide #358 covers the support resolution of the missing confirmation email ticket. It complements the transactional email glossary (definition) and message examples (#27) from the angle of customer service workflows, agent macros, deliverability, and post-checkout self-service.
Summary
Why does this ticket keep reappearing after checkout?
The missing confirmation email ticket arrives in the minutes following the purchase. The customer has no visible proof: they panic, dispute the payment, or open an urgent chat.
Five common triggers
Spam / promotions: Gmail classifies the confirmation in Promotions or Junk mail
Checkout email error: typo @gmail.com, non-existent domain
Perception delay: customer looks before receipt (30 s to 3 min)
Apple Hide My Email: relay alias, customer does not recognize the sender
Pending payment: unpaid order, no email confirmed
Tevello points out that if no confirmation was ever sent (email missing at checkout), the Resend option does not appear in the Shopify timeline (Tevello, resending confirmation 2026).
Angle #358
The transactional glossary defines the concept. #27 gives examples of email content. #358 formalizes the support workflow when the customer reports the absence: triage, resending, self-service, deliverability escalation.
Cost of a poorly handled ticket
Agent responds "check your spam" without looking up the order = 2nd ticket when the customer finds the email 10 min later. Or worse: early refund while the order is going into preparation.
DTC Example
Beauty brand, 142 missing_confirmation tickets/month out of 4,800 orders. After CONF-EMAIL policy + 8 macros: missing_confirmation_resolution 87%, median resolution time 4 min, "not received" chargebacks -38%.
Recommended SLA
P1 priority if message contains "paid", "debited", "scam". Response < 15 min with order status + link to status page or resend.
Typical Volume
On DTC without a visible post-checkout status page, expect 2 to 5% of post-purchase tickets related to confirmation or proof of order in the first year. Sharp drop once self-service and deliverability are corrected.
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
How does it differ from the glossary and examples #27?
Four post-purchase email contents, four distinct roles.
Transactional Glossary
Transactional email: definition, types, general deliverability. The #358 = precise CS ticket playbook "did not receive confirmation".
Message examples (#27)
Guide #27: subject, body, confirmation / shipping sequence. The #358: what to do when the customer says they have not received it.
Documents Bot (#255)
Invoices Bot (#255): order_confirmation_copy intent, PDF re-send. The #358 sets the human ops and policy foundation before the bot.
General support templates
Templates library: cross-functional macros. The #358 adds 8 dedicated CONF-EMAIL-* macros.
Post-purchase support (#9)
Post-purchase automation (#9): WISMO, tracking. The #358 = missing_confirmation sub-intent before shipping.
Duplicate tickets
Avoid duplicates: customer writes email + chat + Instagram. The #358 includes a channel anti-duplicate macro.
Promise #358
CONF-EMAIL policy, CONF-
Which causes should be classified before responding?
Mapping the missing_confirmation causes avoids generic responses and useless refunds.
Eight scenarios to tag
conf_spam_folder: email sent, customer did not check spamconf_typo_email: incorrect address at checkoutconf_delay_anxiety: email on the way, < 5 minconf_unpaid_pending: payment not capturedconf_guest_no_email: checkout without a valid emailconf_relay_alias: Hide My Email, iCloud relayconf_esp_fail: bounce, unauthenticated domainconf_never_sent: Shopify timeline without dispatch
Required ticket fields
order_id or checkout email, payment_status, timeline_email_sent (bool), customer_email_on_order, channel (email/chat/IG). See taxonomy (#135).
Distinction between confirmation vs invoice
Customer sometimes confuses order confirmation with PDF invoice. Clarify before resending: invoices (#254).
90-day ticket mining
Export verbatims "confirmation", "received", "proof", "scam". Prioritize macros based on the top 3 actual causes, not assumptions.
How to structure the CONF-EMAIL policy?
The CONF-EMAIL policy aligns agents, bot, and self-service FAQ.
Ten policy blocks
Check order before making any promise
Never refund without a confirmed unpaid status
Shopify resend if the timeline shows a previous send
Status page as a fallback if resending is impossible
Correct email on the order before resending if there is a typo
Guide spam: Promotions, Junk, Updates folders
Normal delay: up to 5 min, do not escalate before
Bounce ops: tag conf_esp_fail, technical escalation
Single channel: reply on the initial thread
CSAT: do not close before customer confirmation
CONF-EMAIL-GATE Flow
Five sequential gates: auth (email or order_id) → lookup payment_status → check timeline sent → branch cause (spam / typo / unpaid / never_sent) → action (resend, status link, email correction, ops handoff).
Unpaid branch
If payment is pending or authorized only: explain status, do not resend paid confirmation. Macro CONF-EMAIL-UNPAID.
Typo branch
Compare ticket email vs order. If different: ask for light proof of identity (last 4 digits of credit card or delivery address) before correcting contact.
Anti-duplicate rule
Which CONF-EMAIL macros for agents?
Eight CONF-EMAIL macros cover 90% of missing confirmation tickets.
CONF-EMAIL-RESEND-01 (standard resend)
"Hello, your order #[X] is successfully registered and paid. We have just resent the confirmation email to [email]. Also check Promotions and Spam folders. Status page: [link]. Delivery time: a few minutes."
CONF-EMAIL-STATUS-02 (link without resend)
"Order #[X] confirmed on [date]. Track your order here: [status link]. This page contains the same summary as the email. Need the invoice PDF? See invoice guide.
CONF-EMAIL-SPAM-03 (folder guidance)
"The email was successfully sent to [email] at [time]. Search for "[store name]" or "order #[X]" in all folders. Gmail: Promotions tab and Spam. Outlook: Junk email. Add orders@yourdomain.com to your contacts.
CONF-EMAIL-TYPO-04 (address correction)
"The email address on the order is [incorrect email]. To correct it, confirm the exact address and the last 4 digits of the card used. We will update it and resend the confirmation."
CONF-EMAIL-UNPAID-05 (pending payment)
"Your order #[X] is pending payment ([status]). The confirmation email is sent as soon as bank validation is received, within 24 hours max. If the charge is visible, send a screenshot of the statement: we will check with the bank."
CONF-EMAIL-DELAY-06 (immediate anxiety)
"Thank you for your order #[X] placed [N] minutes ago. The email can take up to 5 minutes to arrive. Here is your status page: [link]. Get back to us if nothing arrives within 15 minutes."
CONF-EMAIL-NEVER-07 (never sent)
"No email had been triggered (address missing at checkout). We have added [email] and manually sent the summary. Status page: [link]. Order in preparation."
CONF-EMAIL-DUPLICATE-08 (multi-channel)
"We are processing your request on this thread. Identical response sent via [channel]. Please do not reopen elsewhere for faster processing." Link duplicates.
Tone and personalization
Always include order number, payment status, and status link. Avoid using "this is normal" without lookup proof.
How do I enable post-checkout self-service?
The self-service confirmation deflects the ticket before it reaches an agent.
Visible order status page
Display a "View my order" link on the thank-you page and in the post-purchase header. Shopify generates a unique URL per order (Shopify, status page 2026).
Post-purchase chat widget
Proactive message 2 min after checkout: "Confirmation email on its way. Haven't received it? Click here to access your order." Status page button.
Checkout footer FAQ
"Where is my confirmation email?" with 3 steps: wait 5 min, check spam, status link.
Customer account
Invite account creation on the thank-you page: order history accessible without receiving an email.
Automatic bot resend
Intent order_confirmation_copy (#255): double auth, trigger resend Shopify API or status link. Limit of 2 resends / 24 hrs to prevent abuse.
Optional SMS
If phone number is collected: SMS "Order #[X] confirmed.
How to verify sending and deliverability on the ops side?
Recurring missing confirmation tickets often signal a technical issue, not a distracted customer.
Shopify Timeline Checklist
Open order → Timeline section
Look for "Order confirmation email sent"
If missing: conf_never_sent, correct contact
If present: Resend email under the timeline entry
"Send to yourself" option to test rendering
Shopify documents resending from the Timeline (Shopify, order details 2026).
Domain Authentication
SPF, DKIM, DMARC on sender domain notifications@. Without authentication, Gmail and Outlook send to spam. Test with mail-tester.com after each DNS change.
Recognizable Sender
"Store X" <orders@yourdomain.com>, not generic noreply@. Subject: "Order #4120 confirmed", never a disguised promo.
ESP vs Native Shopify
Klaviyo, Omnisend take over notifications: check delivered / bounced logs in the ESP. Correlate bounce with conf_typo_email.
Monthly Audit
Export 20 conf_esp_fail tickets. If > 5%: review template, heavy images, blacklisted links, subject spam score.
Post-Template modification test
How to configure Shopify and ESP to limit tickets?
The Shopify confirmation setup prevents more tickets than reactive macros alone.
Native notifications
Admin > Settings > Notifications > Order confirmation. Customize logo, colors, support link, and place a prominent status page link at the top of the body.
Optimal email content
Order number in subject and body
Status page link as a visible CTA button on mobile
Product summary + shipping address
Next step: estimated shipping time
Customer support contact: email or chat, not just a form
Shopify recommends order number, details, shipping, and next step (Shopify, order confirmation 2026).
Mandatory checkout email
Do not allow checkout without a valid email. Validate format on the theme side if needed.
Thank-you page
Message: "A confirmation email has been sent to {{ email }}. Check your spam folder if not received within 5 min." + status link.
Klaviyo / Omnisend integration
Disable double sending (native Shopify + ESP) which confuses the customer. Only one active transactional sender.
Multilingual markets
Localized template per Shopify market. "Email in English" ticket on FR store = conf_wrong_locale tag.
Which KPIs should be measured for a missing confirmation?
Without KPI missing_confirmation, it is impossible to prove ROI policy and deliverability.
Seven Key Metrics
missing_confirmation_volume: tickets / orders/month
missing_confirmation_resolution: resolved without escalation / total
conf_first_response_time: median minutes
conf_resend_rate: Shopify resends / tickets
conf_spam_cause_rate: % spam cause vs typo
conf_chargeback_prevented: disputes prevented post-response
CSAT intent missing_confirmation: dedicated satisfaction
DTC Benchmark
Target missing_confirmation_resolution > 85%, volume < 1% orders after 90 days optimized, conf_first_response_time < 10 min.
Deliverability Correlation
If conf_esp_fail rises after aggressive marketing campaign on the same domain: separate subdomain notifications vs news.
Monthly Review
Top causes, top customer email domains (Gmail, iCloud, Orange), adjust macros and self-service FAQ.
Weekly Dashboard
Segment by cause tag. A spike in conf_unpaid_pending = payment gateway issue, not customer service template.
What edge cases and escalations should be anticipated?
Six edge cases missing confirmation require a handoff or a special procedure.
B2B Order / PO
Pro buyer is waiting for confirmation + pro invoice. Route to the invoice macro if a PDF is requested, do not just resend confirmation.
Recipient Gift
Confirmation email goes to the buyer, not the recipient. Explain without revealing the gift content to the wrong person.
Fraud or Threatened Chargeback
Client threatens bank: reply within 15 min with proof of order, resend + status link + call offer if > €200.
Filtered Corporate Email
@company.com blocks external sender. Offer personal email or status link only, escalate to client IT if recurring.
Pre-order Without Capture
Deferred payment: "pre-order registered" confirmation, not "order shipped". Link pre-order (#337).
Multi-order Same Session
Client receives one confirmation, looks for the second. List all orders linked to checkout email over 24 h.
Post-purchase Email Modification
Edit contact information on the Shopify order, then Resend to the new address. Document in the ticket note.
How does Qstomy handle the missing confirmation email?
Qstomy routes the missing_confirmation intent using Shopify order lookup, policy CONF-EMAIL, and guided resend.
Capabilities
conf_order_lookup: payment status + timeline sent
conf_status_link: unique status page
conf_spam_guide: folder instructions by mail client
conf_resend_trigger: agent handoff for resend if needed
conf_unpaid_branch: pending explanation, no false confirmation
Quantified DTC Scenario
Skincare brand, 118 missing_confirmation tickets/month, slow manual responses.
After Qstomy + CONF-EMAIL policy: 82% auto-resolved, missing_confirmation_resolution 89%, conf_first_response_time 45s, CSAT 4.8/5.
Explore AI support, Shopify, book a demo.
What is the checklist for launching the CONF-EMAIL policy?
CONF-EMAIL Checklist (10 steps)
Audit missing_confirmation tickets for 90 days
Tag 8 causes in section 3
Draft CONF-EMAIL policy section 4
Import 8 CONF-EMAIL-* macros into helpdesk
Verify SPF/DKIM/DMARC domains for notifications
Optimize confirmation template + thank-you page
Activate post-checkout status page link
Train agents on CONF-EMAIL-GATE flow
Weekly missing_confirmation_resolution dashboard
Monthly causes + deliverability review
In brief
#358 = ticket resolution, not transactional definition
Order Lookup first: never just "check spam"
CONF-EMAIL-GATE: auth → payment → timeline → action
8 CONF-EMAIL macros: 90% of cases covered
missing_confirmation_resolution KPI: target > 85%
FAQ
Difference with transactional glossary?
Glossary = definition. #358 = customer service workflow when a customer does not receive the confirmation.
Difference with examples #27?
#27 = email content to send. #358 = how to reply to the "not received" ticket.
Should we refund if no email was received?
No, if the order is paid. Resend or provide the status link. Refund only if unpaid or if fraud is proven.
Shopify Resend is not working?
Timeline shows no initial send: correct the contact email, send status link manually.
Can a bot resend it automatically?
Yes, with double auth and resend limits. Hand off to agent if there is an email typo or bounce.
Going further
Test in staging: test order, mock "email not received" ticket, verify the lookup + CONF-EMAIL-RESEND-01 macro without useless escalation.
Share this #358 guide with support and email ops: a well-handled confirmation ticket reassures the customer in 4 minutes, not 4 interactions.
Enzo
July 26, 2026
