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