# Follow-Up robot in Yoxel Add-ons

## Meet Yoxel Follow-Up robot

***

A powerful feature of the Yoxel add-on that automates following up with your contacts and increases email response.

### Activating Follow-Ups

***

<figure><img src="/files/bcb5R4g5tmt5cGPE04xh" alt=""><figcaption></figcaption></figure>

You can activate a follow-up sequence of emails for any email thread for which you're expecting a response. Just click **'Activate Follow Up'** and choose a rule.\
You can also create a new rule directly from here and activate it immediately.

<figure><img src="/files/dEzwcBf4tjWdf3craYBl" alt="" width="321"><figcaption></figcaption></figure>

Additionally, you can add more target recipients for follow-ups, ensuring that key stakeholders receive reminders.

<figure><img src="/files/074pJRy9G78q9P461gSz" alt="" width="316"><figcaption></figcaption></figure>

### Configuring Follow-Up Rules

***

Once a follow-up rule is activated for an email thread, it cannot be modified. However, you can:

* Deactivate the follow-up sequence if needed.
* Manage and update follow-up rules in the settings before applying them to new email threads.

### Managing Follow-Up Rules

***

Manage your follow-up rules on the Follow-up page:

<figure><img src="/files/0rrbO5gL2qWUkvIc0T9g" alt="" width="316"><figcaption></figcaption></figure>

Use the Follow-Up page to manage active sequences, deactivate rules, or update messaging as needed.\
Set up as many rules as you need for different business situations:

<figure><img src="/files/FHIdeUjeXjscxHaYxNOH" alt="" width="315"><figcaption></figcaption></figure>

### Defining a Follow-Up Rule

***

A rule essentially defines a sequence of actions (wait time + follow-up email). An action defines how many days to wait for a response from a contact (optionally just in this thread) and what message to send if there is no response.

<figure><img src="/files/tKqSKYN2lnMO8iOU4eGG" alt="" width="318"><figcaption></figcaption></figure>

When setting up a rule, you can enable the **"Expect a thread response"** checkbox. If selected, the follow-up sequence will automatically stop once a response is received in the thread.

### Default Follow-Up Sequence

***

The add-on automatically provides the following default sequence:\
\
1\. Wait for 4 days, email "Ping... just checking in to see if you got this."\
\
2\. Wait for 6 days, email "Did you get my emails below? Let me know if you are interested in discussing."\
\
3\. Wait for 10 days, email "Ping... I have not heard back. Let me know if you want to have a convo."<br>

### Creating a Follow-up with Merge Variables

***

After setting up the rule condition, create a follow-up that includes a Drip message. This Drip message will be automatically sent when the rule is triggered.

In the message body, you can use your own `{{merge variables}}` such as `{{Name}}`, `{{Company}}`, and more.&#x20;

Example message:

<figure><img src="/files/U5PjO3SL0bWqvIOuYRHY" alt="" width="317"><figcaption></figcaption></figure>

When you activate the rule for a new email thread, the addon will prompt you to provide values for these variables if they are not automatically populated.

<figure><img src="/files/qYuZpL7r2MYwET7zDNDO" alt="" width="311"><figcaption></figcaption></figure>

The message will be filled in with the values you provided for the variables and will look like this:<br>

<figure><img src="/files/2wdFqZGQ28sJ1SGEPfbM" alt="" width="308"><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://helpdocs.yoxel.com/yoxel-addons/follow-up-robot.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.