Agency OS

Procedures

Your SOPs as steps PYLO can carry out, and where your SOPs disagree as settings.

Read as Markdown

A procedure is an SOP's runnable companion. It lists what the SOP needs, its steps, the checks from its QA list and the failures it guards against. Each step is linked to what does it: one of PYLO's own tools, a capability in a client's tool (by API, a snapshot or your own browser), a draft for you to approve, or a person.

Your SOPs themselves stay yours, on the Resources page. PYLO reads them and never edits them. A procedure refers to an SOP by its number.

Running one

Ask your agent, for example "run the relaunch SOP for Thursday". A procedure that is one of PYLO's own planners runs as it, so running the relaunch SOP makes exactly the plan a webinar relaunch makes. Any other procedure becomes a plan for the steps in the client's tools, a dated launch plan with an owner on every step, and the PYLO calls to make next, in order. Nothing is applied until a person approves each plan. If something the procedure needs is missing, your agent asks for it first.

Coverage

Agency OS, Onboarding, Procedures shows every procedure by folder (onboarding, backend, webinars and sales), how its steps run, and how many are not covered yet. The steps not covered are the backlog.

Your own procedures

PYLO ships generic starters. Your agent can save your agency's own version of any procedure, which replaces the starter for your agency only and keeps every earlier version. A procedure that carries the text of an SOP is refused.

Where the SOPs disagree

When two SOPs say different things, for example how long the booking window is, whether a webinar has a replay, or whether people who missed a form are named in a channel, each disagreement becomes one setting per client. PYLO proposes a default for each and cites both SOPs. Your agency's template carries your choice, made once, and a client can differ through a plan of its own.

Asking the SOPs

Ask your agent "how do we do X" and it answers from the procedures and the client's own SOP documents, quoting each passage with where it comes from.