> For the complete documentation index, see [llms.txt](https://v5docs.keyfax.biz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v5docs.keyfax.biz/script-actions/tasks.md).

# Tasks

A task is what a conversation produces: an email to a contractor, a letter to a tenant, a text message, a note on the record, a job in your housing system.

<figure><img src="/files/xNwOaVUssnz7mtPGqIjM" alt="A task open in the editor"><figcaption><p>A task, and the templates it uses</p></figcaption></figure>

## Tasks and templates

A task says **what to raise and who for**. The wording it sends comes from a [task template](/script-actions/task-templates.md), and one task can use more than one — an email to the contractor and a note on the tenancy, from the same conversation.

Keeping them separate means the wording can be corrected without touching the logic that decides when the task is raised.

## Merging in what the conversation collected

Answers and databox values can be merged into the templates a task uses, so the contractor receives the address, the fault and the priority rather than a generic instruction.

## Watching one leave

A raised task goes to [Message queues](/administration/message-queues.md), which is where to look when someone says an email never arrived.