> For the complete documentation index, see [llms.txt](https://docs.senseloaf.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.senseloaf.ai/agents-output/engagement-activities.md).

# Engagement Activities

A complete timeline of every interaction with a candidate

Engagement Activities give you a running record of everything that has happened with a candidate — from the moment they enter your pipeline to wherever they are now. Instead of piecing together what was sent, when, etc., it's all in one place in chronological order.

This is especially useful in team hiring setups where multiple recruiters are involved and alignment matters.

### What's included

* **Messages and communication** — all outreach sent to the candidate, including invite emails, reminders, and any direct communication
* **Prescreening interactions** — when the prescreening invite was sent, whether the candidate opened it, and when they completed or abandoned it
* **Interview-related updates** — when the interview invite was triggered, reminder activity, and completion status

### Communication history

From the Candidate Listing page, you can view a detailed communication history for each candidate directly from the row-level actions.

<figure><img src="https://1117388020-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGO7J9uIHFkn8y0ZeBqYC%2Fuploads%2F6LtMIa4q4n8Pj3yS2uh6%2FCommunication%20History.gif?alt=media&amp;token=8991ba71-bead-4979-9235-52fa6d9349b6" alt=""><figcaption><p>Communication History</p></figcaption></figure>

The communication history shows:

* When the AI interview email was sent
* Whether any reminders were triggered and when
* When the email was delivered, opened, and clicked

If SMS is enabled for your workflow, SMS activity is also visible in the same communication history, so all candidate communication is tracked in one place regardless of channel.

### Re-triggering prescreening or interviews

If a candidate missed their prescreening or interview, or was unable to complete it for any reason, you can re-trigger it directly without having to set up a new workflow.

**From the candidate listing**&#x20;

<figure><img src="https://1117388020-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGO7J9uIHFkn8y0ZeBqYC%2Fuploads%2FSsLnLZvXMBUIL2Tk00x9%2FScreenshot%202026-07-10%20at%2018.31.32.png?alt=media&amp;token=d1470299-2f93-4831-a0b6-92ba4dba4cf4" alt=""><figcaption><p>Resend Invite from Candidate Listing</p></figcaption></figure>

On the candidate listing page, open the actions menu (⋯) on any row to retrigger the AI Prescreening or AI Interview.&#x20;

**From the candidate report card**

<figure><img src="https://1117388020-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGO7J9uIHFkn8y0ZeBqYC%2Fuploads%2FYFjCCEoQvldj7m6mTUoz%2FScreenshot%202026-07-10%20at%2018.37.00.png?alt=media&amp;token=d3ce76a5-bec6-4f3a-bdc2-bd15dc584f92" alt=""><figcaption><p>Resend Invite from Report Card</p></figcaption></figure>

On the candidate's report card, click the dropdown icon next to the favourites action. From here you can resend the prescreening or interview invite directly to the candidate.


---

# 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.senseloaf.ai/agents-output/engagement-activities.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.
