E-commerce
July 1, 2026
"The bot promised a replacement without verifying the serial number." "The AI confuses my email card and my paper voucher." "Chatbot quotes an invented balance on an expired certificate." Three failures where a miscalibrated gift certificate bot doubles liability or frustrates the recipient.
A gift certificate AI chatbot does not replace PHYGCERT agents (#547). It reads PHYGCERT-MAP and the serial registry, quotes grounded balances and terms, guides redemption and handoff replacement without direct reissue.
This guide #548 covers intents bot_phygcert_*, flow PHYGCERTbot, and KPI phygcert_bot. Bot pair to the PHYGCERT playbook (#547). New AI use case: certificate redemption terms balance without bot reissue.
Summary
Why automate gift certificates with a bot?
Queries like "what is the balance" and "how do I use my voucher" skyrocket in January after the holidays. A bot designed to look up the serial registry should state the validity_months and redeem_channel without promising an auto-replacement.
What the bot resolves at tier 1
Balance lookup: remaining balance grounded in the serial registry
Redeem guide: checkout POS steps redeem_channel map
Conditions cite: validity_months policy_url map
Postal tracking: order tracking if the buyer is verified
Digital reroute: email card → gift-card article
The DGCCRF reminds about transparency regarding gift voucher validity (DGCCRF, gift card). The bot intercepts bot_phygcert_balance before simulating a made-up balance.
PHYGCERTbot vs PHYGCERT #547, digital gift card and DGIFT #419
Five contents, five distinct gift formats.
Quick Matrix
#548 PHYGCERTbot: balance redeem conditions tier 1 bot
#547 PHYGCERT: agents replacement reship verify
Digital Gift Card: email code checkout Shopify
#419 DGIFT: scheduled email access codes
Gift card bot: gift_card_balance intents distinct digital
Pipeline: bot balance redeem → lost replacement handoff #547. Email code instant → gift-card, not PHYGCERTbot.
Which bot_phygcert_* intents should be configured?
Eight gift certificate bot intents.
Eight bot_phygcert intents
bot_phygcert_balance: remaining balance serial number
bot_phygcert_redeem_how: use online POS store
bot_phygcert_conditions: validity T&C conditions map
bot_phygcert_expired: expired certificate policy cite
bot_phygcert_tracking: mail delivery tracking buyer
bot_phygcert_lost: lost voucher handoff replacement
bot_phygcert_damaged: unreadable certificate handoff
bot_phygcert_replacement_handoff: verify collect → #547
Tier 1 auto: balance, redeem_how, conditions, expired if serial lookup + PHYGCERT-MAP.
Intent bot_phygcert_lost, damaged, replacement_handoff → agents #547 with payload serial status verify.
How should PHYGCERT-MAP #547 be consumed?
The bot reads PHYGCERT-MAP #547 and registers series: cert_sku, serial_format, validity_months, replacement_policy, redeem_channel, verify_identity, status unused redeemed void.
Lookup grounded
Serial input: client provides format validate number
Registry lookup: balance status expiry date
PHYGCERT-MAP row: redeem replacement policy cite
Mask log: MASK-SERIAL-LOG last4 only analytics
Reissue gate: NO-REISSUE-BOT handoff #547
Alignment anti-hallucination (#123): balance = registry API only.
PHYGCERTBOT-SUP policy in six rules
Six rules for a secure gift certificate bot.
SERIAL-LOOKUP-BOT: registry lookup before balance quote
NO-REISSUE-BOT: bot does not void or reissue certificate
PHYGCERT-MAP-GROUNDED: conditions from map only
MASK-SERIAL-LOG: never log full serial
DIGITAL-REROUTE: email code → gift-card intents
REPLACEMENT-HANDOFF: lost damaged → #547 execute
PHYGCERTbot Flow PGCB-1 to PGCB-8
Eight-step gift certificate bot flow.
PGCB-1 Classify: bot_phygcert_* intent
PGCB-2 Serial collect: serial number format validate
PGCB-3 Registry lookup: balance status expiry
PGCB-4 PHYGCERT-MAP: redeem conditions replacement
PGCB-5 Guardrail: NO-REISSUE MASK-SERIAL
PGCB-6 Respond: TPL-PHYGCERTbot grounded
PGCB-7 Handoff: replacement tracking → #547
PGCB-8 Log: intent serial_mask tag phygcert_bot
Example TPL-PHYGCERTbot-BALANCE
"Certificate ending in [serial_last4]: balance [balance] €, valid until [expiry_date]. Usage: [redeem_channel]. Conditions: [policy_url]."
TPL-PHYGCERTbot templates and touchpoints
Four essential templates.
TPL-PHYGCERTbot-BALANCE
Balance [balance] €. Validity: [expiry_date]. Number ending in [serial_last4].
TPL-PHYGCERTbot-REDEEM
Enter the serial number at checkout in the gift voucher section or present in store [POS_list]. Steps: [redeem_steps map].
TPL-PHYGCERTbot-CONDITIONS
Validity [validity_months] months. Full conditions: [policy_url]. Loss replacement: [replacement_policy summary].
TPL-PHYGCERTbot-HANDOFF
Replacement request registered. An agent will process within [replacement_sla]. Identity verification required. Masked number [serial_last4] transmitted.
Touchpoints
Page /gift-certificate: bot_phygcert_balance chip
Gift voucher checkout: bot_phygcert_redeem_how trigger
Certificate balance footer: balance entry point
Help center gift FAQ: bot embed PHYGCERT-MAP RAG
Edge cases and reroutes
Five cases outside tier 1 bot balance redeem.
Email gift card: DIGITAL-REROUTE gift-card article
Digital gift access: #419 DGIFT reroute
Corporate bulk series: corporate B2B handoff ops
Redeemed fraud series: denial replacement registry status
Chargeback threat: handoff #547 P1 reship proof
Bot never modifies series registry: NO-REISSUE-BOT, execute → agents #547 finance ops.
Essential phygcert_bot KPIs
Five PHYGCERTbot monitoring metrics.
phygcert_bot_balance_success : % balance lookup serial OK
phygcert_bot_redeem_deflect : redeem sessions without ticket
phygcert_bot_unauthorized_reissue : reissue bot, target 0
phygcert_bot_digital_reroute : sessions → gift-card
phygcert_bot_handoff_replacement : sessions → #547 agents
Monthly red team : 10 prompts "reissue lost certificate", "invent 100 € balance", "log my full number". Reissue bot = NO-REISSUE-BOT violation.
PHYGCERTbot anti-patterns
Six common mistakes.
Direct bot reissue: NO-REISSUE-BOT
Invented balance: SERIAL-LOOKUP-BOT registry
Full serial logged: MASK-SERIAL-LOG
Confusing gift-card email: DIGITAL-REROUTE
Replacement without handoff: REPLACEMENT-HANDOFF
Conditions out of map: PHYGCERT-MAP-GROUNDED
PHYGCERTbot with Qstomy
Qstomy on Shopify: detect bot_phygcert intent, registry API balance, PHYGCERT-MAP RAG, MASK-SERIAL-LOG, NO-REISSUE guardrail, handoff #547 replacement payload, digital reroute gift-card.
Pipeline: bot balance redeem → #547 replacement → AI governance #142 audit serial handling.
Explore AI support and request a demo.
Checklist, FAQ and going further
PHYGCERTbot Checklist (8 steps)
Sync PHYGCERT-MAP #547: RAG bot + registry API
Policy PHYGCERTBOT-SUP: 6 NO-REISSUE-BOT rules
8 intents bot_phygcert_*: flow PGCB-1 to PGCB-8
4 templates TPL-PHYGCERTbot-*: BALANCE REDEEM CONDITIONS HANDOFF
Serial mask logging: last4 analytics only
Certificate chip page: bot_phygcert_balance entry
Red team 10 prompts: invented balance reissue
Dashboard KPI: phygcert_bot_* section 9
FAQ
Difference #547?
#547 = agents void reissue reship verify. #548 = bot tier 1 balance redeem handoff.
Does the bot reissue a lost certificate?
No. REPLACEMENT-HANDOFF #547.
Difference from a digital gift card?
Email code = gift-card intents. Paper voucher = PHYGCERTbot.
Is the serial number saved in the logs?
No. MASK-SERIAL-LOG last4 only.
Going further
This week: connect the registry API bot, test the red team on "reissue certificate", measure phygcert_bot_unauthorized_reissue. Activate the gift certificate page chip.
Enzo
July 1, 2026
