Meeting notes and CRM updates

Once a recording finishes processing, Spiich writes one markdown summary of the meeting. It is chosen once on the server, so the web app, the desktop recorder and the note that lands in your CRM all show identical text. The summary leads with the most consequential outcome and uses whatever headings the meeting justifies, rather than forcing every call into the same template.

Then the post-meeting agent runs.

What the agent writes back

The agent has two jobs, switched on and off independently under Settings > Meeting Agent > Post-meeting agent:

• CRM updates. Creates or updates the external people and organizations, updates or creates the deal, saves exactly one meeting note on the single most relevant record, and creates at most one follow-up task, only when material internal work actually remains.
• Follow-up email. Drafts one email for you to review. It never sends anything. See Follow-up emails.

Switch both off and nothing runs after your meetings. That is a supported configuration.

Choose what happens after a meeting

1. 1

   Open Settings > Meeting Agent

   Scroll to Post-meeting agent. The section is only shown where call recording is enabled for your workspace.

2. 2

   Set the level for CRM updates

   Careful acts only on high-confidence updates the meeting states explicitly. Balanced, the default, updates the important records, note and next steps when the evidence is clear. Proactive captures every supported update and creates missing records and tasks.

3. 3

   Decide how updates land

   Under Applying updates, pick Review first so changes wait as proposals you accept, or Apply directly so they are written to the CRM as soon as the agent finishes.

4. 4

   Add your house rules

   Extra instructions under CRM updates takes free text, for example "Always set the next step date on the deal." It saves when you click away.

5. 5

   Set the follow-up email separately

   Switch Follow-up email on or off and give it its own level and its own extra instructions.

6. 6

   Watch for the inline Saved indicator

   Each card saves on its own. If it reads Not saved, the change did not stick; make it again.

Review first, and the gotcha behind it

With Review first, proposed changes gather on the meeting under a Proposals tab with a count. Accept all applies them; the dismiss control on a single proposal drops just that one. Accept all is disabled while the agent is still writing, so accepting cannot cut off the email draft mid-sentence, but individual dismiss buttons stay usable throughout.

Process a meeting you only took notes on

You do not need a recording. Write into the meeting's notes, then click Process Meeting. The agent reads your notes, resolves and updates CRM records, and then drafts a follow-up email for the meeting. A progress modal steps through "Reading your notes", "Identifying action items", "Processing insights" and "Updating records", and can be minimized so it finishes in the background.

The button stays disabled until the note has content, and the run uses credits from your workspace balance. You can see that balance under Settings > Billing.

Correcting something it got wrong

• Dismiss the proposal. On Review first, drop the individual proposal from the Proposals tab and accept the rest.
• Ask in the meeting chat. Every meeting has its own chat beside the notes. Tell it what is wrong and ask it to redo that piece of CRM work, or to revise the visible email draft in place.
• Fix the record directly. Anything already written is an ordinary CRM record and note. Edit it where it lives.
• Stop it happening again. Put the rule in Extra instructions, or drop the level to Careful so the agent only acts on what the meeting stated outright.
• Fix a misattributed speaker. In the desktop recorder, open the meeting's Transcript tab and use Rename speaker. The change applies to every turn for that speaker in the recording.

Limits

• One meeting note per call, on one record. The agent does not scatter notes across several records.
• At most one follow-up task, and only when real internal work remains.
• Extra instructions are capped at 20,000 characters per job.
• A meeting runs in a single mode for every participant, decided by the most permissive setting among them.
• The post-meeting agent section only appears where call recording is enabled for the workspace.
• Runs use credits. A run that cannot be paid for fails cleanly rather than half-writing.

If something goes wrong

• The CRM was updated even though you are on `Review first`, with no proposals. Another participant had Apply directly on. The notice on the meeting names them.
• `Process Meeting` is greyed out. The note is empty, or a run is already going. Type something, or wait for the progress modal to finish.
• A run failed for lack of credits. Top up under Settings > Billing and run it again. Nothing was half-written.
• The agent did nothing at all. Check that at least one of the two jobs is switched on under Settings > Meeting Agent.