# Work tasks in the Chrome extension

> Create tasks, filter and snooze them, add a follow-up after an outreach step, and work through a batch you launched from the Tasks page of the Reply web app.

**The Tasks tab holds everything assigned to you, both what a sequence generated and what you added by hand, and Launch tasks steps through them one at a time. Build a new one by choosing a type, dates and a contact; work an open one with Complete, Send and complete, Clone, Edit, Snooze for 24 hours or Delete. Whether task execution is part of your subscription depends on your plan, which you can check under Plans and Billing.**

_Status: Reviewed – written against Reply's product documentation on 2026-09-22, not yet confirmed against the running product._

## Goal

A worked queue: every [task](/specifications/tasks/) due to you today either completed,
rescheduled or deliberately dropped, with the sequence behind each one moving on
accordingly.

## Preconditions

A subscription that includes task execution: where it is not included, the extension shows
a notice in place of the list and no tasks can be run, so confirm the entitlement under
Plans and Billing in the web app. Tasks that involve messaging need the matching channel
ready: a connected mailbox for email types, a rented number for calls and SMS, a LinkedIn
session for the social types.

## Steps

1. Open the **Tasks** tab at the bottom of the extension. It lists tasks from across your Reply account, whether a sequence produced them or you did.
2. Narrow the list with **Filters**: a **Date** range with **From** and **To**, **Tasks status**, **Tasks type**, **Sequence** and its steps, and **Contact time zone** for calling people while they are awake. Apply the filters and the list redraws. Which filters you see depends on your account, so the set may be shorter than this.
3. Add one of your own from the toolbar's create control. Pick the type (**To Do**, **Email**, **Manual email**, **Call**, **Social media**, **Connect**, **Message**, **Social email**, **View profile**, **Meeting**, **SMS** or **WhatsApp**) set the start and due dates, attach a person with **Add contact** so the task can dial or write to them, choose the sending address for email types, write the body or pull in a template, and create it. On a manual email you can attach up to three files.
4. Open a task to work it. The header carries the contact's local time and quick copies for their email, phone and profile link; the actions along the top are **Complete**, **Send and complete**, **Call**, **Log the call**, **Send message**, **Send social mail**, **Connect**, **Look for social profile** and **Send WhatsApp**, with **Clone**, **Edit**, **Finalize** and **Delete** alongside.
5. Push a task out of the way with **Snooze**. It comes back 24 hours later, unchanged.
6. Chain the next touch on the spot: after logging an outreach step, the follow-up option opens a **New Task** window where you choose the type, the start date and the due date and create it, so the contact is booked for the next action before you move on. This works the same for a task a sequence created as for one you made yourself.
7. Run a batch that was selected in the web app: on Reply's **Tasks** page tick the tasks (or the **All** checkbox and then untick the exceptions) and click **Launch**. The extension opens in execution mode with a counter showing your position in the run, and you work through them in order.
8. Clear out what you no longer need: the three-dot menu on a row offers **Edit** and **Delete**, and selecting several rows, or the all-tasks checkbox, deletes them together.

## Expected result

Completed tasks leave the list and the contact behind a sequence task advances to the next
step. The execution counter in a launched run counts down to the last task, then the run
ends.

## Verification

Open the Tasks page in the web app and filter to the same day. Its statuses should match
what you left behind in the browser, and for a sequence task the contact should now show
the following step rather than the one you closed.

## What happens next

An email you send from a task is subject to the usual
[sequence execution](/behavior/sequence-execution/) rules and shows up in the sequence
report. Where a task ends in a phone conversation, the logging options are covered in
[Call and email contacts from the extension](/how-to/call-and-email-from-the-extension/).

## Common mistakes

- Launching a batch from the web app that is not yours. Owners can see their team's tasks but only run their own, and the extension answers with "Among the tasks that were launched for execution on the platform there are no tasks assigned to account login."
- Including completed rows in a launch. They are skipped silently and never appear in the run.
- Deleting a sequence task to get rid of a contact. The prompt says what actually happens; "This task is linked to the sequence. Delete the task and move the contact to the next step?", so the contact keeps going, one step further along.
- Leaving a variable unresolved in the body. "Task was not rendered: missing variable" means the contact has nothing to fill it with; give the variable a fallback or fill the field on the contact.
- Trying to open a message older than a year from its task. The extension reports that the email has been archived and asks you to contact support to bring it back.

## Related

- [Tasks](/specifications/tasks/) · [Templates and variables](/specifications/templates-and-variables/)
- [Task was not created](/troubleshooting/task-was-not-created/)
- [Variable was not replaced](/troubleshooting/variable-was-not-replaced/)
- [Multichannel outreach](/capabilities/multichannel-outreach/)

## Build with Reply

- REST API: [docs.reply.io](https://docs.reply.io/api-reference/introduction) – read and close tasks from your own tooling
- MCP: [docs.reply.io/mcp](https://docs.reply.io/mcp/overview) – let an assistant triage the queue before you open it