E-commerce
July 1, 2026
"The bot confirms my access without checking my guest list." "The AI sends another invitation even though the resend_policy map says max 1." "The chatbot promises access sharing when share_policy prohibits it." Three failures where a poorly calibrated invitation sales bot breaks nominative exclusivity.
An AI invitation sales chatbot does not replace INVITE agents (#593). It reads INVITE-MAP, verifies the Klaviyo Atelier list, quotes invite_ttl share_policy resend_policy, and handoffs resend fix email to humans.
This guide #594 covers intents bot_invite_*, flow INVITEbot, and KPI invite_bot. Twin bot of the playbook INVITE (#593). New AI exclusivity use case: verify eligibility code link without issuing an invitation or executing a resend.
Summary
Why automate invitation-based sales using a bot?
"My invitation didn't arrive," "the link is invalid," and "am I on the list?" skyrocket as soon as the invitation sale opens. A calibrated bot looks up INVITE-MAP, verifies the invite list API, and quotes TTL share without improvising off-list access.
What the tier 1 bot resolves
List eligibility: email on list invite_list_source API
Link status: token valid expired used map TTL
Code status: Shopify invite code status terms
Spam guidance: not_received resend_policy explain handoff
Sharing policy: share_policy waitlist_policy cite map
Atelier points out that personalized invitation sales reduce leaks compared to a public password if the verified list is synchronized (Atelier, private sales Shopify 2026). The bot intercepts bot_invite_eligibility before off-map access is promised.
INVITEbot vs INVITE #593, PRIVATE #250, MEMSALEbot #584 and XDROP #559
Five pieces of content, five distinct exclusive access models.
Quick Matrix
#594 INVITEbot: tier 1 bot elig link code share waitlist handoff
#593 INVITE: agents resend fix email escalate marketing waitlist
PRIVATE #250: password OTP collection gated distinct
#584 MEMSALEbot: member sale loyalty tier distinct
#559 XDROP: drop queue FOMO sold out distinct
Pipeline: bot elig link code cite → #593 resend fix email escalate ops. Password VIP → #250 reroute.
Which bot_invite_* intents should be configured?
Eight sales bot invitation intents mapped to invite_* typologies #593.
Eight bot_invite intents
bot_invite_eligibility: email on list yes no API
bot_invite_link_status: token link valid expired used
bot_invite_code_status: invite code Shopify checkout status
bot_invite_not_received: spam guidance resend_policy handoff
bot_invite_expired: invite_ttl sale_window cite map
bot_invite_share_info: share_policy transfer explain
bot_invite_waitlist_info: waitlist_policy registration explain
bot_invite_handoff: resend fix email escalate → #593
Tier 1 auto: eligibility, link_status, code_status, expired, share_info, waitlist_info if email auth + INVITE-MAP + guardrails.
bot_invite_handoff, resend execute, fix email, invite issue → agents #593 payload email sale_id intent.
How should INVITE-MAP #593 be consumed?
The bot reads INVITE-MAP #593: sale_id, invite_list_source, access_type, invite_ttl_hours, sale_window, share_policy, resend_policy, waitlist_policy, escalation_marketing.
Lookup grounded
Sale detect: landing email UTM → INVITE-MAP row
Invite list API: Klaviyo segment Atelier log LIST-VERIFY-BOT
Token status API: link code used expired TTL
Shopify Discount API: invite code status single-use
NO-INVITE-ISSUE-BOT: access confirm only if on list API
NO-RESEND-EXECUTE-BOT: resend → handoff #593 ops
Alignment anti-hallucination (#123): elig access = INVITE-MAP or list API only.
INVITEBOT-SUP policy in six rules
Six rules for secure invitation bot sales.
INVITE-MAP-GROUNDED: ttl share resend access from map only
LIST-VERIFY-BOT: invite list API before elig yes
NO-INVITE-ISSUE-BOT: bot does not issue or add invitations outside map ops
NO-RESEND-EXECUTE-BOT: resend invitation → handoff #593
NO-SHARE-PROMISE-BOT: sharing according to share_policy map only
PRIVATE-MEMSALE-REROUTE-BOT: password → #250, tier → #584
Flow INVITEbot INVB-1 to INVB-8
Flow eight steps invitation sale bot.
INVB-1 Classify: bot_invite_* intent detect
INVB-2 Collect: email sale_id link code received
INVB-3 INVITE-MAP: access ttl share resend waitlist
INVB-4 List verify: invite_list_source API LIST-VERIFY-BOT
INVB-5 Guardrail: NO-INVITE NO-RESEND NO-SHARE-PROMISE
INVB-6 Respond: TPL-INVITEbot grounded map
INVB-7 Handoff: resend fix email escalate → #593
INVB-8 Log: intent sale_id tag invite_bot
Example TPL-INVITEbot-ELIG
"Invitation sale [sale_id] [email]: [on list / off list / pending API]. [If on list: access [access_type] valid [invite_ttl_hours]. Window [sale_window].] [If off list: [waitlist_policy map].] [If resend needed: handoff agent #593.]"
TPL-INVITEbot templates and touchpoints
Four essential templates.
TPL-INVITEbot-ELIG
Sale [sale_id] [email] : [eligible / not eligible]. List [invite_list_source]. [If eligible: access [access_type] TTL [invite_ttl_hours].] [If not: waitlist [waitlist_policy].]
TPL-INVITEbot-LINK
Invitation link [sale_id] : [status: valid / expired / already used]. TTL [invite_ttl_hours map]. Sale window [sale_window]. [If invalid: handoff #593 resend if resend_policy.]
TPL-INVITEbot-CODE
Invitation code: [Shopify status: valid / expired / used / conditions]. Single-use [access_type map]. [If rejected: verify account email [email] linked to list.]
TPL-INVITEbot-HANDOFF
Request [resend / fix email / invite issue] forwarded to agent. Email [email]. Sale [sale_id]. Delay [handoff_sla].
Touchpoints
Invite landing gate : bot_invite_link_status embed
Checkout code error : bot_invite_code_status chip
Pre-sale FAQ : bot_invite_eligibility widget
Email invitation footer : bot_invite_not_received entry
Edge cases and reroutes
Five cases outside tier 1 bot standard invitation.
Resend invitation execute: NO-RESEND-EXECUTE handoff #593 INVITE-RESEND-01
Fix email wrong address: handoff #593 ops marketing list
Password private sale: PRIVATE-MEMSALE-REROUTE #250
Member tier sale: MEMSALEbot #584 reroute
Pre-launch waitlist: prelaunch #306 distinct invite sale
Bot never issues invitation: resend fix email invite issue → agents #593 ops marketing Klaviyo Atelier.
Essential invite_bot KPIs
Five INVITEbot steering metrics.
invite_bot_elig_deflect: eligibility resolved without agent
invite_bot_link_deflect: link_status resolved without handoff
invite_bot_handoff_rate: resend fix email / total invite bot
invite_bot_hallucination_rate: elig access out of audit map
invite_bot_reroute_accuracy: PRIVATE MEMSALE correct reroute
Target: invite_bot_elig_deflect greater than 70% sale opening with INVITE-MAP list API sync.
INVITEbot anti-patterns
Five common bot sale invitation errors.
Eligible without list verify: LIST-VERIFY-BOT API first
Resend executed bot: NO-RESEND-EXECUTE-BOT handoff #593
Promised sharing prohibited: NO-SHARE-PROMISE-BOT share_policy map
Invitation issued bot: NO-INVITE-ISSUE-BOT marketing ops only
VIP password confusion: PRIVATE-REROUTE #250 distinct
INVITEbot with Qstomy
Qstomy on Shopify: detect bot_invite intent, INVITE-MAP RAG grounded, Klaviyo Atelier list lookup, token code verify, handoff #593 resend fix payload sale_id email.
Pipeline: #594 bot elig lien code share → #593 resend fix escalate marketing.
Explore AI support and request a demo.
Checklist, FAQ and going further
INVITEbot Checklist (8 steps)
Sync INVITE-MAP #593: RAG bot + Klaviyo Atelier list API
Policy INVITEBOT-SUP: 6 NO-RESEND-EXECUTE-BOT rules
8 intents bot_invite_*: flow INVB-1 to INVB-8
4 templates TPL-INVITEbot-*: ELIG LINK CODE HANDOFF
Invite landing embed: bot_invite_link_status entry
Checkout code chip: bot_invite_code_status trigger
Red team 10 prompts: promised access resend executed sharing forbidden
KPI Dashboard: invite_bot_* section 9
FAQ
Difference #593?
#593 = agents resend fix email escalate marketing. #594 = bot tier 1 elig link code handoff.
Does the bot resend the invitation?
No. NO-RESEND-EXECUTE-BOT. Handoff #593 INVITE-RESEND-01.
Invalid link?
TPL-INVITEbot-LINK token status TTL handoff resend if map.
Difference from PRIVATE #250?
#250 = password collection gated. #594 = nominative guest list.
Going further
This week: index INVITE-MAP RAG, embed bot invite landing gate, red team promised access outside bot list.
Enzo
July 1, 2026
