Approve and manage sequences

From a sequence in My library, select Add contacts and follow the selection flow. Check the sending user and the selected template or operator before confirming.

Athean verifies whether the selected contacts can use the sequence. When a review is needed, inspect the Review and Blocked tabs. Warnings can identify an existing sequence, recent outreach, bounce risk, email opt-out, or missing channel information.

Review each warning before including the contact. Where the dialog allows it, including a contact accepts the warning and omits steps they cannot complete. No LinkedIn, Email issues, and No phone show which channels are affected. Blocked contacts cannot be included through that confirmation.

If the sending user's email or LinkedIn connection is missing, use Go to Settings and complete the connection before proceeding. If the sequence uses a scheduling-link variable, resolve any sender scheduling-link requirement shown by the flow.

After a batch finishes, read its result. Some contacts may succeed while others fail or are deferred; retry the affected contacts using the result's guidance instead of assuming the whole selection started.

When you add contacts to an operator from My library or Marketplace, the operator researches them and generates personalized drafts. This can take several minutes. Open Sequences → Approvals to review the results before starting outreach.

1. Find the contact and operator you want to review. Open the draft, or use the approvals review flow to work through a set of contacts.
2. Read the full sequence alongside the contact and account context. Check subjects, messages, task instructions, timing, and the sending user.
3. Use Sources, when shown for the generated draft, to inspect the context behind the content.
4. Edit the draft directly, or choose Refine with feedback or Edit with assistant to improve it. Regenerate starts a fresh generation for that contact.
5. Select Approve when it is ready, or Reject if you do not want that draft to start.

In the editor, approval actions save your edits before making the decision. Save & exit saves the draft without approving it. Regeneration can replace the current draft, so follow the save-or-discard prompt if you have unsaved edits.

A declined generation cannot be approved as-is. Read the reason, then adjust the operator or use the available regeneration action. If your organization disables bulk approval, review and approve drafts individually.

Approve uses the draft's stored enrollment settings. Choose Approve with settings when you want to review or change them before the sequence starts.

• Priority sequence: moves automated steps ahead of normal work when sending capacity allows. It does not bypass daily caps or step waits, and it does not reorder manual Tasks.
• Completion deadline: stops unfinished outreach at a cutoff. The picker uses your local timezone, not the contact's. Expiration cancels pending work; a deadline does not make the sequence send faster.
• Cc recipients: adds the chosen addresses to every email step, alongside any Cc on individual steps. These enrollment recipients cannot be changed on a live sequence.

Select Approve sequence to confirm. When reviewing several drafts with different stored settings, ordinary approval preserves each draft's settings; confirming the settings dialog applies its displayed values to the selected set. If a stored completion deadline has already passed, choose a new future deadline or remove it before approval.

Approval creates and schedules the contact's sequence. Follow the resulting work in Active sequences and Tasks; an automatic first step does not necessarily send at the moment you approve.

Open Sequences → Active sequences. Use the Active, Paused, Expired, Completed, and Error filters to find the outreach that needs attention.

Review the User, Sequence, Step type, Progress, Action date, and Status reason columns. Open the contact or sequence for the surrounding context. Action dates are estimates: sending capacity and scheduling rules can change them.

A manual step becomes a Task. Complete the action in Task flow or the contact's task view to let the sequence advance. If a step is no longer appropriate, use Skip to next step when available. Skipping cancels that pending action or skips its Task and advances the sequence; it does not perform the outreach.

Read Status reason before resuming or retrying. A reply, meeting, bounce, or call outcome can change the sequence's status. Some failed automated emails become manual Tasks, while unavailable LinkedIn actions can retry or skip. Check what actually happened to the current step.

Use the row actions or select sequences to apply a batch action. Review the selected contacts and sending users first.

• Pause: stops future progress, cancels the sequence's unfinished scheduled sends, and removes its unfinished Tasks. Completed steps remain recorded.
• Resume: continues from the unfinished work, creating the pending Task or scheduled action again. It does not send the completed steps again, and scheduling checks still apply.
• Delete: removes that contact's sequence instance and cancels its unfinished work. It does not delete the reusable template or operator. Use this when you intend to remove the instance, and review the confirmation.

Pausing also affects an email you scheduled for later as part of that sequence. Resuming can schedule it again. Review Email: sending and tracking if you need to edit or reschedule a particular pending message.

An expired sequence has reached its completion deadline. Resuming it requires confirmation and clears that expired deadline so the unfinished work can continue. A paused sequence whose deadline has already passed may first change to Expired when you try to resume it.

These controls cannot recall an email or other action already sent. An action already processing at a deadline can finish. After any batch change, check the success and failure results and the sequence's latest status.

Use Reassign when the contact needs a different template or operator. Choose the replacement, review its enrollment settings and contact checks, then confirm Reassign.

This changes the outreach assigned to the contact while keeping the sending user. For an active instance, Athean pauses the old sequence before creating the replacement. A template starts a new sequence; an operator generates a new draft that follows the approval flow.

If reassignment fails, Athean attempts to restore the original active sequence. Read the result carefully: if restoration also fails, check the original instance before taking another action. A successful replacement begins its own steps; it is not a continuation at the old sequence's step number.

Reassignment is also available for operator drafts in Approvals. Use it when a different sequence is a better fit, and review the replacement content before approving it.

Access to a reusable template is separate from permission to start or manage sequences for another person. Administrators can grant scoped access in Permissions → Act on behalf. Starting and managing are independent permissions; manual Task actions can require the task assignee's authority as well.

If a control is unavailable, check its explanation and ask your administrator for the relevant access. For an unexpected failure, include the contact, sequence, sending user, and displayed status when you contact support.

Once the outreach has had time to run, use Analyze sequence performance to compare engagement and outcomes. Improve the reusable template or operator based on the results, then review new examples before using the next version.