PYLO Settings: Integrations and automations
Sequences
Reminders timed from the webinar or the call, in each person's own time zone, sent by your own tools.
A sequence is a set of reminders timed from something that happens: a registration, the webinar's start, a booking, the call, a no-show or a purchase. Instead of rebuilding hard-coded waits in every tool for every date, PYLO keeps the timing and your tool does the sending. Your agent plans sequences, which needs the Pro plan.
PYLO never sends a message
At each step's time, PYLO adds the person to your own tool in the way that tool starts its automation:
| The tool | What PYLO does | What sends it |
|---|---|---|
| GoHighLevel | Adds a tag to the contact (or sets a contact field) | The GoHighLevel workflow that starts on that tag |
| Brevo, Mailchimp, ActiveCampaign | Adds the contact to a list | The platform's automation that starts on that list |
| Kit | Adds a tag | Kit's automation that starts on that tag |
| A person | Opens an inbox task at the step's time | The person who posts it, for example in a WhatsApp group |
| Calendly | Nothing per person: the step lives in Calendly's own workflow for the event type | Calendly, timed from the booking or the call |
| Close | Subscribes the contact to one of the client's own Close sequences, then reads the subscription back | The Close sequence, from the client's own mailbox |
Each workflow sends straight away, with no wait step, because PYLO already waited. That is why moving a webinar by a day moves every reminder: there are no waits in the tool to rebuild.
Calendly is the exception, for pre-call emails and texts. Calendly holds both the timing and the words, from the booking or from the call's start, so a moved call moves its reminders by itself. PYLO sets the workflow up with each step's timing and approved words, shows who gets what and when, and records no sends for it. A Calendly step can only follow a booking or a call, never a no-show or a webinar.
Close is for a client whose CRM is Close and who has no email platform or GoHighLevel. Their no-show and no-close follow-ups are their own Close sequences, built in Close with their own emails. PYLO never makes or edits a Close sequence. At the step's time it subscribes the lead and reads the subscription back, behind the same parallel mode and hourly limits as every other write. The lead must already be in Close.
Setting one up
Ask your agent, for example "set up the reminders for Thursday's webinar". It uses plan_sequence with a starter, your agency's own template, or a sequence you describe, and changes any step you ask for. The starters are webinar reminders, call reminders, pre-call emails and texts in Calendly (a confirmation at booking, a value email the same day, reminders the day before and an hour before, and a text 15 minutes before), and the no-show and no-close follow-ups (two emails after a missed call, three after a call that did not close, never to someone who has bought). For a Close client with no email platform, the no-show and no-close follow-ups in Close subscribe each lead to the client's own Close sequences; the agent shows you the client's sequences to choose from. The first plan also lists the workflows or automations your tool needs, which the agent builds in your own signed-in browser or leaves for a person, each checked by reading it back.
A sequence messages people, so a person approves it. The code sent to your phone says who it messages, how many people, and the first line of the first message.
Timing
- Offsets. Each step is a time before or after its anchor, for example 1 day before the webinar or 10 minutes after a no-show.
- Time zones. When the person's phone number is from a country with one time zone, the step goes by their clock. Otherwise it goes by the workspace's.
- Quiet hours. By default nothing goes between 21:00 and 08:00. A step that falls inside them moves to 08:00. A reminder before the webinar that would move past its start is skipped instead of sent late. A step marked to go on the minute, such as "we are live", ignores quiet hours.
- Late joiners. Each step has a catch-up rule for people who join after its time has passed: send it now, skip it, or send only the latest missed step. Someone who registers two hours before the start gets the confirmation with the join link at once and only the reminders still ahead of them.
What this page shows
For each sequence: whether it is running, paused, running in shadow or waiting for paused writes, and for each step when it goes, which tool sends it, the next send, and how many people were sent, held in shadow, waiting for a confirm, skipped, suppressed or failed, with the reasons.
Safeguards
- Nothing twice. Each person gets each step once per webinar or call, even if the webinar moves or PYLO restarts.
- Duplicates. Two leads with the same email or phone get one message.
- Suppression. Voided or merged leads, people tagged do not contact, opted out, unsubscribed, bounced or wrong number, and numbers from countries you do not send to are left out. Your tool still applies its own opt-outs.
- Parallel mode. While the workspace runs in parallel, a sequence runs in shadow: it records what it would have done and writes nothing.
- Paused writes. While writes are paused, nothing is added. The sequence carries on when the owner lifts the pause.
- Limits. When more people are due at once than the workspace's limit (25 by default), the step waits until a person confirms the count. Adds are paced within the workspace's hourly limits.
- Stop rule. If too many adds fail on a step, the sequence pauses itself and opens an inbox task.
Pausing
Owners and admins can pause a sequence here, with a reason, and resume it. Pausing stops PYLO adding anyone; nothing already sent is undone. On resume, steps still ahead go at their times and missed ones follow their catch-up rule.