Skip to main content
A sequence draws its contacts from a table you already have. Open one in Sequences and pick the table and its rows in one step, on the Audience tab.
The Audience tab of a running sequence with its settings unfolded: the Pipeline table with a Change audience button and a line reading all 10 rows, kept in sync, a Keep in sync with Pipeline switch, and dropdowns under Columns we need from this table. Below them sit a banner counting the messages waiting for approval with a Review in Tasks button, tabs counting contacts as All, In progress, Needs approval, Done and Blocked, and the contact list with each contact's status and next step.

The Audience tab, table and view chosen.

​
Point the sequence at a table

1

Choose an audience

Click Choose an audience, or Change audience once one is already set.
2

Choose the rows

In the same dialog, pick All rows or one of the table’s saved views. Only that view’s rows are enrolled, and the sequence follows the view as it changes.
3

Confirm

Click Use these rows. The tab then reads the table and enrols its rows, which takes a moment on a long one.

​
Check the columns it needs

Click the arrow beside the table’s name to open the audience settings. Under Columns we need from this table, the dropdowns come filled in from the table. A dropdown left on Not set says under it what that costs, but only for a channel the sequence uses. When the table has a column that looks right, that line offers it. Changing one is allowed on a running sequence. It waits in Review changes for Make changes live, or Apply changes when paused.

​
Control who joins

The tabs over the contact list count the audience, or only your search’s matches. Blocked counts who is held back, and each of their rows says why. Keep in sync sits under the same arrow, and starts on when you choose a new audience table. New reachable contacts join automatically, and contacts who leave the selected audience stop. Switch it off to freeze membership; choosing the same table preserves that choice. Contacts the cooldown refuses are stopped, then start at step one once the window passes. See Cooldown.

​
Pause, resume, retry or remove someone

The contacts are listed under the audience. Tabs over the list put each contact in one group, and clicking one shows only its contacts:
  • In progress: still in the cadence. Before launch it reads Not started
  • Needs approval: a step waiting for your approval in Tasks
  • Paused
  • Done: finished, replied, unsubscribed, stopped, removed or already connected
  • Blocked: unreachable, do not contact, in another sequence, in cooldown, bounced, mailbox removed, or a step that stopped
Open a contact’s row menu to Pause, Retry or Resume them. Tick rows for a selection bar at the end of the filter row:
  • Pause, Resume, Retry and Stop
  • Remove takes them out for good. A removed contact stays out even while the audience stays live
  • On a narrow tab, whatever does not fit moves into the bar’s More actions menu

​
Good to know

