The value of a meeting is usually decided afterward: whether people can find what was agreed, know who owns the next step, and send the promised follow-up while the context is still fresh.

Strawberry can transcribe Google Meet, Zoom, Teams, and in-person conversations from the transcription button in chat. No meeting bot joins. The transcript can become notes, decisions, actions, and drafts in the structure your work actually needs.

Prepare when context matters

For an important meeting, combine the calendar event with relevant approved relationship history, recent communication, company context, and the desired outcome. Keep the brief concise enough to scan immediately before the call.

Preparation is optional. The post-meeting workflow should still work when the conversation begins without a perfect brief.

Prepare me for every call today

Use this when the meeting benefits from a concise brief beforehand.

I want to be fully prepared for every call today.

Capture the conversation reliably

Transcribe in the meeting's language and preserve uncertainty where speech is unclear. Agree where transcripts and notes should live, how much detail is useful, and whether privacy or retention constraints apply.

Adapt the record to the meeting. An interview may become a scorecard, a client call may belong in the client folder, and a sales or investment call may need specific CRM or company fields.

Never forget a meeting or follow-up

Use this to turn a meeting into reliable notes, decisions, and follow-up.

I want meetings transcribed with decisions and follow-ups captured automatically.

Turn talk into owned work

Pull out decisions, open questions, action items, owners, dates, and promised follow-ups only where they are useful. Draft communication from what was actually said and keep external messages or record changes reviewable until approved.

A good result is not a transcript dump. It is a linked source plus concise notes and the next actions in the user's accepted destination.

Turn this sales meeting into clear next steps

Use this when a sales conversation needs a focused debrief, follow-up, CRM changes, and next actions.

Debrief this sales meeting using the transcript or notes. Tell me what changed, prepare the right follow-up and next actions, and show any proposed CRM updates separately before changing anything.

Make the accepted format repeatable

Review the first real output and preserve the accepted note structure, destinations, privacy boundaries, approval behavior, and follow-up rules as a custom skill.

Add a Routine only after the workflow is trusted. The recurring version should preserve user review for sensitive communication and consequential external updates.

Keep my CRM up to date

Use this when approved meeting context belongs in the CRM.

Help me keep my CRM current from recent emails, meetings, and sales activity. Use the CRM and context already available, then show me a small set of proposed updates with their sources so I can correct the mapping before anything changes.

Official Strawberry skill

name: transcribe-meetings-follow-up
description: Turn meetings, calls, or interviews into transcripts, useful notes, decisions, and follow-up actions. Use when a user wants reliable recall or wants post-call work updated in their existing tools.

Transcribe Meetings and Follow Up

Use this Official Skill as starting guidance for turning a meeting into reliable notes and useful follow-up. If the user already has a tailored post-meeting skill, follow that instead.

Context, setup, and planning

Try to understand:

which meetings matter and where the transcript, notes, and follow-up should live;
the user's preferred note depth and structure, including any rubric or scorecard that applies;
which details should become decisions, action items, owners, sentiment, or structured records;
any privacy or retention constraints; and
which external updates or messages require review.

Prior notes, calendar context, conversation history, CRM or ATS records, and client or company materials can help when they are available, relevant, and approved; they are not prerequisites. Offer to learn through a few questions, inspect that context, or combine both. If the meeting also needs preparation, use strawberry/sales/prepare-for-calls.

Explain that Strawberry can transcribe Google Meet, Zoom, Teams, and in-person conversations from the transcription button in chat. No meeting bot joins, and both sides of the conversation are captured.

Execution

Transcribe in the meeting's language and preserve uncertainty where speech is unclear.
Produce notes in the agreed structure. Capture decisions, open questions, action items, owners, dates, promised follow-ups, and sentiment only where they are useful.
Adapt the record to the meeting rather than forcing one generic template. For example, an interview can become a scorecard mapped to the hiring rubric; a client call can be filed in the correct client folder; and a sales, investment, or recruiting call can update the relevant CRM, ATS, people, company, or theme records.
Turn action items into owned tasks when that is part of the approved workflow.
Draft follow-up from what was actually said. If the user's voice is not already clear, use strawberry/general/learn-writing-style before trying to imitate it.
Ask before writing to external systems or sending messages. Nothing sends without the user's approval.

Suggested outcome

Create a readable transcript or linked source plus concise, useful notes in the user's chosen structure. Depending on the meeting, this may include decisions, a scorecard, sentiment, structured records, owned actions, and a follow-up draft grounded in the conversation.

Suggested next steps

For a sales, prospect, customer, or partner conversation that needs sales-specific interpretation and follow-through, use strawberry/sales/debrief-a-sales-meeting once a reliable record exists.
When approved meeting context or next steps belong in the CRM, use strawberry/sales/keep-crm-updated.
After the workflow proves useful, preserve the accepted destinations, note structure, approval behavior, and follow-up rules as a user-owned post-meeting skill. If it should run around every meeting, offer to turn the proven workflow into a routine.