Listen to your articles and PDFs on your phone, like a radio
A writer, a lawyer, an elected official receives more text than they can read. WeDispatch Radio turns it into a private listening queue: pasted text, an article URL, a PDF, offline.
There is the text you have read, and the pile of the text you will read. A journalist gets wire copy, a lawyer gets briefs, an elected official gets committee reports: documents waiting for a moment at the screen that never comes. The commute, the queue, the morning walk are all free time, but the eyes are busy elsewhere. WeDispatch Radio is built for those moments: a place to drop what you have to read, and listen to it the way you listen to a podcast, played in a row and resumed to the second.
Three ways to add a document
You add pasted text, the URL of an online article, or a PDF file. A sixty-page committee report, an internal memo, the op-ed you want to reread before you answer it: they all come in through the same door. The content is voiced with French text to speech, using the account's voice and settings, and joins a personal listening queue. It is the same engine that voices a site's published articles, put to work for private reading instead. For what actually happens between the written text and what gets spoken, our page on French text to speech sets out the approach.
WeDispatch Radio is a tool for customer accounts, trial accounts included. It is not a consumer app: there is nothing to install from an app store, and listening happens inside the account. What a customer finds there is their own queue, their documents, their articles, their series.
What stays private, and how you can check it
A document added for personal listening must never surface anywhere else. For us that is not a promise but two independent locks, one in the database and one in the file path.
First, a private audio carries a marker in the database, and every public list leaves it out: the podcast feed, the account's public listening page, the daily selection, and above all the integrations. A private document never reaches a CMS through the API, nor through the agent server. When something is uncertain (a database error, an unclear answer), the default answer is "private": a public page that returns a 404 out of caution recovers, a personal document served to a stranger does not.
Second, the file itself lives in a folder whose shape says it is private. A touch-up, a partial re-read or a regeneration reuse that same folder: the file cannot slip back out in public through a side path. And when a customer deletes their account, the wipe lists that folder and finds it, because the marker sits inside the folder, not in front of it. A private document is never emailed either: an account's address belongs to its owner, not necessarily to the person who added the document, and its title is personal.
Knowing the cost before you make it
On a site's automatic path, cost is not a per-item question: the site publishes, WeDispatch voices, the monthly counter is the record. Here you come to make one precise move on one chosen document, and finding out afterwards that it ate into your credits would be an avoidable bad surprise. So before you start, the estimate shows two figures: a likely listening duration and a number of credits. The duration is presented as an estimate, because it is only truly known after synthesis (it depends on the voice, the language, the punctuation). Credits are counted upward: a document that runs one character past the size of a credit starts a second one, and announcing anything else would understate the cost in the direction that hurts the customer. It mirrors how the remaining balance is shown, rounded down for the same reason: never promise what you will not deliver.
A long document becomes several episodes
A sixty-page report is two and a half hours of listening. Nobody listens to that in one block, and an audio has a ceiling anyway. So WeDispatch Radio splits a long document into episodes. When the document has recognisable chapters ("Chapter 3", "Part II", "1. Introduction", a short line in capitals), the split follows them. Otherwise it cuts into slices of about thirty minutes, always at the end of a paragraph, failing that at the end of a sentence, never in the middle of a word. A chapter that runs too long is cut again, chapters that are too short are grouped. Each episode carries the document's title with a marker ("2/5"), and the queue resumes where you left off, episode after episode. Past a dozen episodes the upload is refused: that is no longer a document, it is a book, or an extraction that went wrong.
Who it is really for
The person whose job is to absorb text faster than they can read it sitting down. The reporter who listens to three wires on the way to the morning meeting. The lawyer who picks up a ten-page memo between two appointments. The official who listens to the report before the session instead of skimming it the night before. What they share is not a taste for audio, it is a shortage of screen time. If your public articles already have their audio version, the same engine serves your private documents: it is the natural extension, this time for you, of what your readers already receive.
Give your articles a voice with WeDispatch
This blog is itself voiced by WeDispatch. Curious how it sounds on your content?
Book a demo