Skip to main content

Use Case: Turn Your Sales Call Debrief Into a Reusable Skill

Write your call debrief process once as a skill, then paste your notes to get the same four-part debrief each time.

C
Written by Carlos Molero

You probably do the same thing after every sales call: write a quick summary, list the objections, decide the next step and send a follow-up. A skill lets you write that process down once. After that, you paste your notes and JeremyAI follows the same steps and format each time, without you re-explaining what you want.

Watch the walkthrough

Can't see the video? Watch it here (3:03).

In the video, we create a call debrief skill on the My Skills tab, then paste demo call notes into a new chat and get the debrief back.

Why it matters

  • Fewer skipped steps. A checklist in your head gets shortened when you're busy. A skill lays out every step each time.

  • Same format every time. Every debrief uses the same headings, so you can scan them quickly and compare deals.

  • Shorter prompts. You stop pasting the same long instructions into every chat. Paste the notes, and the skill supplies the rest.

  • It's yours. Your skills are private to you and work in all your chats.

What you'll need

  • Notes or a transcript from a sales call. Typed bullet points are enough.

  • About five minutes.

Step 1: Create the skill

  1. In the sidebar, open More (it also holds Memories) and click Skills.

  2. The page opens on Inherited. Click the My Skills tab, then + Add skill.

  3. Fill in the New skill window with the text below, then click Create skill.

Name: my-call-debrief

Description: Use when I paste notes or a transcript from a sales call and ask for a debrief, a follow-up email or next steps.

Sample query (optional): Debrief this sales call: [paste notes]

Body (markdown):

# Sales call debrief
​Use this after a sales call when I paste my notes or a transcript.
​
​## Steps
​1. Read the notes. If the prospect's name, the offer we discussed or the outcome of the call is missing, ask me before going on.
​2. Write a 3-line summary: who they are, what they want, where the deal stands.
​3. List every objection they raised, in their words where possible, with one suggested answer for each.
​4. Name the single next step. Include a date only if my notes give one.
​5. Draft a follow-up email under 120 words that recaps what they want and confirms the next step.
​
​## Output format
​Use these headings in this order: Summary, Objections, Next step, Follow-up email.
​
​## Rules
​- Don't invent anything that isn't in my notes. Write "Not discussed" when something is missing.
​- Keep the email plain and friendly. No hype.

The Create skill button stays greyed out until Name, Description and Body are filled in. Once you click it, you'll see Skill added to your library, and the skill appears in your list with a My library badge and Applies to: All your chats.

Prefer to build it in a chat? Work out the steps with JeremyAI, then say Save this as a skill and click Save to My Skills on the card that appears.

Step 2: Run it on a call

Start a new chat and paste your notes. Here are the demo notes from the video:

Debrief this sales call:
​
​Call with Sam Ortiz, owner of a local roofing company (demo notes).
​Interested in the Booked Jobs Accelerator.
​Worried about time: "I can't add another 5 hours a week."
​Didn't sign on the call. Wants to talk to his business partner first.

JeremyAI shows a Preparing context step, picks the skill from its description, and replies with the four sections: Summary, Objections, Next step and Follow-up email. You'll see the skill load in the reply's Actions. To be sure it uses your skill, start the message with Use the my-call-debrief skill.

Step 3: Tune it

Read the first few debriefs closely. When something isn't right, change the skill, not the prompt, so the fix sticks:

  • On the My Skills tab, click the ⋯ menu next to the skill and choose Edit. The Edit skill window opens.

  • Change the step or rule that caused the problem, then click Save changes.

  • Try it again in a new chat.

What good output looks like

  • All four headings, in the order the skill sets.

  • Objections in the prospect's own words, each with a suggested answer.

  • One next step, not a list of maybes. If your notes didn't include a date, check any date it suggests.

  • A follow-up email you could send after a quick read.

  • "Not discussed" where your notes were missing something. If you spot a detail that wasn't in your notes, see Troubleshooting.

Other skills worth building

The same pattern works for any task you repeat. Check the Inherited tab first, since JeremyAI may already have a skill for it. A few ideas:

  • Ad review: Use when I paste an ad and ask for feedback. Steps: check the hook, the offer, the proof and the call to action, then suggest three new hooks.

  • Weekly numbers summary: Use when I paste my weekly numbers. Steps: compare them with last week, flag anything that moved more than 20%, and suggest one thing to test.

  • Objection answers: Use when I paste an objection from a prospect. Steps: name the real concern, write a short answer in my tone, and suggest a question to ask back.

  • Content repurposing: Use when I paste a transcript and ask for posts. Steps: pull the three strongest ideas and write one short post for each.

Keep each skill to one job. If you want a debrief and a proposal, build two skills.

Prompts to copy

  • Use the my-call-debrief skill on these notes: [paste notes]

  • Help me write a skill for [task]. Here is how I do it today: [your steps]. Turn it into numbered steps, an output format and rules. Keep it under 60 lines.

  • Here is a debrief you wrote: [paste]. What should I change in my skill so the objections section is more useful?

Troubleshooting

  • JeremyAI answers without using the skill: name the skill in your message, or rewrite the description so it says when to use it.

  • The output skips a step: make the step its own numbered line, and keep the skill short. Long skills are followed less closely.

  • The name is already taken: pick a different name, for example one that starts with my-. If one of your own skills already uses that name, rename or delete it first.

  • The body is over the limit: a skill can be up to 200 lines and 20 KB. Split it, and move reference material like transcripts or price lists to Knowledge.

  • Saving from a chat didn't work: a skill with that name may already exist. Ask JeremyAI to save it under a different name, then check the My Skills tab.

For every field and option, see How to Create Your Own Skill. Still stuck? Email [email protected].

Did this answer your question?