Objection Handling: Diagnose → Respond → Follow Up

What this chain helps you accomplish

Turn a real buyer objection into a grounded, respectful response plan: diagnose what was actually said, prepare evidence-backed ways to respond, choose the correct path to the objection owner, and draft a useful follow-up only when continued contact is appropriate.

The four linked prompts produce an objection evidence packet, three distinct response options, a direct-or-intermediary routing plan, and a human-reviewable follow-up with a source audit and send checklist.

The chain prevents AI from inventing buyer motives, competitor weaknesses, discounts, approvals, or successful objection resolution. It helps SDRs and AEs maintain trust, decide when to clarify or involve a specialist, and recognize when to stop rather than push. Promptifi supplies the instructions; the seller runs them in their own approved AI application.

When to use it

• After a prospect or active opportunity raises a concrete price, budget, value, competitor, status-quo, timing, authority, implementation, security, legal or procurement concern.
• Immediately after a discovery, demo, evaluation or commercial discussion when a seller must decide whether to clarify, answer, escalate or pause before sending any follow-up.
• When an objection is relayed by an internal contact and the seller needs to distinguish what the buyer truly said from an intermediary's summary.
• When the seller has direct access to the person raising the concern and needs a grounded two-way response without unnecessary 'Champion coaching'.
• Before preparing a concise post-objection message that refers to the real concern and proposes one realistic next action.

Do not use it to override a clear rejection, opt-out, explicit 'not interested', customer data restrictions, product mismatch or legitimate legal/security requirement. Do not treat routine procurement review as a hidden blocker. When the only source is a rough seller paraphrase, the appropriate first output may be a clarifying question rather than a persuasive rebuttal.

This is a manually run prompt chain, not an automated recovery sequence, an email-sending tool, or a substitute for an employer's commercial or compliance approval.

Before you begin

Minimum tool and permissions

Required: an employer-approved text-capable AI assistant such as ChatGPT, Claude, Gemini or Microsoft Copilot, plus the permitted account notes or message describing the objection. No paid tier, CRM connector, email account, live web search or marketing automation is required. Optional browsing or CRM lookup may enrich context ONLY when actually available and allowed. A pasted website or recording link does not mean the model accessed it.

Use your company's rules for handling meeting transcripts, private emails, customer data, pricing, security documentation and personal information. Redact restricted information rather than sharing it with an unapproved model. Confirm outreach permissions and whether the prospect has requested no further contact before drafting a message for potential use.

Exact placeholders and realistic preparation examples

• {{ACCOUNT_AND_OPPORTUNITY}} — Required. Exact customer and opportunity if known; source: CRM or call notes; e.g., 'Northstar Facilities / compliance reporting evaluation' (fictional). If unknown, do not invent the company.
• {{SELLER_ROLE_AND_DEAL_STAGE}} — Required. SDR or AE, and actual seller-reported stage; e.g., 'AE, technical evaluation'. If stage is unknown, label it UNKNOWN rather than assuming 'closing'.
• {{SOLUTION_AND_APPROVED_CAPABILITIES}} — Required. Accurate short product description and approved features/use cases from current seller collateral; e.g., 'reporting dashboard with scheduled exports'. If missing, response options must rely on clarification, not product claims.
• {{EXACT_OBJECTION_AND_SOURCE}} — Required. Verbatim buyer message, cited transcript line or a clearly labeled seller paraphrase; e.g., 'We already have a dashboard; changing would take time,' quoted from buyer email. If unavailable, STOP Prompt 1 and obtain actual wording.
• {{OBJECTION_SPEAKER_AND_CHANNEL}} — Required if known. Actual person/role, whether direct or relayed, and email/call/chat source; e.g., 'Operations Manager via email' or 'relayed by analyst; decision-maker unknown'. If missing, UNKNOWN.
• {{CONVERSATION_DATE_AND_TIMEZONE}} — Optional. Actual date/time zone from call or email, e.g., '2026-11-05 America/Chicago'. If absent, leave relative deadlines unresolved.
• {{CONVERSATION_CONTEXT_AND_QUESTIONS}} — Required where available. What was shown/proposed, questions already asked, seller's real reply and buyer's answer with dated source. If none, state 'no follow-up yet / not verified'.
• {{BUYER_PRIORITIES_AND_EVIDENCE}} — Optional. Buyer-confirmed outcomes, concerns, decision criteria and sources; e.g., 'wants consistent monthly audit exports, call note L12'. If missing, treat possible priorities as hypotheses.
• {{APPROVED_PROOF_AND_RELEVANT_ASSETS}} — Optional. Approved case studies, help docs, security summaries or product proof with allowed claims and verified links. If none, no invented ROI, testimonials or attachments.
• {{CURRENT_OFFER_AND_COMMERCIAL_LIMITS}} — Required for price/term scenarios. Actual approved offer, currency, discount authority, restrictions; e.g., 'USD quote supplied, no concession authority'. If unavailable, no numerical discounts or alternative commercial promises.
• {{COMPETITOR_OR_STATUS_QUO_FACTS}} — Optional. Facts the buyer actually stated about incumbent or process, source/date; e.g., 'buyer says current dashboard used weekly'. Unknown competitor capabilities must remain UNKNOWN.
• {{STAKEHOLDER_ACCESS_AND_ADVOCACY}} — Required to choose Step 3 path; list documented access and actual internal advocacy actions; e.g., 'contact introduced IT lead by email' versus 'friendly but no introduction'. If absent, route C: access/authority unknown.
• {{LEGAL_SECURITY_PROCUREMENT_RULES}} — Optional unless relevant to objection. Actual review process and seller policies from approved documentation; e.g., 'security questionnaire owned by compliance team'. If unknown, do not promise review completion or waive it.
• {{BUYER_COMMITMENTS_AND_NEXT_STEPS}} — Optional. Customer-agreed owner, action, date and exact source; e.g., 'buyer agreed to review a summary next Thursday (email)'. If no commitment, 'none verified'.
• {{CONTACT_ELIGIBILITY_AND_REPLY_HISTORY}} — Required before any real send. Reply permissions, stop-contact status, prior messages and verified channel history from company system; 'not checked' means HOLD, not assumed clearance.
• {{SELLER_OBJECTIVE_AND_PREFERRED_NEXT_ACTION}} — Required. Appropriate seller outcome such as 'clarify whether reporting migration scope is the blocker'; if no right to continue, specify pause or close.
• {{SENDER_IDENTITY_AND_APPROVED_LINKS}} — Required before any real email. Correct sender details and approved booking/asset links; if absent, draft a safe response without links and mark verification needed.
• {{AI_DATA_AND_OUTREACH_POLICY}} — Required. Employer-approved AI tool, allowed shared information, channel restrictions, retention rules, sender approvals. If unclear, sanitize input and stop any sensitive upload.