Each row’s status says exactly where that contact stands. Needs approval and Paused have no Status column, since every row there would read the tab’s name.All is always there, and any other tab shows only while someone is in it. While the sequence is paused, everyone still in the cadence is under Paused. Anyone held by a mailbox, a browser or a limit stays under In progress, with the hold named on the row.While you search the list or narrow it with Filters, each tab counts only the contacts that match, so searching one name reads All 1. A tab nobody matching is under reads 0. The alerts above the tabs still count the whole audience.If the matches can’t be counted, the tabs show their names alone until they can. The list and the tabs keep working meanwhile.Ticking every row under a tab reaches only that tab’s contacts. Under Needs approval or Paused, a contact you stop leaves the list at once. Undo in the message that follows brings them back.
Pause works on anyone still in the cadence of a launched sequence. Retry is for a contact reading Interrupted or Could not write. Resume brings back one paused, stopped on a reply, or reading Mailbox removed.While the sequence itself is paused, the contacts it holds under Paused go on when you press Resume sequence at the top of the page.A paused contact whose row leaves the audience reads Left the audience and frees them for other sequences. If the row comes back, they are paused again.
No. Choosing or changing the table leaves the steps as they are.On a draft, click the campaign’s name on the Builder canvas, beside Fit, then Tailor to the audience. It fits the campaign to these people by rewriting each step’s prompt. See The outbound agent.
In the picker, the button reads Review replacement. On a draft it opens Review audience replacement, which counts what the change does to your contacts: Added, Removed and Not changed. Why contacts are left out lists why some rows won’t be contacted.On a launched sequence the dialog is titled Change audience and only asks what happens to existing contacts. Continue to review opens Review changes, which shows those counts beside your other changes.Another view of the same table is a new filter. Carry on where they are keeps everyone the new view still selects where they are, and stops the rest, who read Left the audience. A running sequence keeps sending, and this applies even with Keep in sync off.A different table offers Let them finish where they are, which keeps existing contacts where they are, on their original audience data. A kept contact whose row is in the new selection joins it, and stops if their row later leaves it. A kept contact whose row is deleted stops.Stop them and start fresh starts selected contacts at step one, including when you choose the same table. Added then counts everyone who starts again. Previously contacted people may receive messages again, and the do-not-contact list and cooldown still apply.A running sequence pauses once a different table, or Stop them and start fresh, goes live from Review changes. Cancelling the picker leaves the audience unchanged.
Every sequence that keeps in sync with the table applies the new filter as soon as you save it. New matches join, and contacts it no longer selects stop and read Left the audience. Loosen the filter again and they carry on where they left off.Update view first counts what the new filter does to each of those sequences, in Added, Removed and Not changed, and asks you to confirm. A filter that adds and stops nobody saves straight away. A sequence with Keep in sync off ignores the edit.
No. Deleting it would point the sequence at the whole table, so the delete is refused and names the sequence. Change its audience first, then delete the view.
Every column on the table is one, under its own name. Type {{ in a step’s subject or body and pick it from the list. There is nothing to set up first.
The Email address dropdown sits on Not set, and the line under it warns that email steps won’t run. Pick the column that holds it, or the one that line offers, and the warning clears.That column is also the deduplication key, so the wrong one there is the difference between contacting each lead once and contacting them several times.
Set Email deliverability to the table’s Verify email column over the email column. It is filled in when the table has one, and opens once Email address is set. Send to picks the verdicts the sequence emails, starting on Valid.Without it, the tab warns that unverified emails can raise your bounce rate. Verify emails adds the column and points the sequence at it. It checks only the addresses not verified yet, and the price shows before anything runs.
Its email steps are skipped, as if the contact had no address. LinkedIn steps still run for them, and a Has an email address? check takes its No branch. In a sequence of only email steps, they reach the end without an email.Click the contact to see each skipped step in their history, with the verdict that skipped it. The step they wait on reads Will be skipped when their verdict means it will be.An address the column has not verified yet waits for its verdict before its email goes out. Verify emails checks the ones still waiting. An answer the column could not give counts as Unknown.
The line under its dropdown counts the rows that have a value, such as “42 of 50 rows have one.” Under Email address it counts the people left out instead, such as “8 people have no email and won’t be emailed.” A column every row fills in has no line.
Then there is no choice to offer, so the dialog names the table’s row count instead, such as “All 120 rows”.
In the order the view shows them when you launch. A view sorted with the highest score first reaches your best leads first. With no sort, the table’s row order is used, top to bottom.The order is set at launch and kept when sending waits for the window or a daily limit. Sorting the view later does not reorder contacts already waiting. Rows that join after launch go after them.Each LinkedIn account works through its contacts in that order, one step at a time. Messages the AI writes go out as each one is finished, and a step that needs approval goes once approved. Emails leave a few at a time per sender, so contacts close together in the list can swap.Once a sequence is launched, the Audience tab sorts contacts by Status. Whoever goes next is on top, and contacts waiting on your approval follow everyone still in line. Contacts paused by hand come next, and everyone who has left the cadence is at the bottom. Before launch it sorts by Added, newest first.Click Status to reverse it, under any tab that shows that column. Each row’s Next step says what comes next and when. Hover a status such as Queued to see why it waits.
When it has an address the sequence can send to. A row added by hand starts empty. It joins the moment you type the email address or LinkedIn profile URL into it, not when you added the row.While email or LinkedIn enrichment runs, the Audience tab refreshes every two seconds. Newly reachable contacts join when Keep in sync is on. With it off, coverage counts refresh while membership stays frozen.
It stops this sequence reacting to the table. Contacts already enrolled carry on through the cadence exactly as before, rows added to the table are ignored, and rows removed from it stay enrolled. To add the table’s new rows anyway, ask the AI Assistant to sync the audience.A new filter saved on the view it follows changes nothing either. An audience you pick on the Audience tab still applies once, so contacts a new view leaves out stop.
Because the company is read from each contact’s email address, and the Company domain row says so. The dropdown appears only on a LinkedIn-only audience, where there is no address to read it from.To keep a whole company out of every sequence, add its domain to the do-not-contact list.
A step failed for them, and they stay on that step until you retry it. Hover Interrupted to read why. A failed step never runs again on its own.Retry is in the contact’s row menu and on a selection, and Retry all on the banner above the list retries every interrupted contact it can. A LinkedIn step runs again with the same words and approval. See LinkedIn steps.A contact stopped because a withdraw found them already connected has no Retry, because there was nothing to withdraw. Retry all leaves them out too.
The mailbox that first emailed them was deleted, or its sender is no longer on this sequence. A contact is only ever emailed from that one mailbox, so they stop at their next email. LinkedIn steps before it still run.The row names the address. Once it is back on a sender this sequence uses, resume them one at a time or with Resume all.
When the wait they were in would have ended, not the moment you resume them. Someone paused an hour into a one day wait is still due a day after that wait began. If that time has passed, they are due at once, and the step goes out as the sending window and the sender’s limits allow.The same holds for a contact resumed after a reply stop, and for a failed contact you retry. It holds too for a row that left the audience and came back, and for Resume all after an out of office reply. A wait you changed in between counts at its new length.
Yes. Send now in their row menu, or on a selection, makes their next step due at once. The sending window, the sender’s pacing and daily limit, and any approval still apply.A contact waiting for the answer to a connection request has no Send now, because their next step depends on that answer.
No. Removing them here only takes them out of this sequence. Any other sequence they are in keeps running.
Yes. Choose Move to another sequence… from the same row menu. They stop here and start at the first step of the sequence you pick, as long as it shares this one’s audience table.
Their history, from when they were added to the step still to come. Each step is titled like “Step 1 · Opener”, and an email’s subject sits under its title. A step they were moved past without it going out reads Skipped, with why under it.On a narrow tab, such as beside the AI Assistant, the contact takes the list’s place. Close the contact and the list comes back where you left it.
Nothing is running for them until launch, so they read Not started and there is nothing to pause. Remove from this sequence still takes one out. A draft does not hold its contacts either, so another live sequence can still reach them first.

​
Next steps

Build a sequence

Add the steps this audience will move through.

Schedule and sending window

Decide when the sequence is allowed to send to them.