AI for sales: grounded replies as customer questions change
Use a conversation history and product-policy pack to separate resolved questions from current ones, repair unsupported promises and respect contact constraints.
About 27 min readingAs of Oct 2026
Lesson guide · goals & preparation
By the end of this guide
- Separate resolved and open questions in a conversation history.
- Trace commitments in a reply to supplied product and policy facts.
- Distinguish contact constraints from a narrow one-off exception.
Who this is for
- People drafting AI-assisted replies after an initial customer discussion
- People who need to prevent mixed-up turns and unsupported commitments
What you need
- The call-notes lesson introduces evidence IDs and unresolved fields.
- All products, customers, policies and dates are fictional editorial teaching material, not real service or contract terms.
- This website does not execute AI. Read the sources, requests and editorial solutions without an account; using an external assistant is optional.
1 / 4
Theory
Understand what to ask AI to do, how to ask, and the ideas behind the workflow.
When the security question is closed but the same pitch returns
A customer says, “We have reviewed the security material. Now we need the termination terms.” An AI draft repeats the security pitch and promises free cancellation. Politeness does not fix either problem: it answers an old question and invents a policy. This lesson uses the fictional product Moadesk to distinguish them.
The assistant’s assignment is to identify the current question and separate supported answers from items needing confirmation. Product facts come from the product pack; question status comes from the latest conversation. Neither source can substitute for the other.
Every customer statement, date and policy here is editor-created. Worked replies and bad drafts are not model transcripts. Running a request externally is optional: you can follow each claim back to its ID by reading. This site neither generates nor sends the message.
Prepare chronology separately from product facts
The practice date is October 30, 2026. Read C1–C3 in order. C1’s question does not remain open forever: C2 acknowledges the security material and changes the current question to termination. Preserve chronology and speaker when supplying a long thread to AI.
Figure: keep resolved and current questions in chronological order · AI Ping P1–P3 define the fictional product facts. K1 says termination requires the executed contract and confirmation by its owner. That contract is absent. General knowledge of SaaS practices cannot establish this customer’s cancellation or refund rights.
IDs are return addresses for checking claims. P1 does not establish SSO on every plan; read its restriction too. SSO means using a company sign-in across services. This exercise concerns only the eligibility stated in P1.
Fictional source pack · as of October 30 ID Source statement C1 · October 20 Customer: Please provide company sign-in and security information. C2 · October 28 Customer: Security material reviewed. We now need termination terms. C3 · October 28 Customer: Contact us only by email from November 10. Please do not call. P1 Company SSO is provided on the Enterprise plan. P2 Administrator audit logs retained for 90 days. P3 A security summary for review can be provided on request. K1 Termination and refund terms require the executed contract and contract-owner confirmation; no clause is supplied here.
2 / 4
Step-by-step use
Learn what to prepare, how to request help and how to revise the result through examples and explanations.
Request question status and evidence before a reply
Split the request into status extraction and supported reply preparation. Starting with “write a persuasive email” makes it easy to repeat C1 or fill K1 with invented cancellation promises. A status table lets you inspect the purpose before polishing sentences.
C3’s contact window has not opened on the practice date. The deliverable is an internal draft for later review. An internal action to check a contract is distinct from contacting the customer now. No schedule or automatic delivery is created here.
The editorial table below is neither an AI reply nor a performance measurement. C2 acknowledges reviewing security material; it does not establish a passed security audit or approved purchase. Preserve that exact strength of claim.
Example prompt Use only fictional C1–C3, P1–P3 and K1, with practice date 2026-10-30. First tabulate resolved question, current question, contact constraints, supported facts and terms needing confirmation, with IDs. Do not turn security-material review into approval or infer termination/refund terms. Then write an internal reply draft consistent with contact constraints. Do not imply it has been sent or scheduled.
Worked example & explanation Editorial completed status table. A reply need not list every feature; K1 and C3 matter to the current question.
Editorial solution · what needs answering now Field Record Resolved question Security material reviewed (C2); approval unknown. Current question Termination terms (C2); definitive answer held without clause (K1). Contact constraint Email only from November 10; no calls (C3). Internal draft now. Internal next step Check executed termination clause with contract owner (K1); not yet completed. Repair the free-cancellation and call-today promises
The editor-created error reads: “Security is approved, so SSO is available on every plan. You may cancel free at any time; I will call today.” It invents approval, drops Enterprise eligibility, invents cancellation terms and violates timing/channel constraints. More polite phrasing would preserve all four errors.
Figure: trace reply claims to evidence and remove unsupported commitments · AI Ping Request those four repairs explicitly: retain review rather than approval, restore P1 eligibility, remove free cancellation in favour of K1 confirmation and delete the call. Keep an internal draft, show C3 and reduce irrelevant security repetition. Specify what must survive shortening, especially unresolved terms.
The editorial reply draft reads: “Thank you for reviewing the security material. The termination terms you asked about require the applicable executed-contract clause and confirmation by its owner. We will review the verified information before advising you.” Its separate internal note says “Email only from November 10; no calls; do not confirm terms before checking.” It claims neither delivery nor completed review.
If SSO is relevant, use only “SSO is provided on Enterprise (P1).” P2’s 90-day audit-log retention is not a post-termination deletion deadline. The same number can refer to different things; preserve its subject and conditions.
After repairing the four claims, recheck that the draft still addresses termination. Repeating a security pitch returns to the old question. An internal evidence table and customer-facing text have different purposes; a person selects the actual recipient version without mixing in internal notes.
Keep a one-off request narrower than general contact permission
New fictional C4 arrives on November 6: “Please email one security summary today. Keep all other contact under the existing conditions.” A document request does not reopen security approval or resolve termination. Identify the requested item without rewriting the whole conversation’s purpose.
C4 grants a narrow exception to C3: one document email. It permits neither calls nor earlier general follow-up. Ask AI to separate changed permission from retained restrictions. The editorial solution prepares one checked summary under P3 while retaining email-only general contact from November 10.
For the editor-created error “Contact is permitted, so call today and explain contract terms,” request: “Limit the exception to one security-summary email; retain the existing restrictions for general contact and calls, and leave contract terms unresolved.” C4 supplies no contract clause, so K1 still matters.
The editorial handover says: “November 6: prepare only the requested checked summary email (C4/P3). Keep C3 for general contact. Await contract-term confirmation (K1).” Do not record an attachment as complete without checking the actual file. This exercise stops at preparation and status interpretation.
Keeping only the latest message loses why the question changed; freezing all earlier conditions ignores a valid narrow exception. Preserve the source thread and update the status table. A changed/retained comparison limits the revision scope without rewriting history.
3 / 4
Check & explain
Think about what you would ask AI, then read the explanation. Written submissions and external AI use are optional.
This is a learning check, not a test you must pass. Use the explanations to understand the ideas.
Q1P2 retains logs for 90 days. Can the reply promise deletion of all data 90 days after termination?
Write your thoughts (optional)
Your writing is not sent anywhere. It disappears when you leave or reload this page, so copy anything you want to keep.
Read the answer and explanation
No. P2 concerns administrator audit-log retention, not deletion of all data after termination. Leave the latter unresolved under K1 pending the contract and its owner. All policies are fictional practice material.
This is your own review, not an automatic score.
Q2Repair “Security audit passed” using C2.
Write your thoughts (optional)
Your writing is not sent anywhere. It disappears when you leave or reload this page, so copy anything you want to keep.
Read the answer and explanation
Write “The customer reviewed the security material.” Reading a document differs from audit approval or a purchase decision. Retain only the scope established by C2.
This is your own review, not an automatic score.
Q3C4 arrives. Can you call today and send general sales follow-up on November 9?
Write your thoughts (optional)
Your writing is not sent anywhere. It disappears when you leave or reload this page, so copy anything you want to keep.
Read the answer and explanation
C4 permits only that day’s requested security-summary email. Calls remain prohibited; general contact remains email-only from November 10 under C3. Do not expand the fictional customer’s one-off request into blanket permission.
This is your own review, not an automatic score.
Q4AI fills K1’s gap with “Cancel free at any time.” Write one focused revision request.
Write your thoughts (optional)
Your writing is not sent anywhere. It disappears when you leave or reload this page, so copy anything you want to keep.
Read the answer and explanation
Ask: “Remove only free cancellation and state that termination/refund terms require the executed contract and owner confirmation; retain security-review status and contact constraints.” Replace an unsupported promise with an unresolved field, not another plausible policy.
This is your own review, not an automatic score.
Common mistakes
- Turning reviewed material into security approval or a purchase commitment.
- Extending one plan’s feature to every plan.
- Treating a one-off document request as removal of general contact constraints.
Your learning record
Completion is optional. Mark this lesson when you feel ready, or move to the next lesson without marking it.
Completion is saved in this browser.
4 / 4
Apply to your work
Consider how new material changes the workflow and checking criteria. Trying an external AI tool is optional.
Try it: trace three reply claims
Hide C4 and use only the October 30 pack. Can termination terms be confirmed, can you call now, and does reviewing security material imply purchase approval? Trace each decision to the sources without a customer account or AI service.
Reveal C4 and mark its single contact exception while retaining unknown contract terms and the call restriction. A customer can finish reviewing a document and still request another copy; document delivery does not automatically reopen the underlying question.
Keep the source pack, status table, first draft, four repair reasons and C4 change note. Every commitment should trace to P, K or C. Leave missing terms for confirmation and contact scope as requested. The deeper proposal lesson adds account counts, budget and pricing to these habits.
Write a note (optional)
Use this only if you want to record a prompt or your understanding. This is a notebook, not a connected AI assistant.
Your writing is not sent anywhere. It disappears when you leave or reload this page, so copy anything you want to keep.
References
- Prompting best practices — Anthropic
- Reduce hallucinations — Anthropic