Skip to main content
Tasks has three tabs, each spanning every sender and sequence, so you start the day here without knowing where each item came from. Open holds what waits on you, Pending what is approved and on its way, and Completed what already went out or was rejected.
The Tasks table, with a row per contact and columns for Contact, Company, Title, Task, Assigned to, and Waiting. Five rows are Send email tasks and five are View profile steps on LinkedIn, assigned to Maya Chen or Jordan Reyes, each with a tick box for deciding several at once.

The Tasks table on Open, with what is waiting on you.

​
Know what lands in Tasks

  • An email step with Needs approval before it sends switched on, and every email while its sender is on Always ask.
  • A message the agent did not rate high, or wrote with too little data, while its sender is on Send when confident. See send mode.
  • Every LinkedIn step while its sequence or its sender asks for one. A step from Try a step never waits here, because that click is the approval.

​
Work the list

In Tasks, each row names the Contact, the Task, its Sequence, who it is Assigned to, and how long it has been Waiting. Open opens first, with every task that needs your approval. Filters narrows it by waiting time, channel, task type, sender, sequence, or Why it needs approval. Click a row to open it beside the table, with the exact text that will go out. Tick rows instead to decide on them together: Approve sends them all, and Reject stops them all after one confirm.
  • Approve sends an email as soon as its sending window and limits allow. A LinkedIn step goes in line for the sender’s browser, which runs it inside the window.
  • On a paused sequence, nothing goes out on either channel. Approve keeps your decision, and the step goes out after Resume sequence.
  • Rewrite the subject or message in the pane first if you need to. It saves as you type, and what you approve is what sends, word for word.
  • Reject stops the contact in that sequence. Nothing later in the sequence reaches them, and the Audience tab shows them as Rejected. On a message the agent wrote, it offers a reason to note, then Stop contact. The reason teaches the agent nothing.
  • Needs work, the thumbs down on a message the agent wrote that is still waiting, opens a box asking what’s wrong. Type a line and press Enter, or click Rewrite. The task stays on Open and reads Writing while the agent writes it again. Then it shows the new message, marked where it changed, under a Will learn card with the learning it proposes. Approve sends the new message and saves the learning. See Learnings.

​
Watch approved work go out

An approved task leaves Open for Pending until it goes out. There, Detail says where each row stands, such as queued, sending, or waiting for its sending window.

​
Read what already went out

Completed lists every email and LinkedIn step that went out from the workspace, and every task someone rejected, newest first. Click a row to read what went out, as it went.

​
Retry a failed step

On the Completed tab, pick Failed under Outcome to list the steps that failed. Open one to read why, then Open task and click Retry to run the same step again.
  • A LinkedIn step runs again with the same words and the approval it already had. Retry never restarts the sequence.
  • Retry checks LinkedIn first, and a step it finds already done is marked done rather than sent twice.
  • When a message or InMail may already have gone out, Retry first asks “Send it again?”. Send again retries it, and Cancel leaves it.

​
Decide who approves what

Each sender decides what their own channel does, on their own page. A sequence can ask for more, never less. See Senders.

​
Good to know

