> ## Documentation Index
> Fetch the complete documentation index at: https://hopsdocs.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Post-call follow-up

> Draft the follow-up email from your notes and the account context.

After a call, reps lose time writing the recap and next steps. Paste your notes into the chat and Hops drafts the follow-up using the notes, the account history and your sales playbook.

<Info>
  **How it runs:** Ask Hops, with a skill so the output has the same format every time. No automation needed.
</Info>

## What it does

* **Drafts in the rep's voice.** Hops matches the tone of past emails and keeps it under 150 words.
* **Uses the account history.** Deal stage, earlier threads and open items come from the CRM and Gmail.
* **Follows your playbook.** Templates and messaging pinned in the Space shape the structure of the email.
* **Ends with a clear ask.** Every draft has agreed next steps with dates and one specific ask.
* **Leaves it as a draft.** The email waits in Gmail or Outlook for you to review and send.

<Frame>
  <img src="https://mintcdn.com/hopsdocs/E03FYifT87c9QmFJ/images/use-cases/sales-post-call-follow-up.gif?s=3d94384b6f378272377347637be4ad7f" alt="Gmail connection, Hops drafted the follow-up email in Gmail from the call notes and account history" width="1440" height="810" data-path="images/use-cases/sales-post-call-follow-up.gif" />
</Frame>

## Ask Hops

Copy a prompt into any chat with Hops, or mention `@Hops` in a Space.

```text theme={null}
Draft the follow-up email for Acme. Notes: they want SSO, security review next week, pricing for 200 seats.
```

```text theme={null}
Write a short follow-up to Priya at Globex recapping today's demo.
```

```text theme={null}
Draft a follow-up for Northwind that proposes two times for a technical session.
```

```text theme={null}
Turn these call notes into a recap email and a list of next steps.
```

```text theme={null}
Log the outcome of the Initech call in the CRM and draft the follow-up.
```

Example reply:

> Follow-up drafted for Acme:
>
> * Recap of SSO, security review and 200-seat pricing.
> * Next steps: security review Oct 16, pricing sent by Friday.
> * Draft saved in Gmail, 128 words.

## What you get

* **An email draft** in Gmail or Outlook, ready to review.
* **An answer in chat**, in the same thread, with the recap and next steps.
* **A saved Doc, when you ask for one.** Say "save the recap as a doc" and Hops writes it to **Docs** in the Space.

## Connections needed

Connect these apps. Each card opens Connections in the app.

<CardGroup cols={3}>
  <Card title="HubSpot" icon="hubspot" href="https://app.hops.ai/my-hops/connections">
    Account history and deal stage (or Salesforce).
  </Card>

  <Card title="Gmail" icon="envelope" href="https://app.hops.ai/my-hops/connections">
    Earlier threads and the draft (or Outlook).
  </Card>

  <Card title="Google Drive" icon="google-drive" href="https://app.hops.ai/my-hops/connections">
    Playbooks and email templates.
  </Card>
</CardGroup>

## Set it up

<Steps>
  <Step title="Connect your apps">
    Connect your CRM, Gmail or Outlook and Google Drive in **Connections**.

    See [Connections](/docs/connections/overview).
  </Step>

  <Step title="Pin your playbook">
    Create a Space per major account and add the sales playbook and email templates to Space context.

    See [Spaces](/docs/spaces/overview) and [Space context](/docs/spaces/space-context).
  </Step>

  <Step title="Add the skill">
    Give Hops these instructions:

    ```text theme={null}
    You draft post-call follow-up emails. Use the notes from the thread, the account's CRM history, and the sales playbook in the Space Context document. Match the rep's tone. Keep the email under 150 words. Include a clear next step and a specific ask.
    ```

    See [Build a skill](/docs/agents/build-a-skill).
  </Step>

  <Step title="Ask">
    Ask Hops in chat after each call and paste your notes.
  </Step>
</Steps>


## Related topics

- [Sales](/teams/sales.md)
- [Explore use cases](/use-cases/overview.md)
- [Post-event follow-up](/teams/sales/use-cases/post-event-follow-up.md)
- [CRM follow-up](/teams/sales/use-cases/sales-follow-up.md)
- [Shared follow-ups](/teams/sales/use-cases/shared-follow-ups.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.