What the platform has: Broadcast has no sequence or drip feature. A broadcast is one email to one audience. So each step of the sequence is its own draft broadcast. To space them out, a person either schedules each one in the composer, or turns on an automation that sends step 1, waits, sends step 2, waits, and sends step 3.
Video tutorials for this topic
That automation is a mailing to the group on fixed dates. It is not timed per person. Someone added to the group after step 1 has gone out only gets the later steps. Each step goes to whoever is in the group on its day, minus anyone who has unsubscribed or bounced since.
A broadcast sends real email to real people, and there is no test mode. This skill only ever produces drafts. A person presses Send or Schedule, or turns the automation on.
Ask first
- Which leads? The pipeline and the stage by name, e.g. "Sales pipeline, Qualified". Stages differ per pipeline. If they mean the lead's status instead ("all qualified leads"), use lead status
qualified. Don't guess the pipeline. - What should each email say? The goal of each step (introduce, give a reason to reply, last nudge) and any facts, offers or links. The AI writes the words. It doesn't invent facts.
- The days. The default is day 0, day 3, day 7.
- The group. The name of a new group, or an existing group to use.
- From which address? One of the business's email accounts.
- Should the follow-ups go by themselves? If yes, the AI also drafts the automation. Ask for the start date, time and time zone of step 1. If no, the person schedules each broadcast.
Steps
1. Leads: the qualified leads
Find the pipeline (lead_pipeline) by name. Note its sk, then find the stage in its stages list by name and note that stage's id.
Find the leads (lead) where pipelineId is the pipeline's sk and stageId is the stage id. If the person asked by status, use status = qualified instead. Page through all of them, because one page holds only a few. Leave out leads with isArchived = true.
For each lead, keep its sk, its name, its email, and its contactId (the contact the lead was linked to when it was made).
Hands on: the list of leads with their email and contactId.
Check: open the board at that stage (/leads?view=pipeline&pipeline=<pipeline sk>&stage=<stage id>). The number of leads on screen matches your list.
2. Customers & Benefits: a contact with an email for each lead
A broadcast mails contacts (customers), not leads. Work through the list:
- The lead has a
contactId. Read that contact (customer). If it has anemail, use it. - No
contactId, but the lead has an email. Find the contact byemail(orusername, which holds the email for most contacts). If one is found, use it, and link the lead by setting the lead'scontactIdto the contact's sk. That update goes through the lead's own service. - No contact found. Don't create one yet. In this app, creating a contact emails that person a welcome message. Collect these leads for the Stop below.
- No email anywhere (not on the lead and not on its contact). Leave the lead out and put it on the left out list.
Stop: if some leads have no contact, show them (name and email) and say: "Making a contact for each of these sends them a welcome email. Shall I create them, or leave them out?" Create them only after a clear yes, with the customer create (email, first name, last name). Then link each lead's contactId.
Hands on: the contacts' sks, every one with an email, and the left out list.
Check: open one or two contacts (/customers-benefits?openId=<sk>) and confirm the email is there.
3. Customers & Benefits: the group
Find the customer group (customer_group) by name. If there isn't one, create it with name, description and groupType static. Not dynamic: a smart group's members are decided by its rules, so these contacts can't be put in it by hand.
Add the members by writing the group's contacts list: its current entries plus the new contact sks, with no duplicates, sent as the whole list. It sends nothing to anyone. (Contacts → Add to Group calls POST /crm/customer-groups/members with { "customerIds": [...], "add": ["<group sk>"] } instead, which writes this list and each contact's groups field together.)
Don't add the group's name to each contact's own groups field for this job. That also counts as membership, but saving a contact emails them that their profile changed.
Hands on: the group's sk.
Check: count the audience with POST broadcast/audience/count and { lists: [<group sk>] }. The count is the members with an email, minus anyone who has unsubscribed, bounced or complained. It should match your contact list, less any already unsubscribed. Open the group (/customers-benefits?view=groups&groupId=<sk>) so the person sees it. The group's drawer does not list members. The audience count and the Recipients tab of a broadcast show them.
4. Message Templates: the three emails
Write the three emails and save each as a message template (messagetemplate):
| Field | Value |
|---|---|
name | e.g. intro-1-day0, intro-2-day3, intro-3-day7. Use 3–50 letters, digits, - or _, unique in the business. |
deliveryType | email |
subject | the subject line |
html | the message |
Personal fields: a broadcast fills in {{firstName}}, {{lastName}}, {{name}}, {{email}} and {{phone}}, and any field the composer's Personalize button inserts ({{data.<namespace>.<field>}}), from each contact's own record. A contact without that field gets it empty, never the braces — so write the greeting so it still reads well blank ("Hi {{firstName}}," reads as "Hi ,"; prefer "Hello," when names may be missing).
A broadcast sends its own copy of the subject and message. It reads a template only when the broadcast names one (templateId) and its own subject or message is empty, and the composer doesn't set that. The templates are the reusable source, so if the wording changes later, change the broadcast too.
Hands on: each template's subject and message.
Check: open each one (/message-template?openId=<sk>) and look at the preview.
5. Email Accounts: the sender
Find the email account (email_account) it should come from. A broadcast can send only from an account that:
- is active (
isActiveis not false); - is not taken out of rotation (
autoRotateis not false); - is not a hosted mailbox. A hosted mailbox can't bulk-send.
Hands on: the account's sk.
Check: the account exists and qualifies. If the business has no such account, the drafts can still be saved, but they can't be sent. The person adds one in Email Accounts (/email-accounts). The AI can't connect a sending account. Say so.
6. Broadcast: three drafts
Create three email_broadcast records, one per step. Saving one is a plain record create, the same write as the composer's Save Draft. Set exactly these fields:
| Field | Value |
|---|---|
name | e.g. "Intro 1 of 3 (day 0)", "Intro 2 of 3 (day 3)", "Intro 3 of 3 (day 7)" |
channel | email |
subject | the step's subject, from its template |
content | the step's message (HTML), from its template |
senderAccounts | [<email account sk>] |
recipientMethod | lists |
selectedLists | [<customer group sk>] |
status | draft |
Never set status to pending or scheduled, and never add a schedule. A sweep every five minutes sends anything pending or due. Never use the list all-contacts or all-leads. Never call POST broadcast/<id>/send.
Hands on: the three broadcasts' sks.
Check: read each one back. status is draft, selectedLists holds the group's sk, and there is no schedule. Open the first one (/broadcast?openId=<sk>).
7. Automation: the timing (only if asked)
Skip this step if the person will schedule each broadcast themselves.
Check list_automations first so you don't make a second copy. Then call create_automation with status: "draft". The tool defaults to active, and an active one would start sending at the start time.
- Trigger:
scheduled_time, config{ schedule: { type: "once", executeAt: "<start, ISO with time zone offset>" }, timezone: "<their time zone>" } - Steps, in order:
- action
send_broadcast, config{ broadcastId: "<step 1 sk>" } - action
delay, config{ duration: 3, unit: "days" } - action
send_broadcast, config{ broadcastId: "<step 2 sk>" } - action
delay, config{ duration: 4, unit: "days" }(day 3 to day 7) - action
send_broadcast, config{ broadcastId: "<step 3 sk>" }
- action
A draft automation has no schedule and never runs. Each wait starts when the previous step has finished sending.
Hands on: the automation's sk.
Check: open it (/automation?openId=<sk>). The status is draft, and the trigger and five steps are in order.
Stop
Sending, scheduling and turning the automation on are the person's decision. Show:
- the three subjects, and the first lines of each message;
- the sender;
- the group and how many people it reaches now;
- the left out list;
- the days, and the start time if there is an automation.
Then the person does one of these:
- Schedules each broadcast in the composer (Settings & Send → Schedule → Add schedule) for day 0, day 3 and day 7.
- Turns the automation on in Automation. Step 1 goes at the start time. If that time has already passed when they turn it on, it will not run, so change the trigger's time first.
If they say "send it" or "turn it on" in chat, repeat the audience count, the sender and the dates, and act only after a clear yes. Bulk email also needs the business's bulk-email agreement. Without it every step fails to send.
Every email gets an unsubscribe link added automatically, so the AI doesn't add one. Anyone who unsubscribes after step 1 is left out of steps 2 and 3.
When it's done
Tell the person:
- the group, its audience count, and how many leads were left out and why (no email, no contact, archived);
- the three drafts' names and subjects, and the sender address;
- whether there is a draft automation, and its start time.
Then say that nothing has been sent or scheduled, and that the three drafts are waiting in Broadcast under draft.
Don'ts
- Don't create contacts without the yes above, because each one gets a welcome email.
- Don't add leads straight to the broadcast by address (
manualEmails). The group is what step 2 and step 3 reuse. - Don't state facts the person didn't give you: prices, offers, dates, meeting links. Leave a clearly marked gap (e.g. [link to book a call]).
- Don't promise per-person timing ("3 days after each lead qualifies"). The platform doesn't do that for broadcasts.


