Meetings

Quick mental model: Meetings turn conversations into searchable knowledge — transcripts, summaries, and follow-up work you can reuse in Chat and Recipes.

What Meetings Do

Springbase Meeting Intelligence captures spoken work and makes it usable after the call ends:

• Full transcript with speaker segments
• Editable summary with decisions and action items
• Search and Q&A via Chat with the meeting attached
• Save to Context for long-term knowledge bases
• Automations that run Recipes when a meeting completes

Three Ways To Add a Meeting

Open Meetings → + New Meeting. Choose a tab:

Join with a link

Paste a Zoom, Google Meet, or Microsoft Teams URL. Springbase sends a bot to join and record. Best for scheduled calls you cannot record locally.

Record in browser

Use the built-in recorder for ad-hoc conversations (web). Long sessions upload in chunks; wait for processing to finish.

Upload or paste

• Upload audio (up to about 1 GB per file)
• Paste an existing transcript if you already have text

Processing Pipeline

After capture, Springbase:

1. Transcribes audio (async processing — status updates on the meeting page)
2. Summarizes key points, decisions, and action items
3. Indexes content for retrieval when you chat with the meeting

Status badges progress through stages like joining → processing → done (or failed). If processing fails, use Retry on the meeting detail page.

Summaries may take up to ~90 seconds after transcription completes. Refresh if the Summary tab is still empty.

Meeting Detail Page

Open any meeting to see:

Example Chat questions (after Chat with Meeting)

• "What pricing objections came up?"
• "List action items assigned to me."
• "Draft a follow-up email to the prospect mentioned near the end."
• "What did we decide about the Q2 launch date?"

Save to Context

Turn recurring meeting types into institutional memory:

1. Open the meeting → Save to Context.
2. Pick an existing Context (e.g. Sales Calls, Product Interviews) or create one.
3. Future Chat and Recipes attached to that Context can use meeting content.

Best practice: one Context per meeting type, not one Context per single call — unless the call is uniquely important.

Calendar and Auto-Join

Connect your calendar (where available) so Springbase can offer join bots for upcoming meetings. Check Meetings settings and calendar connection prompts in the product for your account tier.

Meeting Automations

On Automations, create post-meeting rules:

• When a meeting completes → run a Recipe (e.g. follow-up email draft)
• Map meeting fields (summary, action items, attendees) to Recipe variables
• Optional delay (e.g. run 1 hour after the call)

Requires Pro/Max for scheduling features; enterprise may gate automations policy.

Example: Sales discovery call ends → automatically run Sales Follow-Up Recipe with summary pre-filled.

Sharing Meetings

Share on a meeting supports:

Meetings do not use public community discovery. Enterprise admins may restrict broader sharing via org policies.

Limits

End-to-End Example: Sales Call

1. Join Zoom link from + New Meeting.
2. After the call, review Summary and edit action items.
3. Chat with Meeting: "Draft follow-up confirming next steps."
4. Save to Context → Sales Calls.
5. Automation runs Follow-Up Recipe on every completed sales meeting.

Troubleshooting

Related Guides

• Sales Follow-Up — meeting → email workflow
• Contexts — archive meeting knowledge
• Recipes — automate follow-up templates
• Security and Sharing — enterprise visibility