Practical guide

Prepare a script for Fliki before importing it

Last materially reviewed 2026-09-24

Quick answerImport a checked spoken script with clear scene intentions; keep reference notes separate from words meant to be narrated.
What to know

Clean the source without stripping its meaning

Remove navigation text, internal comments and drafting instructions from the material that will become narration. Keep the original reference document elsewhere. A generator may not know whether a parenthetical note is an instruction to the editor or something the audience should hear. Mark headings, stage directions and spoken words clearly in your working copy before transferring the approved text into the supported product workflow.

What to know

Resolve numbers and names before synthesis

Decide how the narrator should read dates, decimals, acronyms and product names. Rewrite ambiguous punctuation and long clauses, but keep necessary qualifications. If a source says a feature is available only in one plan, do not simplify it into a universal promise. The writing pass should improve spoken clarity without changing the factual scope. Ask the subject owner about uncertainty instead of allowing a fluent generated line to conceal it.

What to know

Inspect the first scene breakdown

Fliki describes segmenting text into scenes, but an automatic boundary may not match the communication job you intended. Compare the generated structure with your own scene map. Keep a condition beside its instruction and a conclusion beside its supporting evidence. If a visual needs more explanation, revise the script deliberately rather than adding an unrelated sentence merely to fill the duration of a selected stock clip.

What to know

A fictional import check

A support writer imports a passage saying, “Choose Team only if you need shared review.” The review checks that the qualifier remains, that Team is pronounced as intended and that the visual shows a real, current control. A decorative team photograph would not establish the setting. Record the approved wording before generating the rest of the project. This is a proposed editorial check, not a merchant-interface walkthrough or evidence that we executed a paid Fliki production.

Continue when useful

Next: Map a script into scenes without losing its meaning

Give each scene one communication job, while keeping exceptions and supporting evidence attached to the claim they qualify.

Open Map a script into scenes without losing its meaning →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. Fliki text-to-video workflow — Merchant documentation · fliki.ai · Merchant-controlled · checked 2026-09-24
  2. Fliki credit-operation guide, updated 17 September 2026 — Merchant documentation · fliki.ai · Merchant-controlled · checked 2026-09-24