Support

Voice-following uses your browser's speech recognition, which not every browser has. Firefox is the common case. TellyPrompter says so in a line under the script box rather than blocking you, because two of the three scrolling modes still work: it can follow the sound of your voice, or scroll at a steady pace you set.

If your browser does have it and nothing happens, check two things: that the microphone permission is allowed for this site — your browser shows this in the address bar — and that the right microphone is selected under Settings → Devices. A headset plugged in after the page loaded is the usual culprit.

Ear prompting plays your own rehearsal into an earpiece while you perform, and making that read needs your browser's speech recognition, which times the recording to your words. Not every browser has it: Firefox does not, on any device, and some browsers built on Chromium ship without the speech service it relies on. Chrome, Edge and Safari have it, on computers and on phones and tablets alike.

Where it is missing, the Ear prompting control in the Compose header says so rather than disappearing, and opening it says why. Everything else works the same without it: practice, recording, and every scrolling mode.

There is no audio file to find, and that is the answer to the question this entry exists for. When you keep an Ear prompting read, it is stored on the device you recorded it on and plays into your earpiece by itself the next time you press Start take on that script, a beat ahead of you. You do not download it, open it or move it into another app. Signing in syncs your scripts between devices, not your reads: a read stays on the device that recorded it, and on another device the Ear prompting panel says so.

The line under the script box on Compose says the read is ready and, the first time, says the same thing. If you want to check it before a take, press Hear the first line on that panel. A read is made for one version of a script: edit the script and the line says the read is from an earlier version, and Update Ear prompting read replaces it.

No. Start take runs the take itself, on camera when the camera is on, and it does not make an Ear prompting read. The read is a separate recording of your voice, made from Compose: open Ear prompting in the header, press Make Ear prompting read and read the whole script through — your browser asks to use the microphone at that press. Keep it, and it plays into your earpiece by itself the next time you press Start take on that script.

Open App settings from the account control at the top right of Compose or Your scripts, and under Support & feedback press Show the getting-started steps. It asks the two questions again, offers a fresh practice take, and lays out the three first steps: put a script in, Start take, and Make Ear prompting read, which is a separate recording and not the take. Nothing you have saved changes by running it.

It is offered by itself once, on a first visit with no scripts on the device, whether or not you have signed in. If you signed in first, it appears once your account has been checked for scripts kept on another device.

Following stalls when what it hears stops resembling what is written — a skipped line, an ad-lib, a long pause mid-sentence. It is built to find you again on its own, and usually does within a few words.

If it stalls in the same place every time, that is a bug rather than a bad take, and it is worth sending. The lines on either side of where it stopped are enough; you do not need to send the whole script.

Yes, and on the free plan too. Recording is not a paid feature and nothing it produces carries a watermark.

Spoken language does not map cleanly onto written figures — “2024” can be read four different ways, and units are worse. TellyPrompter handles many of these, and the list grows from real recordings that went wrong. If you hit one, send the line exactly as it is written and tell us how you said it aloud. That pair is the whole bug report.

In the app, under your account. Open your account from the header and the Billing section is there: the link into Stripe to manage or cancel a subscription, what happens to your scripts when Pro ends, and how to ask for a refund. The refunds page has the full policy.

Check spam first. Codes are sent from an address that does not accept replies, so replying to that email reaches nobody — write to contact@tellyprompter.com instead, from the address you are trying to sign in with.

You can do it yourself, in the app: open Settings and use Delete account. It removes your account, your cloud library and every earlier version of every script, and it cannot be undone. Scripts held on the device you are using stay where they are.

Export first if you want to keep anything.

The privacy policy answers this properly, table by table, including what leaves the device and what does not. If something in it is unclear, that is worth telling us — an unclear privacy policy is a defect.