Refunds Copilot
Copilot for Refunds, using approved data and bounded actions.
BlueprintRefunds
Learn the customer, business, technology, AI, controls, and KPIs for refunds.
Learning model: business goal → customer journey → systems/data → failure modes → AI opportunity → human control → KPIs.
Agent patterns
Refunds Monitor
Monitor for Refunds, using approved data and bounded actions.
BlueprintRefunds Recovery Agent
Recovery Agent for Refunds, using approved data and bounded actions.
BlueprintRefunds Analyst Agent
Analyst Agent for Refunds, using approved data and bounded actions.
BlueprintRefunds QA & Control Agent
QA & Control Agent for Refunds, using approved data and bounded actions.
Blueprint36 prompts
Refunds — /human
/human Explain Refunds to a fresher using a human story, then a D2C example, workflow, risks, and KPIs.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /visualize
/visualize Visualize Refunds as an end-to-end D2C flow with customer actions, systems, decisions, exceptions, and outcomes.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /diagram
/diagram Create an architecture diagram for Refunds, showing storefront, services, APIs, data, events, and human approvals.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /flowchart
/flowchart Create a decision flowchart for Refunds, including normal path, exception path, retry, escalation, and safe stop.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /mindmap
/mindmap Create a mind map for Refunds: customer, business, data, technology, AI, risks, KPIs, and owners.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /analysis
/analysis Analyse Refunds performance for a fictional D2C electronics business. Segment results, find root causes, quantify impact, and recommend actions.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /RCA
/RCA Create an RCA for a failure in Refunds: timeline, symptoms, hypotheses, evidence, root cause, containment, corrective action, prevention, and owner.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /BRD
/BRD Write a detailed BRD for improving Refunds: problem, users, scope, process, rules, integrations, errors, analytics, acceptance criteria, and exclusions.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /PRD
/PRD Create a product requirements document for an AI-enabled Refunds capability with user needs, UX, logic, APIs, controls, metrics, and rollout.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /userstories
/userstories Write user stories and acceptance criteria for Refunds across customer, operations, support, product, and admin personas.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /testcases
/testcases Generate 50 test cases for Refunds: happy, negative, boundary, integration, performance, security, accessibility, and business-rule cases.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /UAT
/UAT Create a UAT plan for Refunds with scenarios, preconditions, data, steps, expected result, owner, severity, and sign-off.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /API
/API Design APIs for Refunds: endpoints, request/response JSON, validation, idempotency, errors, auth, rate limits, and observability.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /JSON
/JSON Create realistic JSON payload examples for Refunds, including success, failure, partial, retry, and exception states.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /SQL
/SQL Write SQL analysis questions and example queries for Refunds: funnel, failures, cohorts, anomalies, SLA, and business impact.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /dashboard
/dashboard Design an executive and operations dashboard for Refunds with metric formulas, dimensions, thresholds, alerts, owners, and decisions.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /KPI
/KPI Define a KPI tree for Refunds: north-star, leading, lagging, customer, commercial, operational, quality, and risk metrics.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /agent
/agent Design an AI agent for Refunds: objective, trigger, state, tools, APIs, memory, rules, confidence, approval, audit log, KPIs, and tests.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /multiagent
/multiagent Design a multi-agent workflow for Refunds, separating planner, specialist agents, deterministic services, and human approval.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /automation
/automation Map Refunds and label every step: deterministic automation, AI assist, agent action, human approval, or human only.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /guardrails
/guardrails Create AI guardrails for Refunds: permissions, PII, policy grounding, confidence, financial thresholds, irreversible actions, audit, and rollback.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /evaluate
/evaluate Create an evaluation framework for AI in Refunds: accuracy, hallucination, precision/recall, latency, cost, safety, and business impact.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /monitor
/monitor Design production monitoring for AI-enabled Refunds: technical health, model quality, drift, customer harm, business metrics, and alerts.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /incident
/incident Create an incident playbook for Refunds: detect, classify, contain, communicate, recover, reconcile, and learn.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /SOP
/SOP Write an operations SOP for Refunds with roles, prerequisites, normal process, exception handling, escalation matrix, and daily controls.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /checklist
/checklist Create a launch-readiness checklist for Refunds: business, UX, content, data, API, QA, security, analytics, support, and rollback.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /roadmap
/roadmap Create a 90-day roadmap to improve Refunds: baseline, quick wins, experiments, AI opportunities, dependencies, milestones, and KPIs.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /prioritize
/prioritize Prioritise 15 improvement ideas for Refunds using impact, effort, confidence, customer value, risk, and dependency.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /executive
/executive Create a one-page executive review for Refunds: performance, customer impact, revenue impact, top risks, actions, owners, and decisions.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /interview
/interview Create 20 interview questions and model answers about Refunds for ecommerce, product, and AI manager roles.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /quiz
/quiz Create a 15-question quiz on Refunds: beginner to advanced, with answers and explanations.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /project
/project Create a portfolio project for Refunds using fictional data: problem, dataset, analysis, AI solution, architecture, prompts, evaluation, and presentation.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /promptEvolution
/promptEvolution Improve a weak Refunds prompt through beginner, structured, expert, and agent-level versions.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /sales
/sales Create five D2C sales scenarios for Refunds, including intent, recommendation logic, objection, guardrail, and conversion KPI.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /cs
/cs Create five customer-service scenarios for Refunds, including customer message, system checks, grounded response, escalation, and KPI.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.
Refunds — /ops
/ops Create five operations scenarios for Refunds, with exception, evidence, decision, owner, SLA, and preventive control.Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.