E-commerce
July 1, 2026
"What address is it exactly?" "My QR does not scan, the event starts in 20 minutes." "The workshop is postponed, will I be refunded?" Three messages where an attendee without self-service FAQ opens an urgent ticket even though TICK-MAP already contains the date, location, and refund policy.
An e-commerce ticketing AI chatbot does not replace TICK-FLOW agents (#425). It reads TICK-MAP, cites the date TZ and venue, guides through QR wallet pass, explains the transfer/cancel policy, and routes day-of resend requests to pre-filled P0 agents.
This guide #426 covers intents bot_tick_*, flow TICK-BOT, and KPI tick_bot. Distinct from ticketing customer service (#425) and the digital gift bot (#420): here, AI use cases focus on event date, venue access, QR code, and ticket refund policy.
Summary
Why does a ticketing bot reduce same-day panic?
An avoidable ticketing ticket is born when the attendee cannot find the date/time TZ, venue address, or QR ticket before writing to support on the day of the event.
Five botifiable ticketing ticket triggers
Date/location: timezone, address, entrance, parking
QR not received: spam email, missing PDF
QR scan fail: brightness, print, wallet pass
Postponement/cancellation: new date, refund option
Transfer policy: deadline, fee, feasibility
Eventbrite observes that 55-65% of pre-event questions concern date, location, and access, which are resolvable by a structured FAQ without an agent (Eventbrite, attendee support 2026). Tidio estimates that a tier 1 ticketing bot reduces tick_not_received and tick_date_confusion tickets by 45-58% (Tidio, chat stats 2026).
Angle #426 vs Related Content
Ticketing customer support #425: TICK-FLOW transfer execute refund batch. #426 = bot date venue QR policy tier 1.
Dgift bot #420: gift code scheduled. #426 = dated ticket QR check-in.
Partial refund #368: commercial gesture. #426 = explain cancel_policy, not execute refund bot.
Access bot #422: download licence. #426 = event ticket one-shot date.
Digital gift #419: flexible experience voucher. #426 = premium dated event.
DTC Example
Workshops 140 tickets/month, 34 tickets baseline #425. After TICK-BOT: tick_bot_resolution 81%, tick_ticket_delta -47%, tick_j0_handoff_sla 96%.
D-Day bot vs agent
Bot quotes venue + QR tips + resend 1x. qr_invalid at door unscanned → handoff P0 #425 TK-7 under 30 min.
Peak bot sessions D-7 to D-0
Bot sessions 5-8x baseline final week. T5 D-0 proactive reduces handoff queue 25% vs passive widget.
How does TICK-BOT differ from TICK-FLOW #425?
Self-service ticketing bot and event agent playbook: two layers on TICK-MAP.
Tick bot matrix → role
#426 TICK-BOT: arrival date, QR tips, spam, policy explain, resend 1x
#425 TICK-FLOW: transfer execute, refund org batch, D-0 ops backup
#420 DGIFT-BOT: undated gift code
#368 PART-REF: commercial gesture outside of ticketing
Upstream router
"Which date", "address", "QR is not working", "haven't received ticket", "postponed?" → TICK-BOT. "Transfer to [friend]", "refund me org cancelled", "qr scanned fraud", "D-0 at door now" → handoff #425 TK-7 P0. "Spa gift code" → #419 dgift.
TICK-BOT data
TICK-MAP JSON #425, order event_id, qr_sent_at, qr_scanned, event_datetime_tz, venue_address, transfer_policy, cancel_policy, postpone_status.
#426 Promise
TICK-BOT policy, 12 bot_tick_* intents, flow TB-1 to TB-8, guardrails no refund execute, KPI tick_bot_*.
Tier VIP vs GA bot scope
TICK-MAP tier_benefits : bot mentions VIP lounge vs GA entry. Tier change → handoff #425, not bot upgrade.
Which bot_tick_* intents should be configured?
Twelve ticketing bot intents cover tier 1 pre-event and Day-0.
Twelve bot_tick intents
bot_tick_date_venue: datetime TZ, address, entrance
bot_tick_not_received: missing QR email
bot_tick_spam_guide: TICK-SPAM-01
bot_tick_qr_tips: TICK-QR-TIP-01 wallet brightness
bot_tick_qr_status: sent, scanned bool lookup
bot_tick_resend_1x: resend if policy + not scanned
bot_tick_transfer_policy: deadline fee explain, do not execute
bot_tick_cancel_policy: refund window explain uphold
bot_tick_postponed: new date valid ticket + refund option cite
bot_tick_wallet_pass: Apple/Google wallet link
bot_tick_handoff_j0: event today qr fail → P0 #425
bot_tick_route_dgift: experience voucher → #419
Session tags
tick_bot, tick_bot_venue, tick_bot_qr, tick_bot_resolved, tick_bot_handoff_425, tick_bot_j0. Distinct dgift_bot, dacc_bot.
Triggers T1-T5
T1: event order page proactive confirmation. T2: ticket/QR/event/address keyword. T3: Day-1 email reminder bot link. T4: /pages/events-tickets FAQ. T5: event_date=today proactive widget Day-0.
How to apply the TICK-BOT flow in eight steps?
The TICK-BOT flow guides ticketing grounded TICK-MAP #425 and QR status.
Eight steps TB-1 to TB-8
TB-1 Welcome: "I am verifying your ticket: date, location, QR, terms."
TB-2 Auth order: order_id + attendee email
TB-3 Classifier intent: bot_tick_* section 3
TB-4 Match TICK-MAP: event_id, datetime TZ, venue, policies
TB-5 Read ticket status: qr_sent, qr_scanned, postpone_flag
TB-6 Respond: TICK-VENUE-01 | spam | QR tips | policy explain
TB-7 CTA: wallet pass | resend 1x | /pages/events-tickets
TB-8 Close/handoff: transfer/refund execute → #425 | D-0 P0
TB-5 not_received
If sent logged → bot_tick_spam_guide then bot_tick_resend_1x if resend_count < 1. If event D-0 → escalate handoff #425 P0 even after resend offer.
TB-5 qr fail D-0
If qr_scanned=false → bot_tick_qr_tips then resend 1x. If still at door + event starts < 30 min → bot_tick_handoff_j0 P0 supervisor fields.
TB-6 postponed
If postpone_flag true → bot_tick_postponed cite new_date + refund deadline TICK-MAP. Refund execute keyword REFUND → handoff #425 batch queue.
TB-6 cancel customer
bot_tick_cancel_policy cite window. Outside window uphold CGV polite. No refund bot execute.
Series pass partial date
tick_series : bot lists all dates TICK-MAP. Missed session refund → handoff #425 tick_series_partial policy.
Which TICK-BOT policy should be documented?
The TICK-BOT ticketing policy bot governs resend, policy citations, and handoffs.
Eight TICK-BOT rules
TICK-MAP only: datetime TZ, venue, policies from JSON #425
Auth before QR resend: order_id + email before resend trigger
Spam guide first: TICK-SPAM-01 if sent logged
Resend bot max 1: 2nd+ handoff #425 TK-7
No transfer execute bot: explain policy, handoff #425 TICK-TRANSFER-01
No refund execute bot: explain cancel/postpone policy, handoff agents
J-0 P0 handoff 30 min: qr_invalid event today → #425 supervisor
Max 6 turns tick admin: then portal CTA or handoff
RAG source corpus
/pages/events-tickets, TICK-MAP #425, TICK-SUP #425, venue maps links per event_id.
Sync ops
TICK-MAP postpone update → bot glossary + mass email same hour. Event cancelled flag → bot auto bot_tick_postponed variant cancel.
Monthly review
Audit: wrong TZ cite, refund promise bot, missed J-0 P0 handoff.
Accessibility venue bot
TICK-MAP accessibility_notes in bot_tick_date_venue response. Reduce PRM day-of venue tickets.
What guardrails protect QRs and refunds?
The allowed vs forbidden bot tick matrix protects ops gate and finance.
Allowed bot actions
Cite TICK-MAP date TZ venue parking accessibility
Lookup qr_sent qr_scanned status
Send TICK-SPAM-01 TICK-QR-TIP-01 TICK-VENUE-01
Trigger resend 1x if unscanned + resend_count < 1
Deep link wallet pass Apple/Google
Explain transfer cancel postpone policies
Handoff #425 D-0 P0 transfer refund execute
Forbidden bot actions
Execute transfer disable old QR issue new
Process refund Shopify partial or full
Promise refund outside cancel_policy
Override tier VIP vs GA without agent
Resend if qr_scanned true fraud case
Delay D-0 P0 handoff beyond 30 min SLA
Fraud scanned true
If qr_scanned + client claims not entered → handoff #425 uphold + supervisor. Bot zero second resend.
Org cancel mass refund
Bot explain TICK-CANCEL-ORG-01 timeline. Refund batch → agents #425 only, not bot API.
Chargeback D-0 keyword
Scam + event today → immediate P0 handoff with resend proof fields. Parallel bot_tick_handoff_j0 path.
How to integrate TICK-MAP #425 and ticketing apps?
The Shopify ticketing bot integration combines TICK-MAP and the ticket API app.
TICK-BOT read fields
order line event_id: SKU tick mapping
qr_status: sent_at, scanned_at bool
attendee_email: fulfillment recipient
postpone_flag: event rescheduled metadata
resend_count tag: bot resend tracking
Shopify digital fulfillment + Ticket Tailor API (Shopify, digital products 2026).
TICK-MAP bot layer
Import #425: event_datetime_tz, venue, transfer_policy, cancel_policy, postpone_refund_option, wallet_pass_url. TB-4 per order event_id.
Wallet pass deep link
bot_tick_wallet_pass: reduce qr_invalid print issues. TB-7 CTA before resend on J-0 path.
Postpone webhook
Ops update TICK-MAP + bot glossary when event postponed. Auto-trigger bot_tick_postponed template all open sessions event_id.
Multi-qty orders
TB-2 lookup all QR statuses per order. Bot cite qty scanned vs total if partial confusion.
Ticket Tailor API resend
TB-7 resend maps tick_app API endpoint per TICK-MAP. Document regen path per app like #425 agents TK-7.
What are the D-1, D-0, and UX triggers for TICK-BOT?
The UX TICK-BOT deployment maximizes deflection during event week.
Five widget placements
Confirmation event order: T1 proactive venue date
/pages/events-tickets: T4 FAQ per event_id
Email D-1 reminder: T3 bot link venue + wallet
D-0 morning proactive: T5 "ready for [event] ?"
PDP event pre-buy: cancel transfer policy visitor
D-1 email bot link
Klaviyo D-1: bot_tick_date_venue + wallet pass CTA. Reduce tick_date_confusion and tick_not_received day-of historical 35%.
D-0 P0 path
event_date=today sessions auto-priority queue. bot_tick_handoff_j0 pre-fill TK-4 fields for agents under 30 min SLA #425.
Postpone surge
postpone_flag true: widget banner site-wide + bot_tick_postponed default intent boost.
A/B test
T3 D-1 proactive vs passive: tick_bot_resolution + tick_j0_handoff_rate 4 weeks per event.
Multi-event catalog router
Buyer 2 events 2 orders: TB-2 disambiguate order_id before TICK-MAP match. Prevent wrong venue mention.
Which ticket bot KPIs should be measured?
Ticketing bot KPIs link deflection and D-0 SLA.
Eight key metrics
tick_bot_resolution_rate: resolved without handoff / tick_bot sessions
tick_ticket_delta: decrease in tickets #425 vs baseline
tick_venue_self_service_rate: venue bot date / questions date
tick_spam_first_rate: spam before resend / resend intents
tick_resend_bot_convert: resend 1x success / eligible
tick_j0_handoff_sla: P0 handoff < 30 min / D-0 qr fail
tick_handoff_425_rate: transfer refund execute routed agents
tick_bot_csat: satisfaction tag tick_bot resolved
DTC Benchmark
tick_bot_resolution 78-88%, tick_ticket_delta -42-52%, tick_j0_handoff_sla > 94%, venue_self_service > 70% questions date.
Dashboard per event
Intent breakdown D-7 to D+0, resend count, handoff reasons, scan rate post-event correlation.
Audit transcript
20 sessions/month: TZ always cited, no refund bot promise, D-0 P0 triggered correctly.
Post-event CSAT bot
D+1 survey tick_bot sessions only. Correlate tick_bot_csat with scan rate ops KPI.
Which anti-patterns should be avoided on a ticketing bot?
Ten ticketing bot anti-patterns to ban.
1. Refund promise bot cancel customer
Rule 6 explain only. Execute #425 agents.
2. Transfer execute bot
Rule 5 handoff TICK-TRANSFER-01. Disable old QR agents only.
3. Resend if qr_scanned true
Fraud path handoff uphold. No second QR.
4. Date reply without timezone
TICK-VENUE-01 always TZ. Paris 14h CET explicit.
5. D-0 qr fail no P0 handoff
Rule 7 30 min SLA mandatory bot_tick_handoff_j0.
6. Skip spam before resend
Rule 3 TICK-SPAM-01 if sent logged.
7. Confusing dgift voucher #419
bot_tick_route_dgift flexible code ≠ dated QR.
8. No TICK-SUP #425 prerequisite
/pages/events-tickets TICK-MAP before bot launch.
9. Postpone stale bot quote
Sync TICK-MAP same hour ops postpone. Wrong date = chaos.
10. 12-turn conversation
Max 6 turns rule 8. Venue CTA TB-7.
11. Org cancel bot batch refund
Explain timeline only. Finance batch #425 TK-7.
12. Resend duplicate active QR
Bot must check unscanned before resend. Two active QR = door scan conflict ops nightmare.
How does Qstomy manage date, QR, and ticketing policy?
Qstomy on Shopify: TICK-BOT order lookup, TICK-MAP venue date explain, TICK-QR-TIP-01, resend 1x trigger, policy transfer cancel postpone cite, J-0 P0 handoff #425 pre-filled fields.
Qstomy tick bot Capabilities
tick_order_lookup: TB-2 event_id qty datetime
tick_qr_status: TB-5 sent scanned
tick_map_venue: TICK-VENUE-01 auto TZ
tick_resend_once: 1x if policy unscanned
tick_policy_explain: transfer cancel postpone
tick_handoff_j0_p0: supervisor queue fields
Pipeline #426 → #425
Bot tier 1 venue QR policy. Agents transfer refund J-0 ops backup. Shared TICK-MAP.
DTC Encrypted Scenario
Workshops 140 ticks/month, 34 tickets baseline.
After Qstomy TICK-BOT: tick_bot_resolution 84%, tick_ticket_delta -49%, tick_j0_handoff_sla 97%, tick_bot_csat 4.5/5.
Explore customer support and request a demo.
Training corpus sync
See train Shopify chatbot for TICK-MAP RAG sync on postpone webhook.
What is the checklist for deploying TICK-BOT?
TICK-BOT Checklist (12 steps)
Validate TICK-SUP #425 + TICK-MAP /pages/events-tickets
Export TICK-MAP JSON → bot glossary per event_id
Configure 12 intents bot_tick_* section 3
Implement flow TB-1 to TB-8 + qr status read
Activate guardrails no refund/transfer execute + Day-0 P0
Route tick vs #425 #419 #368
Confirmation placements + /pages/events-tickets T4
Triggers T3 Day-1 email + T5 Day-0 proactive
Staging tests 8 scenarios: venue, not_received+spam, qr tips, resend, transfer policy, postpone, Day-0 handoff, cancel explain
Wallet pass links + resend_count tag
Dashboard KPI tick_bot per event + Day-0 SLA audit
A/B T3 Day-1 proactive vs passive 4 weeks
In brief
#426 = bot ticketing tier 1, #425 agents execute
TICK-MAP grounded: datetime TZ, venue, policies
TICK-BOT: status → venue/QR/policy → handoff
Day-0 P0 30 min: qr at door handoff mandatory
KPI tick_bot_resolution: target > 80 %
FAQ
Difference #425?
#425 customer service transfer refund Day-0 ops. #426 bot date venue QR policy resend 1x.
Does the bot refund if postponed?
No. Explains TICK-POSTPONE-01 + refund option. Execute #425 agents.
QR doesn't scan Day-0?
QR tips + resend 1x bot. At door < 30 min → handoff P0 #425.
Transfer to a friend via bot?
bot_tick_transfer_policy explain deadline. Execute → handoff #425.
Spa voucher vs ticket?
bot_tick_route_dgift → #419 experience. #426 dated event QR only.
Go further
This week: sync TICK-MAP bot per event_id, configure TB-5 qr status staging, test Day-0 handoff P0 path, activate widget Day-1 email T3.
Share this #426 guide with ops and support: a bot that quotes the address at 2 PM CET is worth a seamless queue at the doors, a lost attendee is worth ten negative reviews the same evening.
Gift ticket attendee email?
Buyer auth before resend attendee. Gift #205 + handoff transfer if name change.
Enzo
July 1, 2026
