handle-an-objection

Handle An Objection

Single-objection handler. Two outputs: in-call reframe (short, verbal) + post-call follow-up email (short, written).

When to use

• "they said '{objection}' on the {deal} call - draft my reframe".
• "how do I handle '{objection}'".
• Called by check-my-sales subject=discovery-call for any OBJECTION surfaced in call.

Connections I need

I run external work through Composio. Before this skill runs I check that the categories below are linked. Missing → I name the category, ask you to connect it from the Integrations tab, stop.

• Inbox - sample your sent emails to match voice on the post-call follow-up. Optional but recommended.

I can run this skill from your playbook and call notes alone, so no connection is hard-required.

Information I need

I read your sales context first. For every required field that's missing I ask ONE plain-language question (best modality: connected app > file drop > URL > paste) and wait.

• Your sales playbook - Required. Why I need it: the objection handbook and anchor accounts ground the reframe. If missing I ask: "I don't have your playbook yet - want me to draft it now?"
• The objection in their words - Required. Why I need it: I reframe the actual phrase, not a paraphrase. If missing I ask: "What did they say, word for word?"
• Which deal this came up on - Required. Why I need it: I save the reframe under that deal and pull context from the call. If missing I ask: "Which prospect or deal raised this?"
• Voice samples - Optional. Why I need it: makes the post-call email sound like you. If you don't have it I keep going with TBD and use a neutral tone.

1. Read the playbook. Load context/sales-context.md. Find matching entry in Objection handbook. If playbook missing, ask user to run set-up-my-sales-info first, stop.

2. Read the ledger. Load config/context-ledger.json. universal.idealCustomer field grounds reframe; progressive captures there may supersede playbook's initial objection list.