Vizard Agent

How to check every claim in your voiceover against the product page

Last updated 2026-09-05 · 8 min read

Give Vizard Agent the product page and say the ad may only make claims that page supports. It reads the live copy for the exact price and wording before writing a single line on screen, checks your supplied audio for claims of its own, and flags footage whose embedded text contradicts the page.

What is the short version?

An ad makes claims in three places at once — the narration, the on-screen text and whatever is written on the footage — and only one of them is usually checked. The page is the source of truth for all three.

  1. Go to Vizard Agent with the product page and your footage.
  2. Say the ad may only claim what the page supports.
  3. Ask it to check the footage for text that says otherwise.

What do you need before you start?

The live page, not a copy of the copy. A price pasted into a brief was true when it was pasted; the page is true now, and the difference is what shows up in a screenshot somebody sends you three weeks later.

What do you type into Vizard Agent?

Say the word "verified" and name the source you mean. Without that, the sensible default for Vizard Agent is to write persuasive copy from the product description — which produces good advertising and, occasionally, a claim the page itself does not actually make.

Prompt

Make a 30-second ad for this product: [URL]. Use only claims the product page actually supports — read the live page for the exact price and wording first. Flag anything in my footage or my supplied voiceover that contradicts it.

Variants worth knowing:

What does Vizard Agent actually do?

Here is the order Vizard Agent worked in on a real product ad that had to be built entirely from verified claims. Steps two and three both happen before Vizard Agent writes a single line of copy, which is the whole point of doing it this way.

  1. Checks the product page and the supplied footage together.
  2. Reads the live page copy to verify the exact price and claims.
  3. Checks the page source for a live price or discount before showing an offer.
  4. Checks the supplied audio for spoken content and what it asserts.
  5. Checks the brand mark's appearance so it sits cleanly on the card.
  6. Builds the end card with the verified mark and one clear action.
  7. Checks the caption renderer for readable wrapped subtitles.
  8. Assembles the ad — demos, overlays, the supplied voiceover.
  9. Checks the audio waveform to confirm each section is present.
  10. Re-checks the beat moments so every promised card appears on time.
  11. Uploads for motion, sync and browser-side review.
  12. Checks a flagged source clip to find where conflicting embedded text appears.
  13. Widens and reduces the caption layout so a long phrase wraps cleanly.
  14. Switches to a simpler subtitle style for the long product phrase.
  15. Applies the final visual fixes and holds the offer card through a gap.

Step three is a detail worth copying. A discount is the claim most likely to be stale, and it usually lives in the page's markup rather than in the visible copy — so the offer beat is built from what the page says today rather than from what the brief said last week.

Step twelve is the one nobody plans for. Supplied footage frequently has text burnt into it — an old price, a superseded offer, a different claim — and an ad can be perfectly verified in its narration while contradicting itself in the picture.

What does the result look like?

An ad whose price, offer and every claim in it trace back to the live product page, with any contradicting footage flagged by Vizard Agent rather than quietly included, and captions that wrap properly around the product's own unavoidably long phrases.

The verification is invisible in the finished video. It shows up later, in the questions you do not get asked.

When does this not work well?

The page has to be the authority on the claims, and sometimes it simply is not — a price that varies by region, a claim that lives in a datasheet somewhere else, or an offer that has not gone live yet and so cannot be verified at all.

How do you fix a result that came back wrong?

Say which claim is wrong and where you believe it came from. Vizard Agent keeps its reading of the page, the transcript of your supplied audio and the list of flagged footage, so correcting one claim updates the card and the narration without re-verifying the whole ad.

How does Vizard Agent compare to doing it yourself?

Everyone checks the script before it goes out. Rather fewer people re-check the price on the actual day of delivery, and almost nobody checks whether the supplied b-roll happens to have last season's offer printed across a packshot in the background.

By hand Vizard Agent
The price From the brief Read from the live page
Discounts Assumed current Checked in the page source
Supplied voiceover Trusted Checked for its own claims
Text inside footage Rarely examined Flagged when it conflicts
What is verified The script Everything that makes a claim

Common questions

Does it need the page to be public? Yes, to read it. Otherwise supply the copy and Vizard Agent uses that.

Will it invent benefits? Not if you say verified claims only. Vizard Agent stays inside the page.

What if the page is thin? Then the ad is thin. Vizard Agent will tell you what it could not support.

Can it check my own voiceover? Yes. Vizard Agent transcribes it and checks what it asserts.

What about text in the footage? Vizard Agent checks it. That is where contradictions usually hide.

Can it show the price on screen? Yes. Vizard Agent takes it from the page rather than from your brief.

What if the price changes after delivery? Ask Vizard Agent to re-check and rebuild the offer card.

Does it handle several markets? Yes, as separate cuts. Say which page each uses.

Will it list the claims it used? Yes. Ask Vizard Agent for the list before you approve.

Can it flag a claim I wrote? Yes. Vizard Agent flags anything the page does not support.

Is this legal approval? No. Vizard Agent checks against your page, not against regulation.

What about competitor comparisons? Say so explicitly; they need their own sources.

Can it read a datasheet too? Yes. Point Vizard Agent at every source that holds a claim.

Why read the page rather than the brief? Because the brief was written once and the page is maintained, and the gap between them is exactly where a wrong price lives.