> For the complete documentation index, see [llms.txt](https://wiki.dieagenturverwaltung.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/wiedervorlagen-1.md).

# What are followups?

They can be created, for example, in contacts, jobs or financial documents and will then remind the relevant person at the desired time with a notification that appears under the menu item "Wiedervorlagen".

> **Application scenarios**\
> A customer asks for 6 weeks to approve an estimate; the project manager could set a followup for themselves in six weeks to remind them to follow up on this estimate.\
> \
> A new business contact we spoke to today cannot make a decision about an assignment at this time because they are waiting for other developments in their company. However, they ask for a callback in four months. We can, for example, automatically set this contact to reappear for our head of sales in four months with a note about our conversation today.\
> \
> Certain usage rights for the music of a film we produced for a customer expire in 2 years; it is reasonable to assume the customer will want to extend the use of the film (and thus the music). The project manager sets a followup for an appropriate time—e.g., in 22 months—to be reminded that they can offer the customer a re-licensing in good time. \
> \&#xNAN;*If the project manager is no longer with the company at that time, the followup is automatically transferred to their successor.*

On the one hand, a followup can be created for yourself, for example to remind yourself of a date to follow up on an estimate that has not yet been approved. Alternatively, you can assign a followup to another team member to point them to a deadline or a necessary process step or task, or simply to inform the team member.

{% hint style="info" %}
**Tip: Use followups as a record of conversations**\
In many cases it can make sense to create a purely informational entry in the followups without actually resubmitting it to someone. 

Examples: \
"Call attempt on 28.04, not reached" \
"Max Muster left the company in July."\
"Not interested in content marketing"
{% endhint %}

{% content-ref url="/pages/3c5ce7ac63a4a4b355970cf73547baca3cee6d10" %}
[How followups are created](/die-agenturverwaltung-en/wiedervorlagen-1/so-werden-wiedervorlagen-angelegt.md)
{% endcontent-ref %}

{% content-ref url="/pages/348eef7bf9e203596b983da9f2b869eb8fef6b9b" %}
[Notifications](/die-agenturverwaltung-en/wiedervorlagen-1/benachrichtigungen.md)
{% endcontent-ref %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/wiedervorlagen-1.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.