---
name: outreach
description: Outreach with Unify, create email sequences, generate per-prospect copy previews, enroll prospects, and manage rep tasks (calls, LinkedIn touches, to-dos). Use when the user wants to email prospects, write outbound copy, start or edit a sequence, check what's in flight, or work their task queue.
---

# Outreach: sequences and tasks

Outreach briefs go through `run_agent` (see `agent-runs`). Sequences have a strict
safety lifecycle. Use its vocabulary precisely with both the agent and your user.

> **Deterministic alternative.** The public API exposes direct tools for
> inspecting and managing existing sequences, enrollments, and tasks without the
> agent: `list_sequences` / `retrieve_sequence` / `list_sequence_steps`,
> `list_sequence_enrollments` / `create_sequence_enrollment` /
> `pause_sequence_enrollment` / `resume_sequence_enrollment`, and
> `list_tasks` / `create_task` / `complete_task` / `update_task`. To export large
> volumes of enrollments, enrollment steps, or tasks, use the async **Bulk API**
> tools. All require an API-key connection (`X-API-Key`).

## Sequence lifecycle (safety-critical)

1. **Scaffold**, the reusable structure: steps (emails, calls, LinkedIn touches),
   delays, and copy prompts. Creating a scaffold sends nothing.
2. **Preview**: per-prospect generated copy. Still sends nothing.
3. **Approved**: previews are ready to be enrolled.
4. **Enrolled**: prospects are in the sequence and email actually sends.

Never tell your user someone is "enrolled", "started", or that anything "sent"
before step 4. Default briefs should end at previews: "create previews for these
10 people and stop for my review."

## Writing sequence briefs

Include: who (people, by DataTable ID, List, or identities), the offer/value
proposition and any proof points, desired tone and sender voice, step count and
channel mix (2–4 steps typical: email + LinkedIn + call), cadence ("3 days
between steps"), and the sending mailbox if the user has a preference. The Unify
agent is the copywriter: give it real context (why now, what triggered this,
what the prospect cares about), not template text. If prospect context is thin,
it will pause and ask to enrich first; that gate is correct. Relay it.

Per-prospect copy edits ("make the email to Jane mention their Series B") edit
that preview only; scaffold edits propagate to everyone. Say which you mean.

## Checking state

"What sequences do we have?", "who replied?", "how is sequence X performing?",
"which previews are waiting on my approval?" are all valid briefs.

## Tasks

Reps' one-off manual to-dos: calls, LinkedIn profile views/connects/messages,
action items. Useful briefs:

- "What tasks are due today?" / "what's overdue for me this week?" (defaults to
  the signed-in user; name a teammate to scope differently).
- "Create a task to call Jane Doe at Acme on Friday" (self-assigned, manual types
  only).
- "Complete/skip my ready LinkedIn tasks for Acme." Email-reply tasks are
  completed by actually replying, not by marking done.

## Mailbox voice profile

Unify can analyze a mailbox's sent mail to build a **voice profile** that
shapes generated copy. When a run kicks that analysis off, check progress with
`load_mailbox_voice_profile({ connectedMailboxId })` (ID from the run result's
structured content), poll only while `isTerminal` is false; it's read-only.