Fullscreen Teleprompter

For support teams and customer service

Teleprompter for customer support

A teleprompter for customer support turns a written answer into a video people watch to the end. Support teams answer the same questions every day, and the answers depend on exact wording: the product name, the menu path, the number of the setting. A prompter scrolls the approved text at the pace you speak, so the video says exactly what the documentation says, and you can retake one paragraph instead of the whole clip. You can record the answer once and reuse it for the article, the ticket reply and the internal guide. It runs in the browser with no account, the script stays on your own device and nothing is uploaded.

What a teleprompter for customer support changes

A support article is read by somebody who is stuck and tired. A support video is watched by the same person, who does not want to read at all and wants the screen to show where to click. That makes video useful for the answers that involve a sequence of steps, where a paragraph of text is easy to misread and a person pointing at the interface is not.

The problem with video in a support team is drift. Two agents record the same answer a month apart, the product has been renamed in between, and now the help centre has two videos that contradict each other. A prompter fixes that by making the text the source: what the product team wrote is what gets read.

  • The wording of the video matches the article it sits next to.
  • The customer sees the exact menu path, read at the same pace every time.
  • A change to the interface means re-recording one paragraph, not one video.
  • Every agent can produce the same answer without rewording it.
  • The script for an unreleased feature stays on your own device.

The prompter does not record the camera and does not export video. You keep your own camera, your own microphone and your own editing software.

The structure of a short support answer

A support answer that works has 4 parts, in this order: what the customer is trying to do, where to click, what they will see, and what to do if it did not work. Four paragraphs, one idea each. The customer can stop watching at any point and still have the whole answer, because nothing depends on a line they missed.

Length matters more than people expect. A 60 second answer is about 140 words at 140 words per minute, and 90 seconds is about 210 words. Write to that limit: a support video that runs to 5 minutes is not watched to the end, and the part that was useful is usually in the first minute.

  • Paragraph 1: the problem in one sentence.
  • Paragraph 2: the menu path, read slowly.
  • Paragraph 3: what the customer sees on the screen.
  • Paragraph 4: the next step, or what to do if it failed.
  • One paragraph per step, so you can re-record only the step that changed.

Reading a canned answer and giving a useful one

A canned answer read word for word is fast to produce and easy to ignore. The customer can tell that the person is reading, and a video that sounds read does not build trust in the product. The fix is not to improvise, which is worse, it is to write a script that already sounds like an explanation.

Write the answer as you would say it to a colleague: short sentences, second person, no legal wording, no internal code names. Then read it out loud and mark the places where you would normally pause for the customer to follow along. A prompter lets you slow down exactly there and speed up in the parts that do not need attention.

  • Say 'you' and name the button as it appears on the screen.
  • Remove the internal name of the feature and use the customer name.
  • Read the menu path at 120 words per minute, the explanation at 140.
  • Keep one instruction per sentence, so it can be followed with a screenshot.
  • Read the whole answer out loud before you record, once.

Keeping product names and steps exact

In support, a wrong word is a ticket. A feature called Sync in the documentation and Sync now in the marketing page sends the customer looking for a button that is not there. The names, the capitalisation and the order of the steps have to be read exactly as they are written, and that is what a script guarantees.

Put every product name in its own paragraph when it matters, so you can read that line at 110 words per minute and be certain of it. Keep the numbered steps in the script as they appear in the interface, with the numbers written out. When the interface changes, the change is one paragraph and one re-recording.

  • Copy the names from the documentation, do not retype them from memory.
  • Read the product name and the menu path at 110 words per minute.
  • Number the steps in the script, in the same order as the interface.
  • Check the spelling of the button labels with the release notes.
  • Re-record the paragraph with the name, not the whole video.

Making several versions of the same answer

The same question arrives in different shapes. A customer on a phone cannot follow a menu path on a desktop, and a customer on a trial version does not have the setting that paying customers have. One answer cannot cover all of them, and three separate scripts drift apart within a month.

Keep the shared part and vary the part that differs. The introduction and the closing can be the same paragraph in every version, and only the step that changes is rewritten. The prompter holds up to 10 scripts, so the versions of the most asked question sit side by side, and you can export them as .txt or .md to hand to the team.

  • One script per audience: desktop, mobile, trial, enterprise.
  • Keep the shared introduction in the same paragraph in all of them.
  • Read the version that fits the screen the customer is on.
  • Export the set as .txt or .md when the product team changes a feature.
  • Use the same reading speed in all versions of the same answer.

Internal how-to videos for support agents

New agents need the same answer to 40 tickets a day, and a written policy does not get read under pressure. A short internal video that goes through a refund, a billing dispute or a data export request gives the agent the wording and the order of the steps, in the time it takes to watch 90 seconds.

These videos are also the easiest to keep current, because they are small. A 90 second clip is about 210 words at 140 words per minute, so it fits in a single paragraph per step. When the refund window changes from 30 days to 60 days, you edit one paragraph, read that paragraph again and the rest of the video is untouched.

  • One paragraph per step of the procedure, in the order the agent must do it.
  • Number the steps in the script so a new agent can follow them on screen.
  • Keep the legal wording in the paragraph that contains it, and read it slowly.
  • Record it once per policy change instead of explaining it in 12 calls.
  • Store the internal script separately from the customer facing one.

Keyboard shortcuts while you record

These shortcuts work with the prompter open, so the person on camera never touches the mouse during a take.

Keyboard shortcuts What it does
Space Play or pause the scroll
Up / Down Slower or faster, in words per minute
Left / Right Previous or next paragraph
R Back to the top of the script
+ and - Bigger or smaller text
F Enter or leave fullscreen
Esc Leave the prompter and go back to the editor

A Bluetooth controller or a presentation remote sends the same keys, which is useful when the screen is across the room from the person reading.

References and tools

Official documentation, for the recording side and for the general idea of a prompter.

Frequently asked questions

Is a teleprompter useful for customer support videos?
Yes, when the answer depends on exact words. Support answers carry product names, menu paths and steps, and those are the details a customer checks against the screen in front of them. A prompter reads the approved text at a steady pace, and it lets the agent re-record one paragraph when a step changes.
How long should a support answer video be?
Write to about 140 words for 60 seconds at 140 words per minute, and about 210 words for 90 seconds. Support videos work when they answer one question and stop. If the answer needs more than 4 paragraphs, it is probably two answers, and it is better to publish both.
How do I stop the video sounding like a read script?
Write the answer as you would say it to a colleague, with short sentences and no internal code names, then read it out loud before you record. In the prompter, slow down to 120 words per minute on the menu path and return to 140 for the explanation. A script that sounds written is the problem, not the prompter.
Can I record several versions of the same answer?
Yes, and it is the normal way to work. Keep the shared introduction in the same paragraph in every version and change only the part that differs, such as the mobile path or the trial version limit. The prompter holds up to 10 scripts, and you can export them as .txt or .md to send to the team.
Is our support script uploaded to a server?
No. The prompter runs in the browser and keeps the scripts in the local storage of your own device. There is no account, no cloud and no watermark, and the only thing that leaves the device is anonymous usage data. A script about an unreleased feature or a customer case stays on your machine until you publish the video.

Open the teleprompter for your next support video

Open the teleprompter, paste the approved answer and press start. The words scroll at the pace you speak, you can retake a single paragraph and nothing is uploaded.

Open the teleprompter

Support this project

If you'd like to support the project, take a look at these beautiful illustrated products. I'm also a fantasy illustrator, and you can support me by buying prints. I'm sure you'll find something special for you, for a friend or for family.