客服退款 Bot：政策内退款先拟后批 Customer Support · in-policy refunds

这条用法在做什么What this use does

官方扩容角色 Customer support：阅读支持邮件并接入支付服务商，处理政策内的常规退款。Gergely Orosz 在 2026-08-19 公开过同一形态：Grok Bot 连接支持邮箱与 Stripe API，每笔先在 Bot 界面确认再打款。 Official expansion role Customer support: reads support mail, connects to the payments provider, and handles routine in-policy refunds. Gergely Orosz published the same shape on 2026-08-19: Grok Bot on support email plus the Stripe API, confirming each refund in the Bot UI before money moves.

收录理由Why we listed it 官方角色 + 社区真人跑通：政策内退款是钱，必须先拟草稿、人点头。和已有的收件箱分拣不同，这条连到支付 API。 Official role plus a real community run: in-policy refunds are money, so draft first and wait for a nod. Distinct from inbox triage because it talks to the payments API.

上手路径How to start

1. 先跑一次安全范围Run a safe first pass

   先在可撤回、不外发的范围内试跑。本条未批准前：不发起退款、不改支付方式、不自动回复顾客；先提交订单号、金额、政策对照与待批草稿。。 Try it first in a reversible, non-outbound scope. Until approved: Do not issue a refund, change the payment method, or auto-reply to the customer; first return order id, amount, policy check, and a draft for approval..

2. 存 SkillSave a Skill

   这条用法已包含可复用 Skill。跑通安全范围后，立刻把步骤固化下来。 This use already includes a reusable Skill. After the safe pass, lock the steps in.

3. 再上 RoutineThen add a Routine

   输出稳定后再打开例行 / 定时。本条已有例行形态，不要一上来就无人值守外发。 Turn on the routine / schedule only after output is stable. This item already has a routine shape — do not start unattended outbound.