Resume where you left off: the small thing that decides whether an article gets finished by ear
An interrupted listener does not come back to the start, they do not come back at all. What the player remembers from one session to the next (position and speed), why it moves your listen-through rate, and what it does not do.
Listening is rarely done in one sitting. You start an article on the train, get off halfway through, reopen the page that evening. The question that decides everything comes at that exact moment: does playback pick up where it stopped, or does it start again from the first sentence? The answer looks like a detail. It is not. A listener made to sit through the first four minutes they already know does not listen to them again: they quit. And an article quit on resume is an article that will never be finished, whatever the quality of the voice reading it.
What the player remembers, and where
The WeDispatch audio player remembers two things from one session to the next, on the same article and in the same browser: the position reached, and the chosen speed. In practice, someone who listened up to the sixth minute finds the cursor at the sixth minute when they reopen the page, and someone who usually listens at 1.25 times normal speed does not have to set that slider on every article. These settings live on the listener's device, not in an account: they have nothing to create, nothing to connect, and nothing they do flows back to a profile. It is a convenience on the player side, not a tracking device. The trade-off of that choice has to be said plainly: resume holds for a given browser. Someone who starts on their phone and reopens on their computer does not find their position carried from one device to the other, because nothing links the two without an account, and an account has no place here, for ordinary readers.
Why this detail weighs on listen-through
The figure that matters to a newsroom is not the number of plays started, it is the share of articles listened to the end, or at least far into. That is where resume acts, quietly but really. Without it, every interruption is a chance to lose the listener for good: reopening an article means landing back at the start, so having to redo a path already walked, so giving up. With it, the interruption is just a pause: you pick up the thread in an instant. Long articles, the very ones that gain the most from existing as audio, are the ones most often interrupted, and so the ones for which resume changes the most. If you already track your listening metrics, it is precisely in the listen-through depth of long formats that the effect shows.
Comfort that asks for no special setup
The good news is that none of this needs configuring. Resume and speed memory are in the player by default, whatever way you dropped it in: the WordPress plugin, a line of script, or one of the variants we supply for you to copy into your own build. This behaviour is part of what the player does, just like highlighting the text being read or the bar that stays visible as you scroll the article. A technical team rebuilding its own rendering from our render toolkit inherits the same resume, and we check that the web, iOS and Android versions pick up at the same place: a mobile player that resumed differently from the web would be a defect nobody reports and everybody feels.
The right level of expectation
Resume should not be sold for what it is not. It does not sync a listening library across your devices, it does not rebuild a history, it does not know who you are. It does one thing, and it does it without anyone thinking about it: it avoids punishing the listener for having been interrupted. It is a deliberate choice of restraint, in the same line as the rest of the tool: we prefer a simple mechanism that works everywhere, with no account and no personal data, to a promise of sync that would force every reader to identify themselves. To judge the effect, there is only one honest method: start an article, pause it midway, close the tab, come back. What you see at that moment, a cursor waiting for you or a reading starting over, is what your readers will live, several times per article.
Give your articles a voice with WeDispatch
This blog is itself voiced by WeDispatch. Curious how it sounds on your content?
Book a demo