E-commerce
July 1, 2026
“My son didn't receive the gift code.” “The email was scheduled for yesterday, nothing went out.” “Where can I find the access link to the gifted class?” Three messages where a buyer or recipient without self-service opens an urgent ticket while the sending status already exists in Shopify.
An e-commerce digital gift AI chatbot does not replace DGIFT-FLOW agents (#419). It reads DGIFT-MAP, checks delivery status, guides to the spam folder, quotes the scheduled date, and routes resends or wrong recipients to agents with pre-filled fields.
This guide #420 covers intents bot_dgift_*, the DGIFT-BOT flow, and the dgift_bot KPI. Distinct from digital gift customer service (#419) and gift card balance: here, AI use cases for delivery status, code, recipient, and digital gift resend.
Summary
Why does a dgift bot reduce urgent tickets and chargebacks?
An avoidable digital gift ticket is born when the buyer or recipient cannot find how to check the delivery status, recover a code, or confirm the scheduled date before writing "scam" or "refund" to support.
Five triggers for botifiable dgift tickets
Email not received: spam, delay in perception, future scheduled sending
Unknown send status: buyer wants proof of digital delivery
Recipient email: "did it actually go to [email]?"
Invalid code: typo, expiration, already used
Buyer copy: PDF or code for hand delivery
Shopify logs the sending of digital gift cards and transactional notifications in the order timeline (Shopify, gift cards 2026). Gorgias estimates that 55-70% of "gift not received" tickets are resolved by lookup delivery + spam guide without agent action (Gorgias, customer service stats 2026).
Angle #420 vs neighboring content
Dgift customer service #419: DGIFT-FLOW agents resend LMS. #420 = bot lookup status + spam guide + handoff DG-7.
Gift card balance: balance checkout redemption. #420 = delivery email/code, not cart application.
Confirmation #358: buyer post-payment email. #420 = digital gift recipient email.
Physical gift #205: parcel tracking. #420 = zero shipping, digital delivery status.
Gift subscription #273: redeem subscription. #420 = cross-cutting view of dgift bot of all types.
DTC Example
Wellness + gift cards + course access, 64 dgift tickets/month baseline #419. After DGIFT-BOT: dgift_bot_resolution 79%, dgift_not_received_ticket_delta -51%, dgift_chargeback_threat_delta -34%.
Upstream vs Downstream
#420 lookup + spam + status self-service. #419 executes resend, disable code, LMS enroll, expiration extension.
How does DGIFT-BOT differ from DGIFT-FLOW #419?
Administrative bot dgift and agents playbook: two complementary layers on DGIFT-MAP.
Bot dgift → role matrix
#420 DGIFT-BOT: status lookup, spam guide, recipient confirm, scheduled date
#419 DGIFT-FLOW: resend execute, wrong recipient reissue, LMS enroll, extension
gift-card article: balance checkout bot balance lookup
#358 CONF-EMAIL: buyer confirmation, not recipient
Upstream router
"Did not receive gift email", "delivery status", "scheduled when", "code where" → DGIFT-BOT. "Refund", "wrong email corrected reissue", "LMS course access denied", "expiration extension" → handoff #419 DG-7. "Checkout card balance" → gift-card article bot balance.
DGIFT-BOT Data
DGIFT-MAP JSON #419, Shopify order timeline email_sent, gift card admin last4, scheduled_send_date metafield, recipient_email line item, resend_count tag.
UX Coexistence
Post-purchase widget + /pages/digital-gifts. Max 6 turns status/spam then status portal CTA or handoff. Chargeback keyword → immediate P1 handoff with DG-4 fields.
#420 Promise
DGIFT-BOT policy, 12 bot_dgift_* intents, flow DB-1 to DB-8, no code leak guardrails, dgift_bot_* KPIs.
Which bot_dgift_* intents should be configured?
Twelve digital gift bot intents cover post-purchase administrative lookup.
Twelve bot_dgift intents
bot_dgift_status_lookup: sent, scheduled, pending, redeemed
bot_dgift_not_received: email/code never reached recipient
bot_dgift_spam_guide: DGIFT-SPAM-01 before resend
bot_dgift_recipient_verify: confirm recipient email without exposing code
bot_dgift_scheduled_check: scheduled send date + timezone
bot_dgift_code_invalid: typo, expired, already used diagnostics
bot_dgift_resend_request: resend if policy allows, otherwise handoff
bot_dgift_buyer_copy: PDF or buyer resend for hand-delivery
bot_dgift_wrong_recipient: reported email typo, route P1 handoff
bot_dgift_access_link: digital product access link, LMS portal
bot_dgift_expiration_check: code validity or remaining access
bot_dgift_route_gift_card: checkout balance → gift card article
Session tags
dgift_bot, dgift_bot_status, dgift_bot_spam, dgift_bot_resolved, dgift_bot_handoff_419, dgift_bot_route_gc. Distinct missing_confirmation, gift_card_balance.
T1-T5 triggers
T1: post-checkout thank-you page dgift order. T2: keyword gift/code/not received/scheduled. T3: buyer email D+1 "gift status" link. T4: /pages/digital-gifts FAQ. T5: chargeback/scam keyword → handoff P1 #419.
How to apply the DGIFT-BOT flow in eight steps?
The DGIFT-BOT flow guides lookup dgift grounded DGIFT-MAP #419 and Shopify timeline.
Eight steps DB-1 to DB-8
DB-1 Home: "I verify digital gift dispatch status: email, code, date."
DB-2 Auth order: order_id + buyer or recipient email verify OTP
DB-3 Classifier intent: bot_dgift_* section 3
DB-4 Match DGIFT-MAP: dgift_type, delivery_channel, resend_policy
DB-5 Lookup delivery: timeline sent, bounce, scheduled_date, redeemed
DB-6 Respond: status template | spam guide | expiration cite | handoff trigger
DB-7 CTA: /pages/digital-gifts | status portal | ticket handoff fields
DB-8 Close/handoff: resend execute #419 | wrong_recipient P1 | chargeback P1
DB-5 not_received sent logged
If email_sent timestamp + no bounce → bot_dgift_spam_guide DGIFT-SPAM-01. Offer self-service resend 1x if resend_count < 2 per DGIFT-MAP. Else handoff #419 DG-7.
DB-5 scheduled future
If scheduled_date > today: cite date + timezone + recipient masked email "***@domain.com". No panic resend before date.
DB-5 never sent
Timeline empty + paid order → handoff #419 dgift_app_delivery_bug or expedite P1 if event today.
DB-6 code_invalid
Bot checks last4 + expiry admin. Diagnosis: typo spaces, expired, redeemed. No full code in chat log. Extension or reissue → handoff #419 DG-6.
DB-8 wrong_recipient
Collect corrected email + light identity verification. Handoff ticket fields: order_id, old_email, new_email, code_redeemed bool.
Which DGIFT-BOT policy should be documented?
The DGIFT-BOT digital gift bot policy governs auth, resend, and privacy.
Eight DGIFT-BOT rules
DGIFT-MAP only: resend limit, validity, delivery from JSON #419
Auth before status: order_id + email before recipient reveal
No full code chat: last4 only, never 16 full char in logs
Spam guide first: DGIFT-SPAM-01 if sent logged before resend offer
Resend bot max 1: 2nd+ resend handoff #419 DG-7 execute
Wrong recipient no bot reissue: handoff P1 agents disable old code
Chargeback keyword P1: ack + handoff 4 h SLA #419 rule 6
Max 6 turns dgift admin: then portal CTA or handoff
Corpus RAG sources
/pages/digital-gifts, DGIFT-MAP JSON #419, DGIFT-SUP #419, Shopify gift card help. Do not invent validity days missing from map.
Sync ops
DGIFT-MAP update #419 → bot glossary same day. Scheduled flow Klaviyo/Shopify audit pre-Christmas.
Confirmation distinction #358
Intent missing_confirmation buyer → route #358 CONF-EMAIL bot, not DGIFT-BOT.
Monthly review
Audit transcripts: code leak, resend without spam guide, wrong recipient bot reissue attempt.
What guardrails protect code and confidentiality?
The allowed vs. forbidden dgift bot matrix protects codes, recipients, and ops.
Allowed bot actions
Lookup order dgift_type, delivery_status, scheduled_date
Cite DGIFT-MAP validity, resend_policy, spam tip
Confirm recipient masked email "m***@gmail.com"
Send DGIFT-SPAM-01 template with sender address
Trigger 1x resend if resend_count < limit and sent+bounce absent
Deep link /pages/digital-gifts + gift status portal
Route checkout balance u2192 gift-card bot article
Handoff #419 with DG-4 delivery fields pre-filled
Forbidden bot actions
Display full gift code in chat or logs analytics
Reissue code wrong_recipient without agent disable old
Extend expiration "exception" without DGIFT-MAP policy
LMS manual enroll e-product access
Reveal recipient full email to third party unauthenticated
Promise refund chargeback without handoff
Hard block phrases
Block response containing full 16-char code. Use: "code ends with [XXXX], valid until [date]".
Recipient vs. buyer auth
Recipient OTP email match recipient field. Buyer order_id + buyer email. Cross-party info: buyer sees masked recipient only.
Privacy wrong recipient
Never confirm "yes the package is with [wrong person name]" for digital. Status: sent to [masked email] at [timestamp] only.
How to integrate Shopify, DGIFT-MAP #419 and status portal?
The Shopify dgift bot integration combines order API and DGIFT-MAP #419.
Shopify read fields
order_id: dgift line items, gift flag
timeline email events: sent_at, bounce
gift card admin: last4, balance, expiry, disabled
line item properties: recipient_email, scheduled_date
tags resend_count: resend tracking per order
Shopify Gift Cards API (Shopify, redeem gift card 2026).
DGIFT-MAP bot layer
Import JSON #419: dgift_type, delivery_channel, validity_days, resend_policy, extension_policy. DB-4 match per SKU dgift.
Gift status portal
bot_dgift_status_lookup: deep link buyer logged-in order status page. Shows delivery timeline + masked recipient + scheduled countdown.
App Govalo/Rise scheduled
Webhook scheduled_sent → update bot glossary delivery_status. bot_dgift_scheduled_check reads app metafield if native Shopify empty.
LMS e-product handoff
bot_dgift_access_link: cite portal URL + validity. access_denied after verify → handoff #419 DGIFT-ACCESS-01 agents enroll.
Self-service resend API
If Shopify resend gift card email API available: bot triggers 1x, increments resend_count tag. Log timestamp ticket auto-note.
What triggers and UX for DGIFT-BOT?
The DGIFT-BOT UX deployment maximizes lookup without code leak.
Five widget placements
Thank-you page dgift: T1 proactive "gift status"
/pages/digital-gifts: T4 FAQ + bot CTA
Buyer Email D+1: T1 "verify delivery status" link
Order status portal: dgift timeline widget
Christmas Peak footer: "digital gift not received?"
Not received UX flow
Bot DB-5 → if sent: spam guide 3 steps Gmail/Outlook + sender whitelist. Wait 15 min CTA. Then offer resend 1x or handoff.
Scheduled gift countdown
bot_dgift_scheduled_check: "Sending scheduled for [date] at 09:00 [TZ] to ***@email.com. Email modification: contact us before [date-1]." Handoff wrong_recipient if typo reported.
Coexistence gift-card bot
Keyword balance, checkout, apply code → bot_dgift_route_gift_card redirect gift-card article balance flow.
Last minute #129 cross-sell
T4 /pages/digital-gifts visitor: instant send only tip. Link last minute gift (#129) for urgency copy PDP.
A/B test
T1 thank-you proactive vs passive: dgift_bot_resolution + dgift_not_received_delta 4 weeks peak.
Which KPIs should the gift bot measure?
Digital gift bot KPIs link self-service and avoided chargebacks.
Eight key metrics
dgift_bot_resolution_rate: resolved without handoff / dgift_bot sessions
dgift_not_received_ticket_delta: decrease in tickets #419 not_received vs baseline
dgift_spam_first_rate: spam guide before resend / resend intents
dgift_resend_bot_convert: resend 1x bot success / resend eligible
dgift_handoff_419_rate: agent handoffs / sessions (wrong, LMS, 2nd resend)
dgift_code_leak_incident: audit full code in log (target 0)
dgift_chargeback_threat_delta: dgift dispute threats vs baseline
dgift_bot_csat: satisfaction tag dgift_bot resolved
DTC Benchmark
dgift_bot_resolution 75-85%, not_received_ticket_delta -45-55%, spam_first_rate > 90%, code_leak 0, chargeback_threat_delta -25-40% post-fix.
Weekly dashboard
Intent breakdown, scheduled vs instant split, handoff reason tags, peak Christmas vs baseline, bounce rate correlation.
Transcript audit
20 sessions/month: verify no full code, spam before resend, auth before recipient, handoff fields complete.
What anti-patterns should be avoided on bot dgift?
Ten digital gift bot anti-patterns to ban.
1. Full code in chat or log
dgift_code_leak_incident P0. Rule 3 DGIFT-BOT strict last4 only.
2. Resend without spam guide if sent logged
Rule 4: DGIFT-SPAM-01 mandatory DB-5 branch.
3. Wrong recipient reissue bot
Rule 6: handoff #419 disable old code agents only.
4. Extension expiration bot
DGIFT-EXT-01 #419 agents. Bot cites policy only, no promise.
5. Confusing confirmation #358
Buyer "did not receive payment confirmation" → CONF-EMAIL route, not dgift.
6. Checkout balance via DGIFT-BOT
bot_dgift_route_gift_card redirect. Do not diagnose balance here.
7. Resend scheduled before date
DB-5 scheduled future: explain date, no premature resend panic.
8. Recipient email full to unauthenticated
Masked only until auth DB-2 pass.
9. Chargeback promise refund bot
Rule 7 P1 handoff. Bot ack urgency + ticket fields.
10. Missing /pages/digital-gifts prerequisite
DGIFT-SUP #419 + FAQ published before bot launch.
11. Direct LMS enroll bot
access_denied → handoff #419 DGIFT-ACCESS-01. Bot portal link only.
12. 12-turn admin conversation
Max 6 turns rule 8. Portal CTA DB-7.
How does Qstomy manage status, resend, and dgift handoff?
Qstomy on Shopify: DGIFT-BOT order lookup, DGIFT-MAP explain, delivery timeline DB-5, DGIFT-SPAM-01 auto, 1x resend trigger, masked recipient confirm, handoff DGIFT-FLOW #419 pre-filled fields.
Qstomy dgift bot capabilities
dgift_order_lookup: DB-2 type, recipient, scheduled
dgift_delivery_status: DB-5 sent/bounce/redeemed
dgift_map_explain: validity, resend policy FR
dgift_spam_template: DGIFT-SPAM-01 auto
dgift_resend_once: 1x API if policy allows
dgift_handoff_419: wrong, LMS, 2nd resend, chargeback
Pipeline #420 → #419
Bot lookup spam status. Agents resend execute, reissue, enroll, extension. Shared DGIFT-MAP Notion sync.
Encrypted DTC scenario
Wellness 180 dgift/month, 64 tickets baseline #419.
After DGIFT-BOT Qstomy: dgift_bot_resolution 81%, dgift_not_received_ticket_delta -53%, dgift_spam_first_rate 94%, dgift_bot_csat 4.3/5.
Explore customer support and request a demo.
Bot vs agents routing
Qstomy routes bot_dgift_status, spam, scheduled, buyer_copy to DB-6. wrong_recipient, LMS enroll, extension, chargeback → immediate handoff #419 DG-7.
What is the checklist for deploying DGIFT-BOT?
DGIFT-BOT Checklist (12 steps)
Validate DGIFT-SUP #419 + DGIFT-MAP published /pages/digital-gifts
Export DGIFT-MAP JSON → bot glossary
Configure 12 intents bot_dgift_* section 3
Implement flow DB-1 to DB-8 + Shopify timeline read
Activate guardrails no full code + spam first + auth
Route dgift vs #358 confirmation vs gift-card balance
Thank-you widget placements + /pages/digital-gifts T4
Triggers T1-T3 D+1 email + handoff fields DB-8
Staging tests 8 scenarios: sent+spam, scheduled future, never sent, code invalid, wrong recipient handoff, buyer copy, chargeback P1, route gift-card
Gift status portal deep links + resend_count tag
Weekly dgift_bot KPI dashboard + code leak audit
A/B T1 thank-you proactive vs passive 4 weeks peak
In short
#420 = bot dgift lookup, #419 agents resend reissue
DGIFT-MAP grounded: delivery, validity, resend limit
DGIFT-BOT: auth → delivery verify → spam/resend/handoff
No full code ever: last4 only in chat
KPI dgift_bot_resolution: target > 78% post-fix
FAQ
Difference with #419?
#419 customer service agents resend LMS extension. #420 bot status spam lookup pre-filled handoff.
Does the bot resend the full code?
No. Last4 + resend email trigger or handoff #419. DGIFT-BOT rule 3.
Scheduled email not sent yet?
bot_dgift_scheduled_check mentions date. No premature resend. Email modification → wrong_recipient handoff.
Recipient vs buyer auth?
Buyer order_id + buyer email. Recipient OTP match recipient field.
Card balance at checkout?
bot_dgift_route_gift_card → gift-card balance bot article.
Go further
This week: sync DGIFT-MAP bot, configure DB-5 delivery lookup staging, test spam-before-resend flow, activate T1 thank-you widget.
Share this guide #420 with support and ops: a well-calibrated gift status bot prevents the chargeback that gets filed before the agent even opens Shopify.
2nd resend requested?
Handoff #419 DG-7 agents. Bot max 1 resend rule 5 DGIFT-BOT.
Enzo
July 1, 2026
