> For the complete documentation index, see [llms.txt](https://docs.fyxer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fyxer.com/workflows/fyxer-in-practice/workflows-by-use-case/never-drop-a-follow-up.md).

# Never drop a follow-up

Keep track of what you promised, and take action.

### Who it's for <a href="#who-its-for" id="who-its-for"></a>

Anyone who makes promises on calls and over email, or with back-to-back meetings and no gap to write things down.

***

### Sound familiar? <a href="#in-your-words" id="in-your-words"></a>

> "My days are back-to-back meetings, with very little time to follow up on what I’ve promised my clients. Trying to hold it all in my head is stressful, and I'm constantly worrying that I've forgotten something."

***

### Why a Flow fits <a href="#why-a-flow-fits" id="why-a-flow-fits"></a>

Each follow-up only takes a few minutes. The hard part is remembering it's due, when the next meeting is already starting.

A Flow remembers for you. It can run after each meeting and list what you agreed to do, or run once a week and flag outstanding actions.

Then you can ask Fyxer to draft the follow-up there and then.

{% hint style="info" %}
You might not see Flows yet. We're rolling this feature out gradually as we test and refine it, so availability will vary. We'll keep this page updated as things evolve.
{% endhint %}

***

### Set it up <a href="#set-it-up" id="set-it-up"></a>

1. Go to [Dashboard](https://app.fyxer.com) → Flows → **Create Flow**
2. In the prompt box, ask Fyxer to send you a message after each meeting with the actions you owe, or copy the instructions below
3. Check the Flow Fyxer creates and edit the trigger, instructions, or delivery method, if you need to
4. Select **Save**

***

### Instructions to copy <a href="#instructions-to-copy" id="instructions-to-copy"></a>

After meeting follow-up Flow

> After each meeting with someone outside my company, list what I agreed to do, with any dates mentioned, and send it to me in Slack.

Weekly catch-all Flow:

> Every Thursday at 3pm, send me an email with a list of my open actions and emails I need to reply to.

***

### Hand it over <a href="#then-hand-it-over" id="then-hand-it-over"></a>

When the list arrives, ask Fyxer to do the next step. In Slack or Teams, or by replying to the email:

> Review my open actions. For any that are best handled by email, prepare a draft. Skip anything that does not need an email. Then tell me which actions you drafted for.

Review the drafts and send.

***

### Learn more

Find out [**more about Fyxer Flows**](https://support.fyxer.com/article/set-up-fyxer-flows) in the Help Center or watch this short video:

{% embed url="<https://vimeo.com/1232321687>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fyxer.com/workflows/fyxer-in-practice/workflows-by-use-case/never-drop-a-follow-up.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
