How do I write a UGC ad script?
A UGC ad script specifies what the viewer hears and sees, line by line, through hook, situation, product, demonstration, proof and CTA. Match it to awareness: cold audiences may need the problem explained; retargeting can address an objection or offer. Pair each line with a visual that proves it. Use approved facts and never invent personal experience.
A UGC ad script should specify what the viewer hears and sees. A practical structure is hook, situation, product, mechanism or demonstration, proof, and CTA. The best template depends on buyer awareness: a cold audience may need the problem explained, while retargeting can address an objection or offer directly.
Templates are starting structures. Replace every bracket with real audience language, approved facts, and visual evidence.
Anatomy of a UGC script
Use four columns when writing:
| Time | Spoken line | Visual/shot | On-screen text |
|---|---|---|---|
| 0-3s | Hook | Problem, result, or product action | Short reinforcing phrase |
| 3-8s | Context | Situation or workflow | Who/what this is for |
| 8-20s | Product + proof | Demonstration, UI, or evidence | Key mechanism |
| 20-30s | CTA | Result and next action | Offer or action |
If a line cannot produce a useful visual, rewrite it.
Ecommerce script templates
1. Problem in progress
“If [specific situation] keeps causing [specific problem], watch this.” Show the problem, introduce the product, demonstrate the mechanism, and close with the relevant offer.
2. The routine upgrade
“The one thing I changed in my [routine] was…” Show the product inside the actual routine and name the concrete difference.
3. Live demonstration
“Here is what happens when…” Put the test on screen immediately. Avoid editing that hides the result.
4. Objection
“I thought [objection], but the part I missed was…” Answer with a feature or proof. Do not fabricate personal experience.
5. Honest fit
“This is useful if [fit], but skip it if [non-fit].” Explain the tradeoff and show the product.
6. Comparison
“Here is the difference between [current method] and [product workflow].” Compare supportable characteristics, not insults.
7. Three reasons
Open with the strongest reason, demonstrate each quickly, and avoid padding the list.
SaaS and app script templates
8. Painful workflow
Show the old multi-step process, then the shorter product flow.
9. One-feature proof
“I can go from [input] to [outcome] without [old step].” Show the exact clicks or generated result.
10. Role-based use case
“If you manage [job], this removes [specific task].” Use screens that matter to that role.
11. Feature launch
“You can now [new outcome].” Lead with the user change, not company excitement.
12. Integration
“When [trigger] happens in [tool], [product] automatically [action].” Show the trigger and result.
13. Switching story
Compare workflows accurately and give the reason a specific user might switch.
Service and info-product templates
14. Common mistake
Teach one error, explain its consequence, and show the mechanism the offer provides.
15. Mini-tutorial
Deliver a useful step before introducing the paid next action.
16. Myth and correction
Correct a specific misconception with evidence. Avoid manufacturing controversy.
17. Method preview
Show the first part of a real framework and who it is designed for.
18. FAQ
Answer a purchase-blocking question plainly, then point to the detailed page.
19. Proof-led explanation
Open with a verified result or demonstration and explain what caused it. State the source and limitations.
20. Retargeting reminder
Address the likely unresolved question after a product or pricing-page visit. Keep the promise and landing page aligned.
Turn one script into a useful test
Keep the body, proof, offer, audience, and landing page constant. Create three hooks with materially different entry points: problem, outcome, and demonstration. Name the hypothesis before generating.
UGC script QA
- Would a real person say this naturally?
- Does the visual prove the spoken claim?
- Is any personal experience invented?
- Is the product introduced soon enough?
- Can a muted viewer follow the ad?
- Is the CTA specific and accurate?
Turn a template into a complete physical-product script
Here is a fictional example using the live-demonstration template for a storage bag with a labeled front pocket. The product behavior is an assumption for this writing exercise, not a claim about a real brand. Before production, verify the actual product and replace the example details with approved facts.
| Spoken line | What the viewer sees | Why this beat belongs |
|---|---|---|
| Looking for the cable at the bottom of your bag? | A hand searches among several loose items | Establishes the specific situation |
| This front pocket keeps it separate | The cable is placed in the actual pocket | Shows the feature behind the argument |
| The label faces out when you open the bag | A close-up shows the label in the real orientation | Makes the claimed convenience visible |
| Check the pocket size for your own accessories | Accurate dimensions appear beside the pocket | Defines fit without claiming universal compatibility |
| See the layout on the product page | Product shot and the same destination promise | Gives the viewer a concrete next step |
Notice that the script does not require a presenter to say they use the product every day. It can be delivered as a brand demonstration. If a real customer contributes their own experience, preserve what they actually said and review any changes to meaning or context.
A complete software script from the workflow template
For a second fictional example, imagine a scheduling tool that displays an approved availability link. This is a proposed script structure; it does not establish that any particular tool has the described feature.
| Spoken line | Visual or recording needed |
|---|---|
| Still sending several messages to choose a meeting time? | A staged message exchange labeled as an illustration |
| Start with the availability you want to share | Current product screen showing the actual selection step |
| Then send this link | The real generated link and its destination |
| Your guest sees those available times | The guest view, with private information removed |
| Watch the full scheduling walkthrough | End card pointing to a matching demonstration page |
The script needs the product-owner-approved recording before final approval. If the flow requires account setup, payment or another material condition, explain it in the appropriate part of the ad and destination. Do not make a complicated process appear effortless by silently omitting the step that changes the buyer's understanding.
Rewrite lines that ask the viewer to take your word for it
Replace broad praise with the specific action or evidence the product can support. Instead of calling the storage bag revolutionary, show the front pocket and explain what it holds. Instead of promising that the scheduling tool saves hours, demonstrate the actual sharing process. A concrete line gives the editor something to show and the reviewer something to check.
Use a three-part editing pass. First, underline every factual promise, including implied comparisons. Second, attach the source or demonstration that supports it. Third, remove or qualify the lines that the source cannot establish. Do the same for visual implications: a sped-up sequence or an unrealistic transformation can add a claim that never appears in the spoken script.
Keep personal-experience language attached to the actual speaker. Phrases such as I switched, I noticed and my results describe a history, not just a tone of voice. If there is no genuine history behind them, rewrite the line as a product explanation rather than directing a performer to sound more believable.
Make hook variants connect to the same body
For the storage-bag example, a problem opening can show the search for a cable; a demonstration opening can show the pocket immediately; a fit opening can ask whether the viewer wants small accessories separated. All three can lead into the same product explanation if the transition is written deliberately.
Read each variant from its opening through the first shared body line. Remove repeated information and repair missing context. A hook that introduces a travel problem cannot simply flow into a body written entirely for a desk drawer unless the use case genuinely matches. Keeping a body constant is useful only when the resulting ad still makes sense.
Name the variant by its argument, not by an arbitrary number alone. Store the complete approved script beside the final file so the campaign team can match the result to the actual words and footage. A label such as cable-search opening tells the next writer more than version seven.
Hand the script to production with clear boundaries
Mark exact product language, mandatory disclosures and the CTA as required. Mark conversational phrasing and optional gestures separately. Ask the creator or presenter to flag lines that feel unnatural before recording, then review the proposed revision for meaning. This preserves a usable performance without turning improvisation into unapproved claims.
Include references for the difficult shots, pronunciation notes and any product handling constraints. Have the reviewer compare the final captions and voiceover with the approved script, because an accurate recording can still acquire an error during editing. Close the handoff by assigning the person who will consolidate feedback and approve the final version.
Write once, create multiple formats
Knowlify offers end-to-end Meta ads, connecting scripts and creative production with campaign management. Creative-only support is available when you already have a media team. Bring product evidence and prior campaign questions so the next script has a clear job. Media spend is separate from service fees. Explore AI UGC production and video ad production, or plan your Meta ads.
Primary-source check
Scripts that include endorsements or creator relationships should follow the FTC's current endorsement guidance.
Related video marketing guides
Continue with AI UGC ads, TikTok UGC ads, or our AI video ads.
FAQ
Should a UGC script be word for word?
Write the required facts, proof and disclosures precisely. Decide with the creator which conversational phrasing can change, and review the final take for meaning as well as tone.
Can an AI presenter read a customer testimonial?
Do not use an AI presenter to invent a customer experience. If a campaign uses an actual testimonial, confirm permission, accuracy and how the presentation could be understood before production.
How many hooks should one script have?
Choose a manageable set tied to distinct hypotheses. Keep the body consistent when testing openings, and label each version so results can be matched to the intended change.
How do you write a UGC script for a new product with no reviews?
Build the argument around what can be shown or otherwise substantiated: product actions, specifications, a real workflow or the founder's accurate explanation. Avoid writing a testimonial-shaped story without a genuine speaker behind it. A demonstration can make the offer understandable while the team collects legitimate customer feedback for future concepts.
Should the script include camera directions and captions?
Yes, when they are necessary to communicate or prove the message. Pair each important line with its visual, and identify exact on-screen wording for claims, qualifications and the CTA. Leave room for the creator's natural delivery where the meaning can stay the same. Review the final edit because captions, crops and cuts can change the original script's meaning.