E-commerce
July 1, 2026
"The bot confirms Tuesday at 2 PM even though my appointment is not booked." "The AI cannot find the post-purchase Calendly link." "Chatbot promises a postponement without reading the reschedule policy." Three failures where a poorly calibrated post-purchase booking bot invents a time slot, loses the booking link, or executes a postponement/cancellation.
An AI customer service booking chatbot linked to a purchase does not replace APPTPROD agents (#717). It reads APPTPROD-MAP, looks up the booking API, cites the prep checklist, and hands off no-show reschedule cancel to humans.
This guide #718 covers intents bot_apptprod_*, the APPTPRODbot flow, and apptprod_bot KPIs. Bot pair of the APPTPROD playbook (#717). AI use case: guiding booking prep status without promising a time slot or executing a postponement.
Summary
Why automate the post-purchase appointment via bot?
"How do I book?", "When is my appointment?" and "What should I prepare?" come right from the service purchase confirmation email. A calibrated bot cites booking_url booking_window_days prep_checklist without promising a made-up date or rescheduling.
What the tier 1 bot resolves for post-purchase appointments
Booking guide: booking_url method window map
Slot status: appointment_status API verify
Preparation: prep_checklist_copy cite map
Reschedule policy: reschedule_policy RESCHEDULE-CITE map
Appointment format: appointment_format in_store virtual map
Calendly observes that automated reminders reduce no-shows by 40 to 60% on services booked online (Calendly, no-show 2026). Without a grounded bot, AI amplifies slot disputes or out-of-policy actions.
APPTPRODbot vs APPTPROD #717, PARTINSTbot #626, SLOT #427 and FIXDATE #641
Six contents, six distinct scheduling moments.
Quick matrix
#718 APPTPRODbot: bot tier 1 booking prep status policy handoff
#717 APPTPROD: agents reschedule cancel no-show execute redirect
PARTINSTbot #626: physical partner installation distinct consultation appointment
SLOT #427: carrier delivery slot distinct service
FIXDATE #641: event delivery date distinct service booking
Pipeline: #718 bot booking prep status tier 1 → #717 agents reschedule cancel no-show exception.
Which bot_apptprod_* intents should be configured?
Eight post-purchase RDV bot intents mapped to apptprod_* typologies #717.
Eight bot_apptprod intents
bot_apptprod_book_guide: booking_url window method map
bot_apptprod_status: appointment_status API date verify
bot_apptprod_prep: prep_checklist_copy cite map
bot_apptprod_reschedule_info: reschedule_policy RESCHEDULE-CITE
bot_apptprod_cancel_info: cancellation_policy CANCEL-CITE
bot_apptprod_pre_purchase: booking_window availability explain map
bot_apptprod_no_show_hint: no_show_policy cite handoff #717
bot_apptprod_handoff: reschedule cancel execute no-show → #717
Tier 1 auto: book_guide, status, prep, reschedule_info if APPTPROD-MAP active + guardrails.
bot_apptprod_handoff reschedule cancel execute no-show → agents #717 payload order booking intent.
How to consume APPTPROD-MAP #717?
The bot reads APPTPROD-MAP #717: apptprod_program_id, sku_or_service_type, booking_method, booking_url, booking_window_days, appointment_format, prep_checklist_copy, reschedule_policy, cancellation_policy, no_show_policy, customer_communication_copy.
Lookup grounded
APPT-STATUS-VERIFY-BOT: booking API status before date cited
NO-SLOT-PROMISE-BOT: slot confirmed API only
RESCHEDULE-CITE-BOT: reschedule_policy cites map verbatim
CANCEL-CITE-BOT: cancellation_policy cites map verbatim
NO-RESCHEDULE-EXECUTE-BOT: bot does not reschedule or cancel appointments
BOOKING-URL-CITE-BOT: booking_url map only validated link
PARTINST626-REROUTE-BOT: physical install → #626 PARTINSTbot distinct consultation
APPTPROD717-HANDOFF-BOT: reschedule cancel no-show → #717 agents AP-7
Alignment anti-hallucination (#123): booking reschedule cancel = APPTPROD-MAP whitelist only.
APPTPRODBOT-SUP policy in six rules
Six rules for a responsible post-purchase appointment bot.
APPTPROD-MAP-GROUNDED-BOT: booking prep policy from map only
APPT-STATUS-VERIFY-BOT: booking API status before date cited
NO-SLOT-PROMISE-BOT: confirmed slot API only
NO-RESCHEDULE-EXECUTE-BOT: postponement cancellation agents #717 only
RESCHEDULE-CITE-BOT: reschedule_policy cited if postponement concerns map
SLOT427-REROUTE-BOT: delivery slot → #427 SLOT distinct from service appointment
Flow APPTPRODbot APB-1 to APB-8
Flow: eight-step post-purchase appointment bot.
APB-1 Classify : bot_apptprod_* intent detect email order widget
APB-2 Collect : order_ref email booking_id if status
APB-3 APPTPROD-MAP : booking url window prep reschedule cancel
APB-4 Booking lookup : Calendly API appointment_status verify
APB-5 Guardrail : APPT-STATUS NO-SLOT NO-RESCHEDULE RESCHEDULE HANDOFF
APB-6 Respond : TPL-APPTPRODbot grounded customer_communication_copy
APB-7 Handoff or close : reschedule cancel no-show #717 payload
APB-8 Log : intent apptprod_program_id tag apptprod_bot status handoff Y/N
Example TPL-APPTPRODbot-STATUS
“Appt [order_ref map]: status [API appointment_status map.] [If confirmed: [date time map].] [If pending: book via [booking_url map] within [booking_window_days map] d.] APPT-STATUS-VERIFY-BOT.”
TPL-APPTPRODbot templates and touchpoints
Four essential templates.
TPL-APPTPRODbot-BOOK
Appointment [apptprod_program_id]: book via [booking_url map] within [booking_window_days map] days. Format [appointment_format map.] BOOKING-URL-CITE-BOT.
TPL-APPTPRODbot-STATUS
Order [order_ref]: status [API appointment_status map.] [Date time if confirmed map.] APPT-STATUS-VERIFY-BOT NO-SLOT-PROMISE-BOT.
TPL-APPTPRODbot-PREP
Before appointment [appointment_format map]: [prep_checklist_copy map verbatim.] Post-service questions: contact support.
TPL-APPTPRODbot-HANDOFF
Request [report cancellation no-show execute] forwarded to team. Summary [order_ref booking intent]. APPTPROD717-HANDOFF-BOT.
Touchpoints
Purchase confirmation email footer chat: bot_apptprod_book_guide proactive
Order status page widget: bot_apptprod_status entry
Keyword reschedule cancel appointment: bot_apptprod_reschedule_info handoff
D-1 reminder email: bot_apptprod_prep trigger
Edge cases and reroutes
Five non-tier 1 cases bot standard post-purchase business appointment.
Partner installation: PARTINST626-REROUTE-BOT #626 physical installation post-delivery
Parcel delivery slot: SLOT427-REROUTE-BOT #427 carrier distinct service
Custom PDF proof validation: #654 BATPROOFbot distinct booking approval
Reschedule cancellation execute: NO-RESCHEDULE-EXECUTE-BOT agents #717 only
No-show dispute: APPTPROD717-HANDOFF-BOT no_show_policy map
Bot guide booking tier 1. Reschedule cancel no-show execute → agents #717.
Essential apptprod_bot KPIs
Five APPTPRODbot steering metrics.
apptprod_bot_booking_deflect: book guide resolved without agent
apptprod_bot_status_deflect: appointment status resolved API cite
apptprod_bot_prep_deflect: prep checklist resolved TPL-PREP
apptprod_bot_slot_promise_violations: promised slot bot audit target 0
apptprod_bot_handoff_rate: reschedule cancel no-show / total apptprod bot
Target: apptprod_bot_slot_promise_violations 0 and apptprod_bot_booking_deflect greater than 60%.
APPTPRODbot anti-patterns
Five common post-purchase appointment bot errors.
Invented confirmed slot bot: NO-SLOT-PROMISE APPT-STATUS-VERIFY
Direct bot appointment rescheduling: NO-RESCHEDULE-EXECUTE handoff #717
Invented booking link bot: BOOKING-URL-CITE booking_url map only
Confusing delivery with appointment bot: SLOT427-REROUTE carrier distinct
Installation confused with consultation bot: PARTINST626-REROUTE #626 distinct
APPTPRODbot with Qstomy
Qstomy on Shopify: detect bot_apptprod intent, APPTPROD-MAP RAG grounded, booking status cite, prep guide, handoff #717 reschedule tier 2.
Pipeline: #718 bot booking prep status tier 1 → #717 agents reschedule cancel no-show exception.
Explore AI support and request a demo.
Checklist, FAQ and going further
APPTPRODbot Checklist (8 steps)
Sync APPTPROD-MAP #717: RAG bot email confirmation order status
Policy APPTPRODBOT-SUP: 6 rules APPT-STATUS NO-SLOT NO-RESCHEDULE
8 intents bot_apptprod_*: flow APB-1 to APB-8
4 templates TPL-APPTPRODbot-*: BOOK STATUS PREP HANDOFF
Booking API sync: Calendly appointment_status bot agents test
Post-purchase email embed: bot_apptprod_book_guide proactive widget
Red team 10 prompts: promised slot rescheduled bot invented link confused SLOT
Dashboard KPI: apptprod_bot_* section 9 booking_deflect slot_violations
FAQ
Difference #717?
#717 = agents reschedule cancel no-show execute exception. #718 = bot tier 1 booking prep status handoff.
Difference PARTINSTbot #626?
#626 = physical partner installation. #718 = meeting service consultation fitting demo coaching.
Does bot reschedule the appointment?
No. NO-RESCHEDULE-EXECUTE-BOT TPL-APPTPRODbot-HANDOFF #717.
Booking link not found by bot?
TPL-APPTPRODbot-BOOK booking_url BOOKING-URL-CITE-BOT map.
Going further
This week: index APPTPROD-MAP RAG email confirmation, sync Calendly booking API bot, red team promised slot bot violations.
Enzo
July 1, 2026
