PYLO Home and My Board
Launch
Launch plans, with what's left before each launch, who owns it, and whether it is really done.
Launch holds a workspace's launch plans. A launch plan is a checklist dated back from a launch day: every item has an owner, a due day, what it waits on and, where PYLO can read it, a check that proves it. Owners, admins and ops can open it, and it sits beside Setup in the sidebar.
Planning a launch
An owner or admin chooses a template and the launch day under Plan a launch. PYLO ships three templates:
| Template | For |
|---|---|
| Webinar relaunch | Running a webinar again: new session, links, SMS workflow, registrant coverage |
| Base44 partner launch | A Base44 partner: keys, build library, student portal, EOD questions, first proof |
| VSL with dialer | A VSL funnel with setters dialing: page, dialer, bookings, speed to lead |
An agency can keep its own templates in its blueprint, and they stay private to that agency.
Planning works like every other change PYLO makes. Plan it shows the plan under Settings, Plans, and nothing is written until you approve it there. Planning again with a new launch day moves every due day and keeps what is already ticked. Nothing is ever deleted.
Reading a plan
A plan opens on Blocking launch: the items launch waits on that are not done, the overdue ones first. The other views are Overdue, By owner and Everything, and each has its own address, so you can share one.
Each item is Open, Claimed or Done:
- An item with a check is done when its check passes, whoever ticked it.
- Ticked while its check fails, it is claimed, and it stays open until the check passes.
- An item whose check PYLO cannot read (such as which number an SMS workflow sends from) is done when a person ticks it, and says it was ticked by hand.
- An item with no check is done when it is ticked.
PYLO reads the checks every time the plan opens and again when you tick an item.
The checks
| Check | What PYLO reads |
|---|---|
| Access given | Every item on the client's access checklist is verified |
| Bookings arriving | A booking tool is receiving bookings and PYLO refused none |
| Dialer calls arriving | Close is sending the dialer's calls |
| Test lead passed | The latest test lead landed every leg it tried |
| Link audit clean | The latest link audit for the launch's webinar found no stale link |
| Registrant coverage | At least 98% of the webinar's registrants are covered in the SMS platform |
| EOD questions | The setters' EOD asks for Base44 dials, pickups and activations |
| First build proof | A student has sent proof of a build |
Agents
An agent reads a plan with get_launch_plan, asks what is holding a launch up with list_blocking_items, and plans one with plan_launch, which an owner or admin then approves.
Common questions
Why is my ticked item still open? Its check does not pass yet. The item says what PYLO read, so you can see what is left.
Why does a check say PYLO cannot read it yet? The part of PYLO it reads is not switched on for your workspace yet. Until it is, a person's tick counts.