Marketing

Content

The copy your agent drafts in the chat, each version and its checks, who approved it, and where it was pushed.

Your AI agent drafts the copy: emails, SMS, DMs, page sections, the confirmation video and webinar scripts, and ads. It works from your agency's own templates and the client's voice. PYLO keeps every version, checks each one, asks a person to approve it, and puts the approved copy into the client's tools. PYLO never writes the copy itself and never sends it: the tools' own automations do the sending.

Who can open it

Owners, admins and ops. An owner or an admin can approve here.

What each item shows

The copy of the current version, with its subject for an email.
The checks it failed, which stop it being approved until a new version fixes them, and notes worth reading first.
Where approval stands: yours, and the client's for pages, scripts and ads.
Any comments the client left when they asked for changes. Your agent reads them too and saves a new version.
Where each approved version was pushed, and whether reading it back showed the approved words.

The checks

Every draft is checked before anyone approves it:

Merge fields. Each field the template needs is in the copy, and every field in the copy is one PYLO knows. Fields are written like {{first_name}}, and PYLO turns them into each tool's own tags when it pushes.
Tracked links. Every link to a page carries its UTMs, with the funnel and date in the campaign. Paid traffic uses utm_source=paid. Links to WhatsApp groups, calendars and the webinar room are exempt.
Email hygiene. No "free", no words in capitals, no stacked dollar signs or exclamation marks, and no shortened links.
SMS. How many parts the message is, and whether it has opt-out words.
Compliance. Income claims (refused in ads, stories, posts and pages) and your agency's banned words.
Webinar rules. Nothing paid is pitched before the event except the VIP bump, the thank-you video carries no dates, and the presenter link never appears in anything a lead reads.
House style. Only if your agency's template has it: no em-dashes, and none of the phrases that make copy read as machine-written.
The client's voice. Nothing the client would never say.

A draft that holds a key or a password is refused and never stored, and the key is flagged for you to rotate.

Approving

In the chat. Your agent asks for approval of a set of items. PYLO sends a six-digit code to your own phone, email or Slack, with a message naming the set and how many items are in it. Type the code back to your agent to approve the whole set. A code only approves exactly the versions it was sent for.
Here. An owner or an admin presses Approve this version.
The client. For pages, scripts and ads, your agent gets a link for the client. It opens with no login and shows each item, to approve or send back with a comment. Emails and SMS need your approval only.

Saving a new version of an item puts it back to draft: an approval covers exactly the words that were read.

Pushing

When the copy is approved, your agent plans the push. Each line goes the best way PYLO has: Brevo email templates and GoHighLevel custom values by API, the WebinarJam host's reminder emails by its step pack, and a workflow step, a page section or another tool in your own browser, or by a person. You approve the plan like any other. Only approved versions are pushed, and PYLO checks again when the plan applies. A workspace in parallel mode pushes nothing.

Drift

Afterwards your agent can check each tool still holds the approved copy. Where PYLO can read the tool back, it says whether it matches, has been edited in the tool, or is missing. Pushing again puts the approved copy back.

Files and the client's voice

Decks, videos, images and PDFs are recorded where they are, in the client's Drive folder or at a link. The client's voice profile holds their catchphrases, what they would never say and how they come across, built by your agent from the sources you point it to.