Short answer: Use this workflow to organize product facts, an ideal customer profile, approved claims, qualification rules, objections, and next-step criteria into a reviewable call structure. It improves consistency without promising a close rate or inventing customer proof.
This page is a practical prompt workflow. Treat every bracketed field as required input; do not ask an AI system to invent facts, citations, customer results, credentials, compliance conclusions, or financial outcomes.
When not to use this workflow
- Product facts, pricing, eligibility, or support terms are not approved.
- The script would pressure a buyer, misrepresent a competitor, or make a regulated claim.
- You are using generated objections as evidence of actual customer research.
Variables to provide
| Variable | What to provide | Quality check |
|---|---|---|
[Ideal customer profile] |
Role, company context, problem, buying stage, and disqualifiers | The profile is specific enough to change the conversation. |
[Product facts] |
Features, limits, pricing, implementation, and support terms | Claims are sourced from current approved materials. |
[Objections] |
Observed objections, questions, and uncertainty | Observed and hypothetical objections are labelled separately. |
[Qualification rules] |
Required information, fit criteria, and disqualifiers | Rules support respectful qualification, not pressure. |
[Next-step criteria] |
Mutual action, owner, date, and information needed | The next step is optional, concrete, and reviewable. |
Copy-ready prompt
You are a sales-enablement drafting assistant. ICP: [ICP]. Approved product facts: [FACTS]. Pricing and limits: [TERMS]. Observed objections: [OBSERVED OBJECTIONS]. Hypothetical questions: [HYPOTHESES]. Qualification rules: [RULES]. Next-step criteria: [NEXT STEP].
Return: (1) an opening and discovery sequence, (2) objection branches with factual responses, (3) questions that test fit, (4) prohibited or unsupported claims, (5) a respectful close with an optional next step, and (6) a manager QA checklist. Do not guarantee results, invent customers, misrepresent competitors, or pressure a buyer. Mark unverified items [REVIEW].Example prompt failure
Illustrative example only — not a customer run and not evidence.
Write a persuasive sales script that handles every objection and closes more deals.
The illustrative prompt asks for a stronger close without product facts, objections, qualification rules, or approved claims. It encourages generic persuasion and unsupported proof.
Why the controlled version is safer
The controlled version separates observed evidence from hypotheses and forces the script to respect product limits. It creates a review checklist rather than claiming a conversion lift.
- Confirm the source set, version, audience, and owner.
- Run the prompt with the required fields; leave unknowns labelled rather than filling them.
- Compare each factual sentence with its source and record any judgement call.
- Obtain the named reviewer approval before publication or external use.
Proof-of-execution record
Empty proof template — no execution claim. Complete this section only after a real, permissioned run. Redact confidential customer, employee, supplier, personal, and commercially sensitive data.
- Model family and version
- [Record the actual model and version]
- Run date
- [YYYY-MM-DD]
- Input excerpt
- [Paste a short approved excerpt]
- Observed output
- [Paste a short approved excerpt or write “not recorded”]
- Human reviewer
- [Name or role]
- Changes made
- [Record edits and why]
- Limitations
- [Record failure cases, missing evidence, and unresolved questions]
Limitations and reviewer responsibility
A script cannot substitute for customer research, product accuracy, sales training, or legal review of claims. Managers should sample calls and update the source facts.