> ## Documentation Index > Fetch the complete documentation index at: https://docs.custral.com/llms.txt > Use this file to discover all available pages before exploring further. # Task Types > Learn the built-in task types in Custral (Call, Email, Meeting, Follow-up, and more) and the fields every task shares. A task's *type* is the kind of action it represents: a call, an email, a follow-up, a review. In Custral each type is backed by a built-in **task block**, which gives the task its icon, its title format, and the fields it collects. Whatever its type, every task then shares the same core lifecycle: a status, a priority, an optional due date, one or more assignees, and an optional linked record. *** ## Built-in task types Custral ships a fixed set of task types. You don't define new ones. You pick a type when you create a task, or a workflow or sequence step picks one for you. | Type | What it's for | | --------------- | --------------------------------------------------------------------------------------------------- | | **Call** | Call a contact. The task shows a **Call** button that dials the number through the built-in dialer. | | **Email** | Send an email. Optionally using an email template or template pool. | | **Meeting** | Schedule or attend a meeting. | | **Follow-up** | Follow up on a record after an interaction. | | **Review** | Review a document or record. | | **Research** | Research a topic, person, or company. | | **Manual task** | A generic, freeform to-do for anything that doesn't fit a specific type. | Two more types are generated by the system rather than created by hand: | Type | What it's for | | ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Audit** | An auto-generated workspace health item (for example, a record missing a description). It opens an AI-assisted remediation panel so you can fix the issue in place, and a queue of them can be cleared quickly from **Quick Mode**. | | **Permission request** | Raised when a teammate requests access to an entity, so an admin can review and grant it. | The set of task types is built in. You choose a type when creating a task. There is no separate screen for defining your own custom types. For anything that doesn't fit a specific type, use **Manual task**. *** ## Fields every task shares Regardless of type, each task carries the same core fields: * **Title & description**: what needs to be done. * **Status**: Pending, In progress, Completed, or Canceled. * **Priority**: None (the default), Low, Medium, High, or Urgent. * **Due date** *(optional)*. When it should be done. * **Assignees**: one or more users responsible for the task. * **Associated record** *(optional)*. A link to the record the task relates to, for context. * **Source**: the task block that created it (its type). Each type layers its own fields on top. A **Call** task adds a phone number; an **Email** task adds a subject and an optional template; a **Meeting** task adds a topic. The fields shown when you create the task reflect its type. *** ## Type vs. category Two different axes describe a task, and it's easy to conflate them: * **Type** is *what kind of action* it is. Its task block (Call, Email, Review, …). * **Category** is a grouping label (**Manual**, **Workflow**, or **Audit**) used to filter the [Activity Center](/team/tasks/overview). A workflow-generated Follow-up and a hand-created Follow-up are the same *type* but different *categories*. *** ## Where tasks come from Tasks (and therefore their types) are created in a few ways: * **Manually**: pick a type and fill its fields (title, due date, assignee, associated record). A conversation **follow-up** is a manual task linked back to that conversation. * **From a workflow**: the *Create Task* action chooses a task block, fills its parameters, assigns it, and optionally links it to a record. * **From a sequence**: a step can generate a task as part of an enrollment. * **From the workspace audit**: Audit tasks appear automatically when a health check finds something to fix. *** ## Working with tasks Every task lands in the **Activity Center**. From there you can filter by priority and category, drag to reorder your queue, bulk-complete or delete, open a task for detail, jump to its associated record, and (for Call tasks) dial the contact directly. Audit tasks can be resolved in bulk from **Quick Mode**. *** ## Troubleshooting **I can't find where to create a custom task type.** Task types are built in. There's no screen for defining new ones. Choose an existing type when you create a task, have a workflow create one, or use **Manual task** for anything freeform. **My Call task's Call button is greyed out.** The Call button dials the task's **Phone Number** field. If that field is empty, the button is disabled. Add a number to the task (or to the linked record) and it becomes active. **An audit task won't go away.** Audit tasks are cleared by resolving the underlying issue from the task's remediation panel (or **Quick Mode**), or by marking the task done, not by ignoring it. *** ## Related * [Tasks overview](/team/tasks/overview): the task lifecycle, priority, and the Activity Center. * [Workflows](/automation/workflows/overview): automate task creation with the *Create Task* action. * [Sequences](/automation/sequences/overview): generate tasks as steps in an outreach flow. * [Permissions overview](/team/permissions/overview): task visibility follows the same access model as the rest of Custral. ## Related topics - [Task Types](/automation/workflows/task-types.md) - [Tasks](/dev/webhooks/events/tasks.md) - [Implementation](/start/use/implementation.md) - [Team & Permissions](/team/overview.md) - [Workflow Actions](/automation/workflows/actions.md)