Post-Purchase
Watches new orders and sends delivery updates, review requests and replenishment nudges through your connected channel. Where COD exists it confirms the order and scores return risk, then flags risky orders to you. It never cancels anything.
Who it is for
The owner shipping COD orders who finds out about returns three weeks later, and anyone who wants every order followed up without doing it by hand.
What it reads from the brain
Before every run. Sections are addressed as layer.section.
What it does, step by step
- Read the brain
Opens the sections above and the inputs.
- Gather evidence
Lists recent orders. Every finding cites its source.
- Decide and draft
Drafts the message set (confirmation where COD exists, delivery update, review request, replenishment nudge) in your voice using only claims_allowed, and scores return risk from your market playbook's rules.
- Advise stops here
You get the drafted templates and the risk scored order list.
- Act
Registers the new order webhook and, for each new order, sends the pre approved template through the connected channel. Risk flags reach you as a digest, never as a cancellation.
- Write back
What did not work is appended to the brain.
Tools it uses
shopify.orders.listRecent orders to score and follow upshopify.webhooks.registerAct: the orders create webhookwhatsapp_business.send_templateApproval gated. Pre approved templates only, through the Meta Cloud APIemail.sendApproval gated. The email channel where WhatsApp is not connectedjudgeme.review_request.sendReview request timed to delivery, one per order
The three modes for this agent
Read tools only. You get the drafted templates and a risk scored list of recent orders.
Webhook registered. Each new order gets the pre approved template through your channel; every send on the messaging list waits for approval of the template set.
Every 30 minutes. Same gates. Runs on every order, day and night.
Guardrails and approvals
Enforced in code. Items with a filled circle wait for your tap in Telegram.
- Never cancels an order. Only flags and holds.
- Templates pre approved only.
- One review request per order.
- COD confirmation only where your market playbook says COD exists.
- Daily message cap per customer.
- Every claim in every draft is in claims_allowed or is removed and listed as needs your confirmation.
What it writes back to the brain
Dated and sourced. Learnings and performance sections are append only.
Example output
Example output. Structure only. Counts are placeholders.
Post-Purchase, your store, last 30 minutes
Ran at data level 3 (Shopify and WhatsApp connected).
- New orders: [n]. Confirmation sent (COD, per your market playbook): [n]. Delivery update queued: [n]. Review request scheduled for after delivery: [n].
- Return risk flagged: [n] orders, listed below with the playbook rule that fired. Held for you. Nothing cancelled.
orders.csv (columns)
order_id | placed_at | payment_type | action_taken | risk_score | rule_fired | status
Also delivered: messages.md (every message sent or drafted, with the template id and channel).
Planned: the risk score scale and the replenishment nudge timing per product are set from your market playbook and order history and are not fixed in the contract yet.