Ember

The Ember Codex

The Unscoped Channel: Why Between-Session Access Burns Coaches Out

Coaches try to cap the volume of between-session messages. The receipts point at scope instead: no written job for the channel, no reply clock, no out-of-bounds list.

Handy Gunawan · · about 4 min to read

Between-session burnout on Voxer or WhatsApp comes from scope, not volume. A coach prices the channel, picks the app, and never writes down what the channel is for, how fast a reply comes, or what belongs somewhere else. That is an unscoped channel.

I went looking for who had written the job of the channel down. On 26 September 2026 the US top ten for “voxer for coaching clients” gave me five pages on how to offer it, price it or replace it: Luisa Zhou, Coaches & Company, Paperbell, EntrepreneursHQ, ClarityFlow. Useful pages, all of them. None of their titles says what the channel is for.

Zero Reddit results ranked in that ten, which is the part that bothers me, because r/ADHD has a 139-point, 152-comment argument running about daily messaging access with a professional, and none of it reaches the page a coach reads before pricing the thing.

Why does an unscoped channel burn a coach out?

What arrives in it runs past what most coaches trained for. Sibley and colleagues surveyed 481 ADHD coaches for JAMA Network Open in January 2026 and found 89.3% with no professional mental-health background, and the International Coaching Federation’s 2024 Snapshot Survey put 85% of the coaches already working on such issues hearing growing calls for mental well-being support, and 44% referring clients to medical professionals.

Clients are guessing at the same line from their side. Under that r/ADHD thread, on a therapist who texted daily, one commenter wrote: “It’s possible her therapist has a system like this set up and the boundaries aren’t very clear.”

I build software for coaches, so read the next part as an interested party talking.

How do you scope a between-session channel?

Write three things down before the channel opens, and keep them where the client can read them again.

  1. The job. What the channel is for, in one sentence. Not “anything you need”, which is where the trouble starts, but something a client can act on at 11pm: the day the plan stopped fitting, or what got done.
  2. The clock. The hours you read messages, and the longest wait a client should expect. Left unstated, the clock defaults to always.
  3. The out-of-bounds list. What goes to a session, to a prescriber, or to a crisis line instead. The ICF number above is why this line exists, since 44% of coaches are already making those referrals.

A scoped prompt gets answered, and the answer is the work, because ADHD takes away what a person already knows at the moment it matters. The decay date asks one thing: which day the plan stopped fitting. The honest zero gives a client a way to report a week where nothing moved without lying about it.

Access is sold from $65 to $397 a month, and at the top of that range what a client should get is a channel with a written job. Price it however you like, and write the job down first.

Questions people ask next?

Is between-session messaging part of ADHD coaching, or an add-on?

It is standard equipment in the coach writing I have gathered: paid intake, weekly sessions for eight to twenty-four weeks, check-ins between, then a deliberate taper. Those coaches also say the results happen between sessions, which makes the channel the delivery. That is their claim, not a trial finding.

How much does between-session access cost?

Coach packages in the corpus behind this piece run from $65 to $397 a month, with a named Voxer pass at the top end. Paperbell, Luisa Zhou and EntrepreneursHQ all publish packaging guides. None of them prices the scope, which is the part that decides whether a coach can keep going.

What if a client messages every day?

Daily contact happens, and it is not itself the trouble; the question is whether what arrives matches the job the channel was given. Where no job was written, the client cannot send the right thing, and both people end up calling a scope problem a boundary problem.

The Ember Codex is written by Handy, who builds Ember, a session-report builder for coaches.

Start free →