Volnyn – Website Builder, Domains, Property, Freelancers & Free Games
Open App

Call Notes to CRM Summary

Turns messy call notes into a fixed CRM summary with an owner and date on every next step.

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

What you give it

Whatever the job is about — a block of text, a URL, a name. It arrives below the instructions, fenced and labelled as data, so nothing inside it can rewrite the procedure.

Tools it uses

Restricted to these, and nothing else:

  • read_document
  • create_document

Fewer tools means fewer ways to do the job, which is what makes the result the same next week. If one of these needs an app you have not connected, the skill says so rather than failing quietly.

The procedure it follows

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

Read all the notes before writing, then fill fixed sections in order: Status (one line), Who was on the call, What they need (in their words where possible), Objections or blockers, Budget / timeline, Next steps. Write "not discussed" for any section the notes do not cover; never infer budget from company size or timeline from enthusiasm. Objections are stated reasons not to proceed; open questions become next steps for us. Every next step gets an owner and a date or "date not set". Keep it under 250 words so it fits a CRM field, and make every line traceable to the notes.

How to run it

Where How
Chat "Run my Call Notes to CRM Summary skill", or pick it from the + menu
Skills page Find Call Notes to CRM Summary under Library and press Add & Use
Automations Invoke it on every trigger
API POST /v1/skills/{id}/run — add it to your own skills first, then take the id from GET /v1/skills

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.