Prepare a simple evidence packet

1. Copy the exact objection and identify whether it came directly from the buyer, from someone relaying a concern, or from a seller's memory. Preserve quote and date when available.
2. List the actual prior buyer questions and seller responses. Do not treat an intended response from an earlier call as something already said.
3. Check approved solution proof, proposal constraints and internal subject-matter experts relevant to price, technical, security and legal topics.
4. Find the real message history and customer contact preferences before considering a follow-up; do not assume the prospect wants more outreach.
5. Keep unknowns explicit. One well-chosen question can be more useful than an invented persuasive argument.

Research basis: HubSpot's objection-handling guide (updated August 14, 2026, blog.hubspot.com/sales/handling-common-sales-objections) emphasizes listening, acknowledging, clarifying and tailoring responses; Harvard Law School's Program on Negotiation (pon.harvard.edu/daily/negotiation-skills-daily/ask-the-negotiation-coach-nb/) emphasizes careful questions and active listening. Both inform the practical prompts; they do not guarantee an objection will be resolved.

How to run the chain

1. Open a fresh conversation in an employer-approved AI assistant. Copy and fill out the STARTING CONTEXT in the protected Chain Steps below. Paste only the customer data your organization allows. Mark unknown or unverified fields rather than inventing answers.
2. Run Prompt 1. Check that the buyer's exact words and the speaker's identity are accurate, and that the model separated fact, relay, hypothesis and unknown. Correct errors before approving OBJECTION_DIAGNOSTIC_v1.
3. Run Prompt 2 using the complete approved diagnostic. Evaluate the three approaches, source references and stop conditions; select an option based on the actual buyer context, not the model's confidence in a guessed motive. Approve RESPONSE_STRATEGY_v1.
4. Run Prompt 3 even if there is no Champion. The same prompt selects a relayed-advocate path, direct-buyer path, unknown-access path or no-contact path. A shared internal brief is only a draft until the seller and its intended reviewer approve accuracy and distribution. Approve STAKEHOLDER_RESPONSE_ROUTE_v1 or hold.
5. Run Prompt 4 with all three approved artifacts plus the verified record of anything actually spoken or sent. Review the message against the buyer's concern, evidence and contact eligibility. If a refusal, opt-out or unresolved policy hold exists, use its NO SEND result rather than forcing a follow-up.
6. Before any actual customer message, verify contact status, timing, permissions, correct recipient, legal/commercial statements, signature and working links. Send only manually through your authorized channel after review; this chain does not send emails or write to CRM.
7. If output is wrong, provide the exact evidence to correct and request a COMPLETE v2 of the affected artifact. Re-approve the revision; if the objection diagnosis changes, rerun all downstream prompts that depended on the old interpretation.
8. If moving to a different conversation, paste the permitted Starting Context plus full latest approved artifacts and actual contact history; do not assume the assistant retains previous chat context.

Version and approval rule

Use exact approval lines: 'APPROVED — OBJECTION_DIAGNOSTIC — v1', 'APPROVED — RESPONSE_STRATEGY — v1', and 'APPROVED — STAKEHOLDER_RESPONSE_ROUTE — v1'. For corrections, issue the next version and explicitly approve it; a new version supersedes an old one only after review. Seller approval is not a buyer's agreement or permission to contact. Never claim the objection was resolved without the buyer's real confirmation.

Recognize completion

You have a source-checked diagnosis, three safe response alternatives with one selected for seller review, a validated communication route or no-contact decision, and an optional human-reviewable follow-up pack. The final work remains DRAFT ONLY until appropriate human action occurs.