No. An item waits until someone decides, and the sequence’s Audience tab shows the contact as Needs approval meanwhile.
Yes. It counts toward the emails its sequence keeps written ahead, so the agent writes the next contacts once these are sent or rejected.
First thing when its sending window opens, ahead of its own sequence’s other contacts due then. Sequences sharing a sender still take turns, so another sequence’s send can come first. An approved LinkedIn step goes ahead of its sequence’s steps queued after it.
The agent writes a contact’s follow-ups with their first email, so one task covers the whole thread. Each follow-up shows when it goes, such as “3 days later”, and you can edit any of them before you decide.Approve approves the whole thread, and says how many emails that is, such as Approve 2 emails. Each follow-up then sends as written when its turn comes, with no task of its own. A reply or a bounce still stops the rest. Reject stops the contact, so none of them send.
On the sender: Send mode and LinkedIn run mode, both on its Settings tab. Manual run holds every step for a person, and Automatic run lets steps go out on their own within the daily limits. A new sender sends email when the agent is confident and holds LinkedIn steps.On the sequence: LinkedIn approval and Email approval on its Settings tab, each offering Sender default, Send when confident, and Require approval. A step’s own Needs approval before it sends switch works the same way.Both add approval, and neither can remove it: whether a mailbox or a LinkedIn account may act unwatched is the sender’s call. A step shows that switch only while it could change the answer, and names the rule already in force otherwise.Under Senders on the sequence’s Settings tab, a sender whose rule differs from the others carries a chip naming it, such as “LinkedIn: Manual run”. When every sender agrees, none does.Switching a sender to Automatic run approves the LinkedIn tasks that waited only for that setting. Switching back to Manual run returns their queued steps nobody approved to this list.
Every row on Open needs your approval, except one reading Writing. Every row on Pending is approved and on its way, and Detail says where it stands. On Completed, Outcome says how each row ended, such as Sent, Done, Failed, or Not sent for a rejected task. An approved email that never went out reads Failed when the send failed, or Stopped when the contact replied, unsubscribed, or was stopped first.An approved step on a paused sequence stays on Pending and waits. Its Detail reads “Sequence paused” until Resume sequence.A LinkedIn step the browser passed over, such as a request to someone already connected, reads Skipped on Completed.Writing, in the Waiting column on Open, is a message the agent is rewriting after Needs work. The same task stays in its place and takes the new words.A row on Pending has no tick box, and its pane offers no Approve or Reject.
Where each approved row on Pending stands, with any time counting down as you watch:
  • “Running” or “Sending” is going out now, and “Sent” has gone.
  • “Next, in 47 seconds” or “3 ahead, in 2 minutes” is a LinkedIn step’s place in its sender’s line.
  • “Daily limit · resumes in 6 hours” waits for the sender’s limit to reset at midnight in their timezone.
  • “Browser offline” runs once a browser with the extension opens for that sender.
  • “LinkedIn disconnected” waits for the sender’s LinkedIn account to be reconnected, and “Limit at zero” for a limit set to 0 to be raised.
  • “Scheduled · sends in 3 hours” is an email waiting for its sequence’s sending window, in the sender’s timezone. A LinkedIn step reads “Scheduled · starts in 3 hours”.
  • “Sequence paused · Out of credits” waits until the sequence resumes, with the reason it paused. “Contact paused” waits until that contact resumes.
Open has no Detail column. A message the agent is writing again reads Writing in its Waiting column.A failed row says why it failed. For a LinkedIn step, those are the words the step shows when you open it on the sender’s Activity tab. The column appears only while some row has something to say.
Because something holds them back. The message names the one thing that matters most:
  • “They wait for their sequence to resume.” Their sequence is paused, so they go out after Resume sequence.
  • “They wait for the sending window to open.” Their sequence’s sending hours are closed in the sender’s timezone.
  • “They run when a browser is open for Maya.” No browser with the extension is open for that sender.
  • “15 wait for the daily limit to reset.” Those steps are past the sender’s daily limit.
