Create a custom summary recipe

A recipe controls how a call is turned into notes — which sections appear and what goes in each. Callmora ships with recipes for common meetings — 1-on-1, Sales debrief, Stand-up, Hiring interview, Tech spec / design review, and Investor update — plus Auto, which reads the meeting's title and applies the matching built-in when it recognizes the kind of call (a standup, a 1:1, an interview), falling back to Callmora's general notes when nothing matches. When none of those fit the way you work, you can write your own.

What a recipe is

A recipe is two things: a name and a section plan — a short, plain-text list of the sections you want, one per line. The section plan shapes the Key points of the notes, and only that. Everything else Callmora produces for every call stays put no matter which recipe you use:

• TL;DR and Overview
• Action items (grouped by owner, and fed to your to-dos)
• Decisions, Open questions, and Topics
• Highlights you can click to jump to that moment in the recording

So a recipe reshapes the body of the notes without breaking the parts that link to your to-dos, the audio player, and export.

When to make your own

Reach for a custom recipe when your meetings have a repeatable shape the built-ins don't cover — a client kickoff, a user-research interview, a weekly ops review, a therapy or coaching session. Two things worth knowing before you start:

• Auto never picks a custom recipe. Auto only matches the meeting title to the built-in recipes. To have your recipe used, you either make it your default or choose it on the call (both below).
• A recipe describes sections, not format. It can't add new fields, change the layout, or turn off the always-on cards above — it decides what the Key points sections are and what each should capture.

Create a custom recipe

Recipes live in Settings, and sync across your Macs with the rest of your data if iCloud sync is on.

1. Open Callmora's Settings → Summary.
2. Find the Default recipe row and click Manage… beside it. The Summary Recipes window opens, with your Custom recipes on top and the Built-in (read-only) ones below for reference.
3. Click Add recipe.
4. In the editor, type a Name, then write your section plan in the box below — one section per line. A counter shows how much of the 2,000-character limit you've used.
5. Click Save. Your recipe now appears under Custom and in every recipe picker.

To edit or delete a recipe later, reopen the same Manage… window and use the pencil or trash button on the row (or right-click it).

Two ways to use it

Writing a good recipe

The section plan is dropped straight into Callmora's notes prompt, so a few habits make a big difference:

1. One section per line, numbered like the built-ins. Callmora maps each line to one Key-points group, in the order you write them. Open a built-in in the Manage… window to see the shape.
2. Give each line a short heading and a "— what goes in it" note. The heading becomes the section title in the notes; the note tells Callmora what to pull from the call. For example: Risks & open questions — concerns raised and anything still to confirm.
3. Write the plan in plain English even if your calls aren't. Headings are rendered in the summary's own language automatically, so you don't need to translate them.
4. Describe sections only — don't fight the format. Don't ask for JSON, extra fields, or a different layout; the TL;DR, action items, decisions, highlights, and topics are always produced, and Callmora ignores anything in the plan that tries to change that.
5. Keep it to 3–6 focused sections. Fewer, well-described sections read better than a long list, and the editor caps the plan at 2,000 characters. If a section has nothing to capture on a given call, it may be merged or dropped — that's expected.

Example: a "Client kickoff debrief" recipe

Here's a complete recipe you can copy into a new recipe. Name it Client kickoff debrief and paste the section plan below.

1. Client & project — who the client is, the project, and the goal in their own words.
2. Scope & deliverables — what we agreed to deliver, and what's explicitly out of scope.
3. Stakeholders & roles — who does what on each side, and the main point of contact.
4. Timeline & milestones — key dates, deadlines, and dependencies discussed.
5. Risks & open questions — concerns raised, unknowns, and anything still to confirm.
6. Next steps — what each side committed to before the next touchpoint.

Note a call with this recipe and the Key points come out in six sections — Client & project, Scope & deliverables, Stakeholders & roles, Timeline & milestones, Risks & open questions, and Next steps — on top of the usual TL;DR, action items, decisions, highlights, and topics.

Troubleshooting & FAQ

← Back to all docs