E-commerce
July 1, 2026
“Where do we stand with our pool for Sophie?” “How much is left to collect before Friday?” “How can I add my message without everyone seeing my amount?” Three messages where an organizer or contributor without a self-service lookup pool opens a ticket even though GGRP-MAP and the pool dashboard already contain status, deadline, and message policy.
An e-commerce group gift AI chatbot does not replace GGRP-FLOW agents (#433). It reads GGRP-MAP, quotes pool progress, budget target, single recipient address, common message rules, and name visibility, then routes share reimbursement or dispute to #433.
This guide #434 covers intents bot_ggrp_*, flow GGRP-BOT, and KPI ggrp_bot. Distinct from group gift customer service (#433) and the digital gift bot (#420): here, collaborative purchase AI use case: coordinate budget, recipient, and single delivery.
Summary
Why does a group gift bot reduce pool tickets?
An avoidable group gift ticket is born when the organizer or a contributor cannot find the pool status, remaining crucial amount, closing deadline, or message rules before reaching out to support.
Five triggers for botifiable ggrp tickets
Pool status: collected/target, how much is remaining
Contribution link: how to pay my share
Deadline countdown: closes Friday, still open
Common message: add text, who sees what
Recipient address: where the single gift will be delivered
Shopify does not handle native split payments on an order (Shopify, checkout 2026). Pools via app or gift cards require a bot layer that reads GGRP-MAP and pool API. Tidio estimates that a tier 1 gift bot reduces contribution status tickets by 42-55% vs a static FAQ (Tidio, chat stats 2026).
Angle #434 vs neighboring content
Group CS #433: GGRP-FLOW refund ship dispute execute. #434 = bot tier 1 pool status budget message address policy.
Solo gift #205: one payer hidden price. #434 = N payers pool organizer contributor.
Dgift bot #420: scheduled digital code. #434 = collective physical or digital pool.
Corporate bulk #158: 1 payer N addresses. #434 = N payers 1 address inverse.
Gift finder: pre-purchase product choice. #434 = pool coordination post-campaign start.
DTC Example
Home decor 95 pools/month, 22 baseline tickets #433. After GGRP-BOT: ggrp_bot_resolution 85%, ggrp_ticket_delta -47%, ggrp_pool_status_self_service 72%.
Organizer vs contributor bot paths
Organizer auth: address edit policy, message lock, ship trigger handoff. Contributor auth: own part + public pool status only.
Gorgias group gift chargeback context
Gorgias: multi-party gift disputes 2.2x chargeback vs solo without visible pool status. Bot status transparency reduces perceived fraud contributor side.
How does GGRP-BOT differ from GGRP-FLOW #433?
Self-service bot pool and group gift agent playbook: two layers on GGRP-MAP #433.
Bot ggrp → role matrix
#434 GGRP-BOT: pool status, budget target, deadline, message policy, address cite, contribution link
#433 GGRP-FLOW: refund part execute, ship trigger, message edit locked, chargeback P1
#420 DGIFT-BOT: single digital code resend
#205 gift solo: hide price single buyer
Upstream router
"Where is the pool at", "how much is left", "contribution link", "group message", "delivery address", "names on card" → GGRP-BOT. "Refund my share", "not shipped full pool", "edit message after sending", "scam" → handoff #433 GF-6.
GGRP-BOT Data
GGRP-MAP JSON #433, pool_id API app or Sheet, collected/target, deadline, message_mode, name_visibility, organizer email, ship status, contributor ledger read-only.
#434 Promise
GGRP-BOT Policy, 12 intents bot_ggrp_*, flow GB-1 to GB-8, guardrails no refund bot, KPI ggrp_bot_*.
Pre-campaign vs active pool
bot_ggrp_organizer_start: visitor how to create pool. Active pool: bot_ggrp_pool_status auth pool_id + email role.
Which bot_ggrp_* intents should be configured?
Twelve group gift bot intents cover tier 1 pool and routing dispute.
Twelve bot_ggrp intents
bot_ggrp_pool_status: collected/target, contributors count, open/closed/shipped
bot_ggrp_contribution_link: contribute my share URL
bot_ggrp_target_budget: target amount shopping cart product
bot_ggrp_deadline: closing date countdown
bot_ggrp_message_policy: common message, max chars, lock rules
bot_ggrp_message_submit: form link to add contributor snippet
bot_ggrp_name_visibility: card names anonymous_group policy
bot_ggrp_address_confirm: unique recipient address organizer view
bot_ggrp_recipient_info: who receives, no individual amounts
bot_ggrp_organizer_start: create pool pre-campaign guide
bot_ggrp_handoff_433: refund, not shipped P1, chargeback, message edit locked
bot_ggrp_route_solo_205: solo gift redirect single payer
Session tags
ggrp_bot, ggrp_bot_organizer, ggrp_bot_contributor, ggrp_bot_resolved, ggrp_bot_handoff_433. Distinct gift_bot, dgift_bot, corp_bulk.
Triggers T1-T5
T1: pool creation confirmation page proactive status link. T2: keyword cagnotte/cotisation/pot commun/groupe. T3: email threshold 80% bot pool status deep link. T4: /pages/group-gifts FAQ. T5: deadline D-2 proactive countdown organizer.
How to apply the GGRP-BOT flow in eight steps?
The GGRP-BOT flow guides pool grounded GGRP-MAP #433 and API pool ledger.
Eight steps GB-1 to GB-8
GB-1 Welcome: "I am checking your pool: progress, deadline, delivery."
GB-2 Auth role: pool_id + email → organizer vs contributor vs visitor
GB-3 Classifier intent: bot_ggrp_* section 3
GB-4 Match GGRP-MAP: ggrp_type, message_mode, name_visibility, refund policy
GB-5 Read pool data: collected, target, deadline, ship status, address masked
GB-6 Respond: GGRP-STATUS style | contribution link | message policy | address organizer
GB-7 CTA: pool dashboard | message form | /pages/group-gifts
GB-8 Close/handoff: refund ship dispute chargeback → #433 GF-6
GB-5 pool_status
Cite collected/target €, N contributors, deadline date, status open/closed/shipped. If complete unshipped → cite GGRP-NOT-SHIPPED ETA if known, else handoff #433 if overdue P2.
GB-6 address_confirm
Organizer auth only: full address cite. Contributor: city only or "address confirmed by organizer" privacy.
GB-6 message_submit
If pool open + message_mode common_card: deep link contributor message form. If locked J-2 → bot_ggrp_message_policy explain no edit bot, handoff #433 organizer request.
GB-2 contributor part lookup
Contributor auth: cite own contribution amount + date, not other contributors amounts privacy.
GB-5 digital pool variant
grp_digital_pool closed: cite gift card/dgift delivery recipient not physical address. Link #419 if resend needed handoff.
Overfund bot cite
If collected > target flexible GGRP-MAP: GB-6 explain surplus gift card recipient or charity option #433 policy.
Which GGRP-BOT policy should be documented?
The GGRP-BOT group gift bot policy governs status cite, privacy, and handoffs.
Eight GGRP-BOT Rules
GGRP-MAP only: message_mode, name_visibility, deadline from JSON #433
Pool data API/Sheet: GB-5 collected target from ledger, no LLM inventing
Auth role gate: full address organizer only, contributor partial privacy
No individual recipient amounts: bot never cites "Marie €30" to contributor cross-view
No bot-executed refund: bot_ggrp_handoff_433 refund part ship dispute
Message lock uphold: after D-2 lock explain policy, handoff #433 edit request
Single address cite: one delivery per pool, no multi-address promise bot
Max 6 turns ggrp admin: then dashboard CTA or handoff #433
RAG Sources Corpus
/pages/group-gifts, GGRP-MAP #433, GGRP-SUP #433, macros GGRP-STATUS GGRP-NAMES from #433 section 7.
Sync ops
Pool deadline extend ops → bot glossary + auto-notify open sessions pool_id. Target change → GB-5 refresh.
Monthly review
Audit: wrong pool status, contributor amount leak, address over-share, refund promise bot.
Chargeback keyword P1
Scam + pool_id → immediate bot_ggrp_handoff_433 P1 fields pool ledger timeline.
Fevad seasonal bot boost
Nov-Dec widget proactive bot_ggrp_organizer_start on gift category PDP. Align Fevad 78% online gift buyers peak.
What guardrails protect budget and confidentiality?
The bot ggrp authorized vs forbidden matrix protects contributors and recipients.
Authorized bot actions
Cite pool collected/target/deadline/status GB-5
Share contribution link bot_ggrp_contribution_link
Explain message_mode name_visibility GGRP-MAP
Organizer full address cite if auth
Contributor own part amount date lookup
bot_ggrp_organizer_start guide create pool link
Handoff #433 refund not shipped chargeback message locked
Forbidden bot actions
Process contributor refund API bot
Trigger ship fulfillment bot
Edit common message after lock bot
Reveal other contributors amounts to contributor
Reveal contributor names if anonymous_group policy
Promise multi-address delivery one pool
Anti-hallucination budget
Template: « Pool #[id]: [collected]/[target] €, closing [date], status [status]. » All numbers from GB-5 JSON only.
Recipient surprise privacy
Bot never confirm recipient identity to wrong email. Auth pool organizer or contributor match ledger.
Price hide #205 apply
bot_ggrp_recipient_info: recipient never sees individual contribution amounts or packing slip prices bot cite.
How to connect GGRP-MAP #433 and apps pool?
The group gift bot integration combines GGRP-MAP, the API app pool, and the Shopify organizer order.
GGRP-BOT read fields
pool_id status: open, closed, shipped
collected / target: ledger sum
contributors_count: N unique payers
deadline_at: ISO close date
organizer_order_id: Shopify final ship order if shipped
shipping_address: organizer entered masked contributor view
GroupTogether, Presently, and Rise group gifting webhooks apps (Shopify, gift cards 2026 for manual pool variant).
GGRP-MAP bot layer
Import #433: ggrp_type, message_mode, name_visibility, refund_part_policy, target_flexible. GB-4 per pool.
Manual pool Sheet sync
grp_pool_manual: Google Sheet → bot read cache 15 min. Lag flag → bot quotes "status within 15 min" honest.
Organizer order link post-close
Pool closed → Shopify order created → GB-5 ship status from fulfillment API. Tracking quotes organizer auth.
Qstomy Integration
See Shopify integration + pool app webhook for GGRP-MAP RAG sync.
What are the campaign, deadline, and UX triggers for GGRP-BOT?
The GGRP-BOT UX deployment maximizes organizer deflection and pool complete conversion.
Five widget placements
Pool dashboard embed: T1 bot chip status refresh
/pages/group-gifts: T4 bot_ggrp_organizer_start + FAQ
Email 80% threshold: T3 bot link collected/target
Contribution thank-you page: T2 pool status + message form link
Deadline D-2 organizer: T5 countdown + top-up remind
Organizer dashboard bot chip
"Pool status" chip on app dashboard opens bot_ggrp_pool_status + bot_ggrp_address_confirm one-shot. Reduce organizer email support by 50% historically.
Contributor post-pay flow
After contribution: bot_ggrp_pool_status public + bot_ggrp_message_submit CTA if open. Engagement increases message collect rate by 35%.
Pre-campaign PDP chip
"Give as a group?" bot_ggrp_organizer_start + target product link. Complements gift finder, does not replace.
A/B test
T3 80% email bot link vs static: ggrp_bot_resolution + pool_complete_rate delta 4 weeks.
Seasonal peak staffing
Nov-Dec: T5 deadline proactive daily organizer with incomplete pools. Fevad Christmas volume context.
WhatsApp share contribution link
bot_ggrp_contribution_link short URL for organizer share group chat. Track ggrp_contribution_link_convert by channel.
What KPIs should the ggrp bot measure?
The group gift bot KPIs link deflection pool and completion rate.
Eight Key Metrics
ggrp_bot_resolution_rate: resolved without handoff / ggrp_bot sessions
ggrp_ticket_delta: decrease in tickets #433 vs baseline
ggrp_pool_status_self_service_rate: status bot / status questions
ggrp_contribution_link_convert: contributions after bot link / link sessions
ggrp_message_submit_bot_rate: message form opens from bot / open pools
ggrp_handoff_433_rate: refund ship dispute routed agents
ggrp_pool_complete_rate: pools hit target / pools opened bot cohort
ggrp_bot_csat: satisfaction tag ggrp_bot resolved
DTC Benchmark
ggrp_bot_resolution 82-92%, ggrp_ticket_delta -42-52%, pool_status_self_service > 68%, ggrp_bot_csat > 4.3/5.
Monthly Dashboard
Intent breakdown organizer vs contributor, handoff reasons, pool complete bot vs no-bot cohort.
Transcript Audit
20 sessions/month: amounts grounded ledger, no amount leak, role auth correct, handoff #433 timely.
Pool Complete Correlation
Track bot Q3 80% email open → complete rate uplift. Target +8-12% complete vs control.
Organizer Repeat Pool KPI
Track organizers creating 2+ pools after bot positive CSAT. ggrp_bot drives repeat campaign ops metric.
Deadline Missed Bot Path
Past deadline under target: GB-6 offer extend 48 h, top-up, refund all per GGRP-MAP. No silent pool abandon.
What anti-patterns should be avoided on a group gift bot?
Ten group gift bot anti-patterns to banish.
1. Invent collected amount LLM
Rule 2 GB-5 API only. Wrong target destroys organizer trust.
2. Refund part bot execute
Rule 5 handoff #433. Finance ledger bot API forbidden.
3. Contributor amounts cross-leak
Rule 4 privacy. Social awkwardness + policy violation.
4. Address full to contributor
Rule 3 organizer auth full. Contributor city only if policy.
5. Message edit after lock bot
Rule 6 handoff #433. WMS may have picked GGRP-MESSAGE.
6. Confondre solo #205
bot_ggrp_route_solo redirect single gift checkout.
7. Skip GGRP-SUP #433 prérequis
/pages/group-gifts GGRP-MAP before bot. Empty RAG wrong policies.
8. Multi-address promise
Rule 7 single address. #409 or #158 not ggrp pool.
9. Ship promise bot pool incomplete
Status open + collected < target → no ship ETA promise.
10. Conversation 12 tours
Max 6 turns Rule 8. Dashboard pool CTA GB-7.
11. Anonymous_group leak names
GB-4 name_visibility audit. Bot list contributors forbidden if anonymous.
12. Corporate bulk conflate #158
Company 120 addresses ≠ group pool 1 address. Router distinct.
13. Stale Sheet cache bot
grp_pool_manual : if cache > 15 min flag honest "updating in progress". Stale status worse than loading state.
How does Qstomy coordinate budget, recipient, and delivery?
Qstomy on Shopify: GGRP-BOT pool lookup, GGRP-MAP message name policy cite, GGRP-STATUS-01 auto, organizer contributor role route, handoff #433 refund ship pre-filled fields.
Qstomy ggrp bot capabilities
ggrp_pool_lookup: GB-5 collected target deadline
ggrp_map_explain: message_mode name_visibility refund
ggrp_contribution_link: bot_ggrp_contribution_link generate
ggrp_role_auth: organizer vs contributor GB-2
ggrp_address_organizer: full address auth gate
ggrp_handoff_433: P1 chargeback not shipped fields
Pipeline #434 → #433
Bot tier 1 pool status budget message address policy. Agents refund ship dispute execute. Shared GGRP-MAP.
Encrypted DTC scenario
95 pools/month, 22 baseline tickets #433.
After GGRP-BOT Qstomy: ggrp_bot_resolution 87%, ggrp_ticket_delta -49%, ggrp_pool_complete_rate +10%, ggrp_bot_csat 4.5/5.
Explore customer support and request a demo.
Corpus sync training
See train Shopify chatbot for GGRP-MAP RAG sync on pool policy update.
What is the checklist for deploying GGRP-BOT?
GGRP-BOT Checklist (12 steps)
Validate GGRP-SUP #433 + GGRP-MAP /pages/group-gifts
Export GGRP-MAP JSON + pool app API or Sheet webhook
Configure 12 intents bot_ggrp_* section 3
Implement flow GB-1 to GB-8 + role auth GB-2
Enable guardrails no refund/ship/message edit + amount privacy
Route ggrp vs #433 #205 #420 #158
Placements pool dashboard T1 + /pages/group-gifts T4 + contribution page T2
Triggers T3 80 % email + T5 deadline D-2 organizer
Staging tests 8 scenarios: status, contribution link, message policy, name visibility, address organizer, contributor privacy, handoff refund, handoff not shipped
Organizer vs contributor auth paths validated
Dashboard KPI ggrp_bot monthly + privacy audit
A/B T3 80 % email bot vs static 4 weeks
Summary
#434 = bot pool tier 1, #433 agents refund ship dispute
GGRP-MAP grounded: budget, message, names, address policy
GGRP-BOT: auth role → pool data → status/CTA → handoff
GB-5 ledger only: no fabricated amounts
KPI ggrp_bot_resolution: target > 85 %
FAQ
Difference with #433?
#433 CS refund part ship message edit execute. #434 bot pool status budget deadline message policy.
Does the bot refund my contribution?
No. bot_ggrp_handoff_433 #433 GF-7 refund if pool open policy.
View recipient's address as a contributor?
Organizer auth full address. Contributor partial privacy per GGRP-MAP.
Group message via bot?
bot_ggrp_message_submit link form if open. Locked → policy explain handoff #433.
Solo gift instead of group?
bot_ggrp_route_solo_205 redirect #205 single buyer flow.
Go further
This week: sync GGRP-MAP bot per ggrp_type, configure GB-5 pool API staging, test organizer vs contributor auth paths, enable widget pool dashboard T1 + email 80 % T3.
Share this guide #434 with support and ops: a bot that quotes « €87/120, closing Friday, group message locked D-2 » is worth ten reassured organizers, a fabricated amount is worth five contributor chargebacks.
Incomplete pool past deadline?
GB-6 quotes GGRP-MAP extend/top-up/refund options. Execute → handoff #433 GF-6.
Enzo
July 1, 2026
