Flickr — Pro Refund Automation (Zendesk + Stripe)
End-to-end Flickr Pro refund handling. Pulls the Zendesk ticket, classifies it, looks up the member in Flickr admin and the subscription/charge in Stripe, then applies Flickr's refund policy written in plain English (editable per run). Code guardrails (auto-approve $ limit, identity match, AI confidence, Trust & Safety flags) force escalation to a human approver. Issues the Stripe refund / cancels auto-renew, downgrades the account, writes an internal note + customer reply to Zendesk and returns a full audit trail. Scenarios: auto_approve (forgot auto-renew, 3 days ago), needs_approval (second refund in 12 months -> human approval), decline (renewed 5 months ago, heavy use -> decline + auto-renew off). Mocked Zendesk/Stripe/Flickr admin; credential-free.
Shared by Ajain Vivek · Brainfish.
Remixed 2 times on Ballet.
How it works
- Pull the new refund ticket from Zendesk (mocked) — Pulling the new refund ticket from Zendesk…
- AI reads the ticket: intent, reason, username, cancellation wish — Reading the customer's request…
- Find the member in Flickr admin and verify the requester owns it — Looking up the member in Flickr admin…
- Pull the Stripe customer, subscription, latest charge and refund history — Checking the subscription and charges in Stripe…
- AI applies Flickr's plain-English refund policy; code guardrails can force human review — Applying Flickr's refund policy…
- Escalated refunds pause for a support lead to approve or deny, with full context — Waiting for a support lead to approve…
- Issue the Stripe refund / cancel auto-renew and downgrade the Flickr account — Updating Stripe and the Flickr account…
- AI drafts the internal Zendesk note and the customer reply — Writing the reply to the member…
- Post the private note + public reply to Zendesk, tag and solve; return audit trail — Updating the Zendesk ticket…
- Render the run as a one-page HTML dashboard for the demo — Building the run dashboard…
Remix this playbook