Internal comms as audio: what changes when the text must stay inside the company

Inside a company, the texts that matter most are often the ones people read least. The quarterly note from the director, the Friday internal letter, the quality procedure updated for the third time this month: they land in an already crowded inbox, they are long, and most people skim them before moving on. Audio changes that relationship. A text nobody would have read between two meetings gets listened to on the commute, on a walk, while making coffee. This is not a promise of miraculous engagement. It is simply a second channel for content that had only one, and the more demanding of the two.

But internal communication raises a question the press never has to ask. A news article is meant to be public: putting it into audio spreads it a little wider, and that is exactly the point. An internal memo must not leave the company in any form. So the real question is not "does it sound good," it is "where does my text go, and who will be able to hear it."

Where the text goes

This is the first thing to check before handing an internal document to any voice tool, and it is exactly the kind of question we lay out on our French text-to-speech page: a text sent to a synthesis service is processed somewhere, by someone, and you need to know where and for how long.

With us, an internal document goes through WeDispatch Radio, the private listening queue reserved for customer accounts. You add a pasted text, a page address or a PDF, you pay for it with your credits like any other audio, and you listen to it in your own space. The audio that comes out is not published on your site, not placed in your RSS feed, and not reachable through the API. It leads nowhere outside your account.

This is not a pinky promise. It is held by two independent locks, described on the WeDispatch Radio feature page. The first is a marker placed on the document itself: public lists and public pages exclude it, and a page that tried to serve the file by its identifier answers "not found." The second is where the sound file is stored, in a private folder regardless of your account settings. A correction, a partial re-read or a regeneration reuse that same folder, so the file cannot slip back into the public side through a side door. Two locks beat one because they do not rest on the same assumption: if one were set wrong, the other would still hold.

Who can hear it

A public audio is visible to the whole team sharing the account. A private document is not: it is visible only to the person who added it. Not the other team members, not even the account owner. That is a deliberate choice, and it holds up. The letter a leader is drafting for all staff has no business showing up in an assistant's library before it is ready, and the memo a lawyer is listening to in order to proofread it concerns that lawyer alone.

What it costs, shown before you spend

Text-to-speech is billed by volume, and a ten-page internal document is not trivial. So we made sure the cost shows up before any production, not after. The moment you add a document, the screen gives you an estimate in listening time and in credits, never in a character count: "about 24 minutes, 3 credits" means something, "28,000 characters" means nothing to anyone.

The calculation depends on the source. Text you paste is estimated right away, in your browser, with the same rules the server will apply next. An address or a PDF asks the server to read the content in order to measure it, but reading is not producing: at that stage nothing is made and nothing is charged. You see the price, and you decide. Production only starts once you tick the box that states in plain words that the audio will not be published or shared and that you have the right to use this content. Until it is ticked, the button stays inactive.

One practical detail for long documents: past a certain size, the text is split into episodes of about thirty minutes, cut at the end of a paragraph. An annual report becomes a handful of episodes you listen to one after another, like the chapters of an audiobook, rather than a single two-hour file you never open. We go further into this everyday use of the queue in listening to your documents and PDFs like a radio.

In short

Turning internal communication into audio gives a second channel to texts that had only one, a channel that gets used where nobody reads. The single precaution specific to this use case fits in one question: does the text stay inside the company? With private listening, the answer is yes, by construction, and you know the price before you start. If the content you want to voice is not your own, this is the moment to read what we write about copyright and turning a text into audio: the rule is the same for an internal document as for a public article.

Try it on a document you would never have read

Take the last ten-page internal note you skimmed. Add it, look at the estimate, and listen to it on a walk. That is the best test of the channel, and it costs only a few credits.

Read next

• Writing for the ear: what reads well and listens badly
• An accessible audio player: the criteria the player itself has to meet
• Listening to a long text in French TTS: listening fatigue, and what actually helps