PYLO Messaging
Broadcasts
One text, email or WhatsApp template to a tag, a pipeline stage, custom fields, a saved view or an uploaded list, now or at a set time.
A broadcast sends one message to many contacts at once: the doors-open text before a webinar, a replay email, or a reminder to everyone in a pipeline stage. Every message in it passes the same checks as a workflow's, so do not disturb, consent, quiet hours and the daily limits all still apply.
Who gets it
Pick one way to choose the audience:
- Tag. Leads with any of the tags you name, or only leads with every one of them.
- Pipeline stage. Leads sitting in one stage of a pipeline.
- Custom fields. Leads whose fields match the filters you add, such as a country or a budget.
- Saved view. Everyone in one of your saved views when you send. A team view whose owner is "me" changes with whoever opens it, so it names no one in a broadcast: use a view that names its owners, or your own copy.
- Uploaded list. A CSV with a header row and an email or a phone column. Rows that match a lead use the lead. If the people on the list agreed to get texts or WhatsApp messages from you, tick the box and paste the words they agreed to. PYLO records that consent against each number, with your name and the time.
You can narrow any of these with custom field filters, and leave out leads with a tag. The tag boxes offer the tags your workspace already uses.
A message you send to many leads from Views arrives here as a draft holding exactly those leads, so it gets the same preview and the same confirm as any broadcast.
Before it goes
The panel on the right counts again a moment after every change:
- How many people get it, and how many are left out and why: no phone or email, do not disturb, no consent on file, a bounced address, or a WhatsApp marketing template to a US number.
- How long it takes. Texts and WhatsApp go within each channel's daily limit, so a big audience can take more than one day. The estimate says how many days and when it should finish.
- What it costs, when the workspace sends on PYLO's numbers. The credits for the whole broadcast are held when it starts and released as each message settles. If the balance does not cover it, PYLO says so before anything goes.
- The count to type. Above the workspace's send guard limit, you type the number of people to confirm it, the same as any large send in PYLO.
When
- Send now, or Schedule for a date and time.
- Texts and WhatsApp messages always go between set hours, no earlier than 8am and no later than 9pm. For an email, Only send between set hours is on by default and can be turned off. The default is 8am to 8pm. The hours are read in each contact's own time zone, worked out from their phone number, or in the workspace's time zone if you prefer. A message that falls outside the hours waits for the next morning.
Testing subject lines
An email broadcast can test two or three subject lines. Choose how much of the audience the test goes to, how long to wait, and whether the winner is picked by opens or by clicks. When the time is up, PYLO sends the winning subject to everyone else, and the broadcast's page shows each variant's figures and which one won.
While it sends
Each broadcast has its own page with its state, the figures as rates with both of their counts (delivered, opened, clicked, replied, bounced, unsubscribed, opted out) and every recipient with what happened to them.
- Pause stops new messages going, and Resume carries on from where it stopped.
- Cancel stops the rest for good. Messages already sent are not taken back.
- Duplicate copies it into a new draft.
If the opt-out or complaint rate climbs during a send, PYLO stops the broadcast and tells the team.
Replies land in Conversations like any other message, tagged with the broadcast.
From Claude
Claude can read broadcasts and plan one with plan_broadcast. A planned broadcast is never sent by Claude: a person approves it with apply_plan, and the count they approve has to still be the audience when it goes.