← All plays
GT
Alta GTMS team
Creator

Objection Map

Know the objections you hear most, and how to answer them

Raised by customers on 90+ calls in the past year

Sorts negative replies and call objections into the reasons that keep coming back, shows how often each appears, and suggests a response for each.

Learn
Luna
Reviewed by Alta

What it does

  1. Reads negative replies and objections from recorded calls
  2. Groups them into recurring reasons
  3. Ranks them by how often they appear and how often the deal died after
  4. Suggests a response for each, taken from replies that worked

You give it

  • The period to look at
  • Access to replies and call recordings

You get

  • Your top objections, ranked
  • A proven response for each

Why it works

Objections feel random one at a time and obvious in aggregate. Seeing them ranked turns reps' instincts into a shared playbook.

Run this play

Copy the SKILL.md below into your agent
Works in Alta, Claude, Cursor and Codex
Runs on
Luna
Category
Learn
CostAlta credits per run, shown before it runs
ApprovalEvery run stops at a draft for you
--- name: objection-map description: Group negative replies and call objections into recurring reasons, ranked by frequency, with a suggested response for each. Use when someone asks why prospects say no, about objections, negative replies or objection handling. agent: Luna category: Learn ends_in: report --- # Objection Map The same five objections usually cost most of the deals. Name them, then answer them. ## How it runs 1. **Read negative replies** and objections from recorded calls 2. **Group them** into recurring reasons - timing, budget, incumbent, priority, fit 3. **Rank by frequency** and by how often the deal died after 4. **Suggest a response** for each, from replies that turned a no into a meeting 5. **Write the report** ## Rules - Quote real lines, anonymized - Suggested responses come from what worked, not from theory ## What you get - Your top objections, ranked - A proven response for each
- Five to eight reasons cover most of the objections - Each reason has real, anonymized examples - Every suggested response comes from a case where it worked
The play fileSKILL.md

This is the whole play. Read it, copy it, or change it for your team - it runs the same in Alta, Claude, Cursor and Codex.

Install this play
Claude app or claude.aiUpload the zip as a skill

Download the zip, then upload it as a skill in your Claude settings. Code execution needs to be on.

Claude CodeDrop the folder in

Unzip it into your skills folder. Claude Code finds it on its own.

~/.claude/skills/
Cursor and other agentsAdd the SKILL.md

Put the folder where your agent reads skills, for example:

.cursor/skills/

Run it where you work

Same play, same result. Pick the place you already are.

In Alta

One click

Open Skills in Alta, pick the play and press Run. Or ask Ask Alta to run it for the companies you care about.

In Claude

Ask in plain words

Connect Alta to Claude and describe the target. Claude loads the play, the agent does the work, and the draft opens in Alta for you to approve.

In Cursor or Codex

Drop in the file

Add the SKILL.md to your agent's skills folder with the Alta plugin connected. Edit it like code, and keep your team's version in the repo.