Detail on the Pending tab has each row’s time.Before you approve, the pane warns when the sender has no browser open: “Approved steps wait until a browser is open for Maya.” On a paused sequence it says “Approved steps wait until this sequence resumes.” See Connect LinkedIn.
Yes. Click Check the writing on the sequence’s Builder tab, or open its AI writing tab. A message that would wait here says so under it, with the reason. See The outbound agent.
Open a message the agent wrote. How confident it was and why it is waiting show above the email, and Why the agent wrote it under the email opens the reason for that confidence and the facts it used. To read the doubtful ones first, pick a reason under Why it needs approval in Filters.To approve every message the agent scored above a number you name, ask the AI Assistant. It skips messages a check marked unless you have read them, and it always asks you first.
No. Only Needs work with a reason teaches it, as a learning listed under Learnings on the sequence’s AI writing tab. Your edits, a reason given to Reject, and approving a task with no proposed learning teach nothing. Once you edit a task’s words, Needs work is greyed on it, since the agent can’t learn from your words. See Learnings.
Only if your reason needs it. The agent rereads the message it wrote and the research it wrote it from, then rewrites with your reason. It reads the web again only for a fact that research lacks, and a rewrite that does is charged as a researched message.
Before you save, it throws the proposed learning away and puts the task’s earlier words back. After you save, it removes the learning, and puts the earlier words back while the new ones are still waiting and unedited. Once the new words are edited, approved, or sent, they stay, and the note says so.
The new words are not in yet, and approving would save a learning without the message it came with. Approve comes back once they are. Meanwhile the next task waiting is a click away.
Yes. When ticked tasks carry a proposed learning, the bar says how many it also saves, such as “Also saves 2 learnings”. Each is saved as its card showed it.
Yes. Open it on Completed and click the thumbs down beside the line saying the agent wrote it. Say what’s wrong, then click Show a better version. Nothing is sent again: the card shows what the agent would have sent and the learning to save.
Because its contact has moved on since it failed. They were retried already, stopped, or removed. Retry shows only while the contact is still stopped at that step.A withdraw that found the person already connected never offers it, because there was nothing to withdraw.
On the sequence’s Audience tab, where the contact reads Failed until you retry. Completed, the sender’s Activity tab and the sequence’s Activity tab list the step as Failed, with the same reason. See LinkedIn steps.
On the Completed tab, for the whole workspace: the emails and Inbox replies sent, the LinkedIn steps that ran, and every task rejected here. Each row says whether a person approved it or it went automatically.A sender’s Activity tab, a mailbox’s page, and a sequence’s Activity tab show the same table, holding their own part of it. See Senders.
Each row names the Contact, the Action, who it went out From, its Sequence, the Decision, and the Outcome. Open it to read what went out, as it went.Open conversation, Open contact in sequence, Open in table, and Open task go to where it came from.
Yes, on the Completed tab. Choose Only LinkedIn checks under LinkedIn checks in Filters, or Shown with the rest to list them among everything else.These are the checks of a sender’s own inbox, sent connection requests, and new connections, and reads of one conversation. They reach nobody, so Completed hides them until you ask.
Yes. The newest task is on top, and the list and the sidebar’s count update without a reload.
On Open, use the box at the top of the table. It ticks every row on the page. When any row is already ticked, the same box clears every tick instead.
Type a name, an address, a LinkedIn profile, or a word from a subject into Search tasks.On Open, click Contact to sort the list by name, or Waiting to sort it by when each task arrived. On Pending, that column reads Decided and does not sort.On Completed, filter by Channel, Action, Sender, Mailbox, Sequence, Decision, Outcome, or When, or search by contact or subject. Click Contact or When to sort.Each page holds 50 tasks, with the total under the table. Rows per page shows 25 or 100 instead.
Yes. Ctrl-click or Cmd-click its row, or middle-click it, and the task opens in a new tab with its pane open.The address keeps the list you picked, its filters, and its search, so a copied link opens the same list.
They go out ten at a time. Each group leaves the list as it goes through. You can tick and approve more meanwhile.A group that fails stops the ones after it. They wait on Open again.A group cut off by a lost connection may still have gone through. The list shows which of its tasks still wait.Leaving the page or closing the tab sends the groups still to go.
Company and Title appear only when the contact’s table has them.Otherwise the list is too narrow for all of them, such as beside the AI Assistant. Title gives way first, then Company, Assigned to, Sequence and, on Pending, Detail. The contact, the task, and Waiting or Decided always show, and a wider window brings the rest back.
The list is filtered to one sequence, and the filter already names it. Clear it in Filters to bring the column back. It is also hidden when none of the tasks listed came from a sequence. A task that no sequence made, or whose sequence is in Trash or deleted, shows a dash under Sequence.
No. The extension’s side panel runs approved steps and can skip one, but approving and rejecting happen here for every sender and channel.
No. Checks of your inbox, your sent requests, and your new connections run on their own in every mode, so the list only ever holds work that reaches someone.
Oneprofile couldn’t tell whether a contact accepted a connection request by the end of its wait, so it looks at their profile once. The row reads “Check whether they accepted”.The look is a LinkedIn step of that sequence, so it waits here whenever the sequence’s other LinkedIn steps do. Approve it, and the contact goes down the branch the look finds. See LinkedIn steps.
Because they had moved on while you were reading. A browser ran the step, the contact replied, or a teammate decided it first. The rows that could still be decided were, and the count says how many of each.
Any AI-written part of an email is written when the task is created, so you read exactly what would send. That writing is charged once, whether you then approve or reject.
No. Once approved, an email goes out as soon as its sending window and limits allow, and a browser may already be typing the LinkedIn step. To stop that contact, tick them on the sequence’s Audience tab and click Stop.On a paused sequence the approved step is still waiting, so stopping its contact before Resume sequence means it never goes out.
Pausing a sequence keeps its tasks, and you can still approve or reject them. Nothing goes out on either channel until Resume sequence, approved steps included. Only a LinkedIn step a browser had already started may finish.Moving a sequence to Trash withdraws every task it created, and a reply typed in the Inbox still sends. Restoring it does not bring them back: each contact’s step asks again once you resume the sequence. Stopping a contact withdraws theirs, and resuming them asks the step again.
Each opened task says who approved or rejected it, and when. The contact’s timeline on the Audience tab carries the same entry.

​
Next steps

Email steps

Switch on Needs approval before it sends on one step.

Build a sequence

Set a sequence’s own approval mode.

Branch on a condition

Branch the sequence on a reply or a connection.

Connect LinkedIn

Connect the browser that runs approved LinkedIn steps.