Recommend the next best action for a customer
Uses a customer's history to suggest the most helpful next step for the agent.
The prompt
Role: Act as a CX manager designing next-best-action guidance for agents.
Context: Customer signals available (product usage, tenure, tier, recent tickets, sentiment, lifecycle stage, entitlements): [SIGNALS]. Candidate actions (proactive tips, feature nudges, plan changes, retention offers, check-ins, escalations): [ACTIONS]. Business goals (retention, expansion, deflection, satisfaction) and their priority: [GOALS]. Guardrails (offer limits, do-not-contact, fairness, consent): [GUARDRAILS].
Task: Produce: (1) the signal set and how each is read; (2) for common customer situations, the recommended next best action and the reasoning, balanced across the goals; (3) the decision logic as clear rules or a decision table; (4) the guardrails as hard constraints the recommendation must never breach; (5) how an agent should present the action as a suggestion, not a script; (6) what to log to learn whether it worked.
Format: Sections: Signals | Situations -> recommended action & why | Decision table | Guardrails (hard rules) | Agent framing | Measurement.
Verification: Check no recommendation can breach a guardrail; flag situations where signals conflict and the logic is ambiguous.
Validation: Test on a churn-risk customer and a happy power user: are the actions genuinely helpful to the customer, not just to our metrics? Adjust anything that feels manipulative.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Customer Support prompts
What to fill in
- SIGNALS
- ACTIONS
- GOALS
- GUARDRAILS
How this prompt is built
This prompt follows the RCTFVV structure (Role, Context, Task, Format, Verification, Validation). RCTFVV extends RCTF with two checking steps. Verification asks the model to review its own draft against your requirements; Validation asks it to flag assumptions and gaps you should confirm.
Related prompts
- Turn resolved tickets into a knowledge-base articleHelp-center articles customers and agents can follow, built from real tickets.
- Write order, shipping, refund, and delay noticesTransactional messages: confirmations, cancellations, refunds, shipping updates, and delays.
- Handle a formal patient complaint or grievanceAn investigation plan and a written grievance response that meets common timeline and documentation expectations for healthcare organizations.
- Plan a customer onboarding kickoff callAn agenda, discovery questions, and talking points for a first onboarding call that sets clear goals and next steps.