Scripts vs PPV: choose the right FanvueAutomation workflow
Understand Scripts, locked Vault media and PPV products. Review prices, pacing, positive-reply requirements and refusal cooldowns before rollout.
Choose the workflow, not the label
A Script is a sequence of message steps. A PPV product defines a paid offer. A Script can include a locked PPV step, but that does not mean the step selects a PPV product. This distinction matters when you are choosing media and reviewing settings. Neither workflow guarantees a purchase.
Start with the correct account and media
Select the creator account you intend to configure. Check the relevant files in Vaults before opening either workflow. The Scripts interface and the PPV product interface both depend on Vault media. If a file is missing, check the account, filters and sync result before uploading another copy. A locally uploaded file is not by itself proof that paid delivery through Fanvue is ready.
Use Scripts to arrange a sequence
In Scripts, review the message steps in their intended order. The editor provides a Message template, Wait minutes and Approx. messages before next step. The wait control describes a minimum time after a step before the next can send; it is not a guaranteed delivery time. Message pacing describes how much fan conversation should happen before moving on. Avoid promising an exact schedule from those controls alone.
Choose paid media inside the Script step
For a locked PPV offer, the editor provides Locked Vault media and a price. Its help text explicitly distinguishes this media from a PPV product. Select the actual files intended for that step rather than searching for a product entry. Review the positive-reply requirement and relevant follow-up settings before activating a sequence. Creating a price does not establish that a fan has agreed to buy.
Use a PPV product to define an offer
The PPV product editor asks for media, Description (for AI) and Price (USD). Describe the selected content accurately so the offer does not promise something absent from the files. The optional Description (for user) is a separate field. Review any enabled first-offer discount settings instead of assuming every fan receives the same price. Check the final configured amounts before enabling the offer.
Check pacing and refusal handling separately
The PPV editor exposes a cooldown per conversation and a cooldown after refusal or a price objection. These are separate controls. The backend also checks the offer cooldown and refusal interval. A permitted offer is not a guaranteed send or sale: other eligibility and runtime conditions may apply. For Scripts, review the sequence controls rather than assuming PPV product settings govern every paid Script step.
Review before rollout
- Account and files: confirm the creator and inspect the intended Vault media.
- Offer: compare the description with those files and review the price and any discount.
- Sequence: check step order, minimum waits and positive-reply requirements.
- Repeat contact: review cooldowns, refusal handling and after-purchase behaviour.
Check the account, selected files, descriptions, prices, step order, pacing and relevant guards. Keep a record of what you changed. If you have an authorised write-capable test workspace, test using fictional data and inspect what actually happens. An interface review alone cannot prove a completed delivery or purchase. After rollout, use recorded sends and purchases to evaluate the workflow rather than invented conversion expectations.
A simple way to choose
For a planned opener, qualification message and paid-media step, start by reviewing a Script. For a named paid offer with its own content description, price and offer settings, review a PPV product in PPV Campaigns. The similar wording does not make their media selectors interchangeable.
For example, imagine a fictional studio photoset. A Script can introduce its theme and then reference those Vault files in a paid step. A PPV product can describe the same approved files as an offer. Review each configuration independently; creating one does not prove the other has been configured. This is an illustrative setup, not an observed sale.
This guide was checked against deployed interface source and a read-only staging interface on 21 September 2026. No delivery or purchase test was performed. FanvueAutomation is an independent third-party tool, not affiliated with or endorsed by Fanvue.