Customise your meeting Overview

The Overview is the summary you get after each call. Out of the box it covers what was said. Customised, it answers the questions you actually ask after every call of that type, which is a very different thing.

Before you start

You do not rewrite the Overview by hand. You tell Claap which AI Fields should feed it, and those fields are then reflected in the summary.

An AI Field is a question asked of every call, the customer's needs, who holds authority, what the decision process looks like. Attach those fields to your Overview and each summary comes back structured around them, rather than around whatever the call happened to cover.

The practical effect: instead of reading a neutral recap and hunting for the decision process, you get an Overview that leads with it, every time.

💡 New to AI Fields? Create your first one before configuring anything below. Using AI Fields covers Meetings › Add Column › Add New AI field, the ten answer formats available, and how to test a prompt before rolling it out. Testing is free.

This is the part that decides whether your Overview becomes useful or unreadable.

Start from what you write down anyway. If you always note the next step, the budget and who else is involved, those are your three fields.

Three or four is usually right. An Overview personalised with a dozen fields stops being a summary and becomes a form, which defeats the point.

Prefer questions with a stable answer shape. Was a next step agreed produces something comparable across two hundred calls. How did the call go does not.

Watch the volume, not the count. Each field costs one credit per meeting, so your consumption is fields multiplied by call volume. Four fields on twenty calls a week is eighty credits a week.

Internal and external meetings are configured separately. That separation matters: the questions worth asking on a customer call are rarely the ones worth asking on a team sync.

⚠️ Configure both sections. Setting only the external one leaves every internal call with a default Overview, the most common reason people think this feature isn't working.

While you are in Automation preferences, this is also where you choose which meetings are auto-recorded, whether to record only the ones you host, and who receives the recap email. Full detail: Meeting automation preferences.

Same idea, one level up, and this is what you want if the Overview feeds a report or a CRM field.

Admin automations also have an Enforce automation option, which stops members overriding the rule with their personal preferences. Use it when consistency matters more than individual choice.

💡 If someone belongs to several teams, the order of the teams decides which settings win. Drag and drop to set the priority. Workspace default at the bottom is the fallback.

Run it on an actual meeting rather than a clean test. If a field comes back empty or vague, the question is usually too broad rather than the call being unusual.

To apply your fields to calls you have already recorded: select the recordings, then Bulk edit › Complete X recordings. You can also click the wand in a column header to fill a single field across the view.

Adjust the field, not the Overview. The Overview reflects the fields, so that is where every change belongs. See Editing an AI Field.

Work through these in order.

💡 Still got questions? Contact our Support Team at support@claap.io.