---
ref: workflow:sales-call-follow-up
title: Send an approved follow-up and book the next call
author: Shahzaib0217
tools: [tool:bridge/search-meetings, tool:bridge/get-meeting-details, tool:bridge/get-follow-up-plan, tool:bridge/create-follow-up-plan, tool:bridge/act-on-follow-up-step, tool:bridge/find-free-time, tool:bridge/create-meeting]
tags: [capability:automate-workflows, capability:book-meetings, capability:host-meetings, capability:review-recordings, capability:send-email, channel:email, has:mcp, motion:outbound]
updated: 2026-10-28
---

# Send an approved follow-up and book the next call

Builds a Bridge follow-up plan for a sales call, drafts the recap email for your approval, sends it, and schedules the next meeting.

Set up the tools below, then run the steps in order for the user, carrying each step's results into the next. The run is done when the user has the outcome below.

## Outcome

- A follow-up email you approved, sent from your connected mailbox, recapping the call, commitments and resources.
- The next meeting scheduled in Bridge, with the buyer invited.
- The rest of the follow-up plan, with each step done, skipped or left for you.

## Inputs

Ask the user for these before you start.

- `meeting`: the finished call, by title, account or day, e.g. Acme discovery call yesterday
- `resources`: links to share, e.g. https://example.com/case-study
- `next_meeting`: the next step to book, with its length and window, e.g. a 45-minute technical deep dive next week

## Set up

### Bridge (tool:bridge/search-meetings, tool:bridge/get-meeting-details, tool:bridge/get-follow-up-plan, tool:bridge/create-follow-up-plan, tool:bridge/act-on-follow-up-step, tool:bridge/find-free-time, tool:bridge/create-meeting)

Use the MCP server. Add it to your agent's MCP settings, then sign in when asked.

```json
{ "mcpServers": { "bridge": { "url": "https://api.meetonbridge.com/mcp" } } }
```

- Search meetings: call the MCP tool `search_meetings`
- Get meeting details: call the MCP tool `get_meeting_details`
- Get a follow-up plan: call the MCP tool `get_follow_up_plan`
- Create a follow-up plan: call the MCP tool `create_follow_up_plan`
- Act on a follow-up step: call the MCP tool `act_on_follow_up_step`
- Find free time: call the MCP tool `find_free_time`
- Create a meeting: call the MCP tool `create_meeting`

Note: Needs a paid Bridge plan (Professional or above); not on the free Starter plan or a trial. At sign-in the user grants read, or read and write, access. Call get_bridge_context first for the tools the plan and connection allow.

Notes:

- Search meetings: Omit `query` to browse by date or participant. Pass a returned `recapId` to `get_meeting_details` for the full meeting.
- Create a follow-up plan: Nothing is sent when the plan is created. Check `get_follow_up_plan` first so a meeting does not get two plans; takes up to 30 seconds.
- Act on a follow-up step: `draft` previews Gmail, Google Calendar, Google Docs and HubSpot steps, but Slack, Notion, Linear, ClickUp and Attio actions not named as writes run during `draft`. `approve` with `revision` only rewrites the draft. Drafts expire after about 30 minutes.
- Find free time: Range is at most 31 days; returns 20 slots unless `maxResults` (up to 100) is set. Without `page`, slots fall Mon to Fri 9:00 to 17:00 unless `workingHours` is passed. With `page`, returns the slots `book_meeting` accepts; an inactive page has none.
- Create a meeting: Does not add an event to the user's calendar. Keep the returned `recap_id`: the brief, notepad and meeting calls take it.

Before step 1, confirm access with the cheapest read-only call, like a list or a search. Never send or change anything to test access.

## Steps

1. **Find the call** with Search meetings (Bridge). Find `meeting` and confirm it with the user. Keep its `recapId`.
2. **Read the call** with Get meeting details (Bridge). Keep the buyer's names and emails, and the commitments each side made.
3. **Check for a plan** with Get a follow-up plan (Bridge). Get the latest plan for the `recapId`. If there is one, keep its steps and skip step 4.
4. **Create the plan** with Create a follow-up plan (Bridge). Generate a follow-up plan for the meeting. Keep its plan id and steps.
5. **Draft the email** with Act on a follow-up step (Bridge). Run `draft` on the follow-up email step. If it fails with "Needs input" (e.g. a recipient who was not in the meeting), ask the user for what is missing and run `draft` again with it as `details`. To add `resources` and the commitments from step 2, run `approve` with them as `revision`: it only rewrites the draft. Show the user the new `draft_preview`.
6. **Send it** with Act on a follow-up step (Bridge). After the user approves the exact preview, run `approve` on that step without `revision`. Skip or check off the other steps as the user says.
7. **Find a time** with Find free time (Bridge). Search the window in `next_meeting` for slots of its length, with `maxResults` set to 100, and offer the user three on different days. Keep the one they pick.
8. **Book the next call** with Create a meeting (Bridge). Schedule the meeting at the chosen time with the buyer's emails as invitees. Keep its join link for the user.

## Notes

The follow-up email goes out from the user's connected Gmail; without one, copy the approved draft into any email tool. To send the buyer a link to pick the time themselves, share a booking page instead of steps 7 and 8.

## Rules

- Use only the services set up above. The read-only calls they need, like listing ids or polling for results, are fine.
- Ask the user before anything that sends messages, costs money, or changes data, and say how many records it touches. One approval covers a batch the user has seen.
- Never print API keys.