Guide

Granola Recipes for customer feedback, and when a recipe is enough.

A recipe is a saved prompt you run on your Granola notes. For customer feedback you want three: one after each customer call, one across a folder of calls, and one before you meet a customer again. Copy them below. They work well for a few calls a week. Once you need the same themes counted by company over months, a recipe starts to strain.

Updated . Checked against Granola's help centre that day.

A saved recipe

/call-problems

Every problem from this call, word for word, with the company and whether they raised it themselves.

What is a Granola recipe?

A reusable prompt. You save it once, give it a name, and run it on your notes by typing / and the name in Granola's chat. Recipes are on every Granola plan.

Each recipe is one of two kinds, and you choose which when you create it:

  • Single meeting: runs inside one meeting's chat, during or after the call.
  • Multiple meetings: runs on the home screen, in a folder, in a person or company view, or on meetings you select.

A recipe cannot be both. That is why the setup below uses three separate recipes.

How do you set one up for customer calls?

  1. Make a folder for customer calls and move each customer conversation into it. Keep internal meetings out.
  2. In the chat bar, type / and choose "Create a recipe".
  3. Give it a short name. The name is what you type to run it, so "call-problems" beats "Customer call problem extraction v2".
  4. Paste one of the prompts below and choose single or multiple meetings to match.
  5. Run it on a call you remember well, and check the answer against what you know was said. Adjust the prompt once, then leave it alone.

Recipes have no variables, so a prompt cannot take a date or a company name as input. Where the prompts below need one, run them from the right place instead: the folder, or the company's view.

Recipe 1: after each customer call

Single meeting. Run it when the call ends.

From this customer call, list every problem, workaround or request the customer raised.
For each one give:
- their exact words, quoted from the transcript
- who said it and their company
- whether they raised it themselves or answered our question
- what they do today instead, if they said
Leave out anything our side said. If there was nothing, say so.

"Whether they raised it themselves" is the line that matters most later. A problem a customer brings up on their own is stronger evidence than one they agreed to when asked. Prompted and unprompted feedback explains why.

Recipe 2: across a folder of calls

Multiple meetings. Run it from the customer calls folder, before a planning meeting.

Go through every meeting here and list the problems customers raised, grouped by the problem underneath (not by the feature they asked for).
For each problem give:
- the number of different companies that raised it (a company counts once, however many calls it came up in)
- how many of those companies raised it before we asked about it
- one word-for-word quote with the company and the meeting
Sort by the number of companies. List the meetings you used.

Telling it how to count matters. Left alone, an answer tends to count mentions or meetings, so one customer who raised something on four calls looks like four separate requests.

Recipe 3: before you meet a customer again

Multiple meetings. Run it from that company's view in Granola, a few minutes before the call.

What has this customer told us in earlier meetings?
List the problems and requests they raised, with the date and their exact words, and anything we promised to get back to them about.

The last line is the one people thank you for: it reminds you of what you said you would come back on. The guide Closing the customer feedback loop has messages for when you do.

How do you share them with the team?

Publish a recipe to your workspace, or share it by link. Colleagues can run it on their own notes and save their own copy, but they cannot edit yours or see your notes.

Sharing is worth doing for the first two recipes. When sales, success and product all run the same prompt, their answers can be put side by side.

When is a recipe enough?

  • You have a few customer calls a week, and one or two people run the recipes.
  • The question is about now: this week's calls, this quarter's folder, this customer.
  • You check the quotes before anything leaves the chat.

Many teams never need more than that. If that is you, the three recipes above and the guide Find patterns across your Granola customer calls are all you need.

Where do recipes stop?

A recipe writes a fresh answer every time it runs. It does not remember last month's answer, so the same problem can come back under a different name, and you cannot see that a theme has grown from three companies to nine.

Its counts cover what it read in that run. Across a large folder, check the list of meetings it used before trusting a number.

And on Granola's free plan, meeting history goes back 30 days, so a folder only ever holds the last month.

What if you need the count over months?

Then you need something that keeps the themes between runs, counts each company once, and remembers who to tell when a fix ships.

Ordagrann reads the customer calls you record in Granola, groups every problem and request into themes, counts how many companies raised each one, and turns a theme into a one-page brief your team can build from. It connects with a Granola API key, so it needs Granola Business, and it reads only the calls you approve.

Get started

Works with Granola Business. Any other transcript can be pasted in.