Meeting prep prompt for Customer Support Teams

This is the meeting prep prompt adapted for customer support teams. It exists because spending too much time on admin, and the prompt below is the shape that actually survives contact with how customer support teams work day to day.

What this prompt is for

Purpose: feed Strawberry the prompt that produces a usable meeting prep doc in under 60 seconds. For customer support teams specifically, the value is that it turns a recurring admin task into a 5-minute repeatable artifact. This isn't a generic template - the items below are tuned for customer support teams and the tools they actually live in.

The meeting prep prompt (prompt)

• The meeting context (calendar invite, attendees, agenda)
• The goal of the meeting in one sentence
• The three signals you need (recent news, role change, prior contact)
• The format you want back (one-page markdown, slack-ready bullets, CRM note)
• The guardrails (no fluff, no fictional details, source-cited)

Adjustments for customer support teams

customer support teams typically live in . That changes how this prompt runs:

• Pull the inputs from the apps customer support teams actually use, not generic SaaS exports.
• Anchor on recent activity in the prospect or company - it's the highest-signal field for this role.
• Skip items that don't apply to your weekly cadence; this is a starting shape, not a contract.

The most common way to mess this up

Leaving the goal vague - a meeting prep prompt without a goal produces generic context, not decision-ready prep. For customer support teams, this shows up as spending the saved time on more admin instead of higher-leverage work. Build the prompt into your week, not as a one-off.

How Strawberry runs this prompt

Strawberry runs the prompt against your live calendar, email, and CRM - so the output is grounded in your actual history with the contact. For customer support teams, Strawberry uses your live tabs and connected apps - so the prompt is filled with your real context, not a placeholder.

When to use this, when to skip

Use this prompt when the work recurs (weekly, per-prospect, per-meeting). Skip it when the situation is novel and judgment-heavy - the prompt is a baseline, not a substitute for thinking.

Caveats

Strawberry holds back on sending email, updating CRM records, or changing shared systems until a human approves the action. Treat the agent as a fast first-draft author, not an autopilot.