E-commerce
July 1, 2026
“I never received my invitation.” “The link says invalid even though I just opened it.” “Can I transfer my access to my sister?” Three tickets where a poorly managed invitation-only sale shatters the perceived exclusivity and brand trust.
The DTC invitation-only sale support covers missing invitation emails, rejected link codes, expiration, incorrect address, and sharing policies. Distinct from private sales (#250) and members (#583): here, there is personal access with an guest list, a unique link or code, and no public password or loyalty tier.
This guide #593 covers policy INVITE-SUP, flows INV-1 to INV-8, and the INVITE-MAP matrix. The first customer service invitation content. Future customer service pair: INVITE bot (#594).
Summary
Why do invitation-only sales generate tickets?
An invitation-only sale promises exclusivity: you are on the list. When the email does not arrive, the link expires, or the code is rejected at checkout, the customer feels unfairly excluded. The ticket is emotional because access was supposed to be a personal privilege.
Five typical invitation frictions
Missing invitation: email in spam or never sent
Invalid link: token expired or already used
Code rejected: invitation code refused at checkout
Wrong address: invitation sent to a different email
Sharing requested: transfer of access to unauthorized third party
Atelier notes that identity-based invitation sales reduce leaks compared to public passwords but require synchronized resend and list verification (Atelier, private sales Shopify 2026). Without INVITE-MAP, agents send links at random or promise access outside the list.
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
INVITE #593 vs private sale #250, MEMSALE #583, XDROP #559 and bot #594
Five contents, five distinct exclusive access models.
Quick matrix
#593 INVITE: invitation sale guest list direct link unique code
Private sale #250: password OTP collection gated public leakable
#583 MEMSALE: member sale tier loyalty active status
#559 XDROP: exclusive drop queue FOMO sold out
#594 INVITEbot: bot verify eligibility link code tier 1
#250 = whoever knows the password enters. #593 = whoever is on the guest list receives a nominative link.
Which invite_* typologies should be classified?
Eight invitation sale ticket scenarios.
Eight invitation typologies
invite_not_received: invitation email never received / spam
invite_link_invalid: expired token link already used
invite_code_rejected: invitation code rejected at checkout
invite_expired: invitation window or sale expired
invite_wrong_email: invitation sent to the wrong address
invite_eligibility: am I on the guest list
invite_share_request: transfer/share access to a third party
invite_waitlist: invitation request off-list
Tags: invite, invite_only_sale, exclusive_access. INVITE-MAP-GROUNDED: resend/share access from map only.
How to structure the INVITE-MAP matrix?
The INVITE-MAP matrix documents each invitation sale for agents and the future bot #594.
INVITE-MAP Columns
sale_id: campaign invitation sale identifier
invite_list_source: Klaviyo CRM segment waitlist app Atelier
access_type: unique_link invite_code OTP email
invite_ttl_hours: link code validity in hours
sale_window: opening closing dates timezone
share_policy: transfer sharing allowed yes no
resend_policy: invitation resend max times delay
waitlist_policy: add list outside of invite yes no
escalation_marketing: contact ops invitation list
Sync Klaviyo flow sent, Atelier invite log, Shopify discount single-use, and marketing sheet. Pre-sale audit: invite_list_source up to date resend_policy communicated to agents.
INVITE-SUP policy in six rules
Six rules supporting invitation-based sales.
INVITE-MAP-GROUNDED : resend share waitlist access from map only
INVITE-LIST-VERIFY : list lookup API before confirming access
NO-INVITE-ISSUE : no invitation outside of waitlist_policy map ops
RESEND-SCOPE : resend based on resend_policy map max times
NO-SHARE-PROMISE : sharing based on share_policy map only
ACCESS-REROUTE : password tier → #250 #583 distinct invite
Flow INVITE INV-1 to INV-8
Flow agent eight steps invitation sale.
INV-1 Intake: invite_* intent + email sale_id link received
INV-2 Sale lookup: INVITE-MAP access ttl share resend
INV-3 List verify: invite_list_source API email on list
INV-4 Classify: not_received link code expired wrong share waitlist
INV-5 Token check: link code status used expired TTL
INV-6 Respond: macro INVITE grounded map
INV-7 Execute: resend fix email escalate marketing waitlist
INV-8 Close: tag invite_resolved sale_id
SLA: invite_not_received resend or spam check in one interaction if resend_policy map allows it.
Essential INVITE macros
Four macro agents sale invitation.
INVITE-ACCESS-01
"Sale invitation [sale_id] [email]: [on list / off list / pending]. [If on list: access [link / code] valid [invite_ttl_hours].] [If denied: reason [expired / used / wrong email].] Window sale [sale_window map]."
INVITE-RESEND-01
"Invitation [sale_id] [email]: [sent date / not found log]. [If resend authorized: resend performed [N]/[max resend_policy].] [If spam: check spam folder sender [from_domain].] [If max resend: escalation [escalation_marketing].]"
INVITE-SHARE-01
"Share access sale [sale_id]: [share_policy map]. [If prohibited: nominative invitation non-transferable.] [If authorized: procedure [share_procedure map].] Personal link [email] linked to Shopify account."
INVITE-WAITLIST-01
"Request invitation [sale_id] [email]: [waitlist_policy map]. [If yes: registration [waitlist_url] notification if space available.] [If no: closed sale fixed list next [next_sale_info].] Open promo site: [link #111]."
Edge cases: private sales, members only, pre-launch, and drops
Five cases outside the standard macro invitation.
Public password collection: ACCESS-REROUTE #250 PRIVATE distinct
Tier member sale: MEMSALE #583 distinct loyalty list
Pre-launch waitlist: prelaunch #306 before invite sale
FOMO drop queue: XDROP #559 distinct queue
Segmented CRM offer: POFF #573 distinct email invitation
Personalized invitation ≠ shareable Reddit password. Reroute if customer cites public VIP code #250.
Essential invite KPIs
Five INVITE steering metrics.
invite_ticket_rate: invite_* tickets / dirty list guests
invite_access_success_rate: access resolved without escalate / invite_link_invalid
invite_resend_success_rate: not_received resolved resend without ops
invite_share_request_rate: invite_share / total invite tickets
invite_waitlist_conversion: waitlist registered / off-list requests
Target: invite_access_success_rate higher than 90% with INVITE-MAP resend_policy and spam guidance agents.
Anti-patterns INVITE
Five common invitation sales errors.
Invitation issued off-list: NO-INVITE-ISSUE waitlist_policy ops
Access without list verify: INVITE-LIST-VERIFY API first
Promised sharing prohibited: NO-SHARE-PROMISE share_policy map
Unlimited resend: RESEND-SCOPE max resend_policy
VIP password confusion: ACCESS-REROUTE #250 distinct
INVITE with Qstomy
Qstomy on Shopify: detect invite intent, INVITE-MAP RAG grounded, invite list lookup Klaviyo Atelier, token status verify, handoff #594 bot tier 1 eligibility code link.
Pipeline: #594 bot verify link code → #593 resend fix email escalate marketing waitlist.
Explore AI support and request a demo.
Checklist, FAQ and going further
INVITE Checklist (8 steps)
INVITE-MAP v1 : list source ttl share resend waitlist
Policy INVITE-SUP : 6 INVITE-LIST-VERIFY rules
8 invite_* typologies : helpdesk tags
4 INVITE-* macros : ACCESS RESEND SHARE WAITLIST
Sync invite list API : Klaviyo Atelier test lookup
Test resend flow : sandbox email spam guidance
Agent training 30 min : INVITE vs PRIVATE #250 vs MEMSALE
KPI Dashboard : invite_* section 9
FAQ
Difference with private sale #250?
#250 = password OTP collection gated leakable. #593 = nominative guest list with unique code link.
Invitation never received?
INVITE-RESEND-01 spam check then resend_policy map.
Transfer my access?
INVITE-SHARE-01 share_policy map nominative non-transferable default.
Is bot #594 enough?
Tier 1 verify eligibility code link. Resend fix email → agents #593.
Going further
This week: publish INVITE-MAP active sale, test INVITE-RESEND-01 sandbox, measure invite_not_received_rate D-1 opening.
Enzo
July 1, 2026
