Call notes to CRM summary

Turns messy call notes into a structured summary with next steps.

Sales · produces a Document · built in, ready to run

What you give it

Something like this:

call w/ Ahmed @ Kanwal Foods, thurs 40 min. also Sana from finance joined late. main thing = reps take orders on whatsapp, finance re-types into excel, ~6 hrs/day wasted, errors on price lists. wants stores to order themselves. worried abt reps losing commission visibility - said that twice. sana asked abt sap integration, they r on sap b1. budget he said 'we spent 40 lakh on the erp so this shouldnt be more than half that'. wants live before ramadan. ahmed to send price list format, sana to check w/ sap partner abt api. me: send proposal + 2 refs from food distribution

What you get back

This is a real run of the skill on the input above, not a mock-up:

# Call Summary: Kanwal Foods

## Who was on the call
- Ahmed (Kanwal Foods, primary contact)
- Sana (Kanwal Foods, Finance — joined late)
- You

## What they need, in their words where possible
- **Ahmed:** "Reps take orders on WhatsApp, finance re-types into Excel, ~6 hrs/day wasted, errors on price lists. Wants stores to order themselves."
- **Sana:** Asked about SAP integration capability (they use SAP B1)

## Objections or blockers raised
- **Ahmed (stated twice):** Worried about reps losing commission visibility

## Budget / timeline
- **Budget:** Ahmed stated: "We spent 40 lakh on the ERP so this shouldn't be more than half that" (≤20 lakh)
- **Timeline:** Wants live before Ramadan

## Next steps

| Owner | Task |
|-------|------|
| Ahmed | Send price list format |
| Sana | Check with SAP partner about API availability |
| You | Send proposal + 2 references from food distribution companies |

The wording changes a little every run. The shape does not — that is what the procedure below is for.

Tools it uses

None of its own. A skill that only writes needs no tools, so this one inherits whatever your assistant can normally reach.

The procedure it follows

This is the skill, in full. Add it to your own skills to change any of it.

Turn the raw call notes below into a clean summary.

Sections, in this order:
- Who was on the call
- What they need, in their words where possible
- Objections or blockers raised
- Budget / timeline, or "not discussed"
- Next steps, each with an owner

Never fill a section by inference. Write "not discussed" where the notes do not say.

How to run it

In chat, on the Skills page and in automations you do not have to add it first — a library skill runs as it is. Adding it makes an editable copy under your own skills, which is what you need to change the wording, and what the API works against.

New to skills? Start with what a skill is.