Between-Session Messaging Rules for Coaches

Between-session messaging rules for coaches explain what a client can send, what the coach will do with it and when the reply is due. They distinguish the freedom to leave a note from a promise of continuous attention. “Message anytime” does not tell a client whether an answer will arrive before tomorrow's decision.

A useful agreement covers the channel, scope, response clock, submission allowance, receiving work, time off and review. The complete fictional case below includes a late coach reply, actual coaching content, a client clarification, a recipient's counterproposal and the work each person really does.

Coachful is our #1 recommendation for organizing these agreed conversations and follow-through. This is our editorial recommendation for the workflow, not an external market ranking, a guarantee of rapid answers or a substitute for agreeing a service that fits the client.

Choose the service before choosing the notification settings

Messaging can support preparing a question, reflecting after a session or reviewing one small experiment. It can also become a separate substantial service. Decide which you offer. A short note allowance cannot honestly stand for unlimited document review, live negotiation or ongoing emergency monitoring.

Describe the work the coach promises. An automated receipt, a clarifying question and a completed coaching response are different events. The agreement should say which is due by the stated deadline and what happens when missing information prevents a complete answer.

The ICF Code of Ethics, with a current cover revised May 2026, supports clear responsibilities, financial and confidentiality arrangements, appropriate boundaries and attention to changing value. It does not prescribe a universal message allowance or reply schedule. The arrangements here are original practical examples to adapt together.

Match the promise to the client's real work. A person who routinely needs a Tuesday-morning decision cannot plan around a Wednesday reply. Discovering that mismatch before purchase is useful. A written boundary is not automatically a suitable boundary for every service.

1. Name the primary channel and a usable exception

Choose where the coaching conversation belongs and explain why. Keeping the agreed context together can make review easier. A personal social message, a group community post and an individual client conversation have different audiences; they are not interchangeable inboxes.

Provide a way to report being locked out of the primary channel. Otherwise the rule requires the client to enter a service they cannot access before asking for help accessing it. Name the actual administrative contact, its owner and its response arrangement. Do not make that address an undisclosed second coaching channel.

State who may read the conversation. A private client conversation is not a public group, but a practice still needs clear handling and authorized staff arrangements. Adding a covering coach requires attention to access, confidentiality and agreement, not merely forwarding a thread.

Keep unnecessary third-party details out. In the UK, the ICO's data-minimisation guidance connects adequacy, relevance and necessity to the stated purpose. It does not impose our example word limit. Ask for enough context to coach responsibly without collecting a whole personnel file when a short nonidentifying account would do.

2. Define a clock the client can reproduce

State review days, cutoff time, named time zone and response deadline. Say whether a message arriving exactly at the cutoff belongs to that window or the next. Avoid a phrase such as “twenty-four business hours” unless you also explain how those hours accumulate.

An original example is: messages received strictly before 12:00 Europe/London on Monday, Wednesday or Friday receive the agreed response by 17:00 that day. At 12:00 or later on a review day, or at any time on a non-review day, the deadline is 17:00 on the next actual review day after applying notified leave and holiday exceptions. “Europe/London” follows the local clock through seasonal changes; it is not a promise of a fixed year-round UTC offset.

Test representative situations together. A Friday 11:59 submission and a Friday 12:00 submission have different deadlines. Publish holiday and leave exceptions and explain how they change those examples. A client should not need to infer the next review from the coach's online indicator.

If missing information requires a clarification, the coach should identify the actual gap and the next response process. An empty acknowledgment is not equivalent to a useful answer. If you miss the deadline, name the miss, its practical effect and the actual next step rather than silently moving the original due time.

3. Define the unit of support and its completion

“One message” can mean one bubble, one question, one recording or a whole exchange. Choose a service unit people can use. One focused issue with one related clarification is different from one initial note followed by unlimited amendments.

Explain which week owns the submission and whether unused allowance carries forward. Also specify how a permitted clarification sent the next week is counted. Otherwise a Friday question can unexpectedly consume the next week's entire allowance, or quietly create unlimited unfinished issues.

A length limit helps describe the work but does not measure all of it. Reading two hundred words about a familiar question may take less effort than understanding a short note with a complex attachment. Say whether attachments, research, document review and multiple topics are included.

Offer an appropriate alternative when a format is unsuitable. A longer agreed text, an accessible document or a live session may be useful. Obtain an agreement before changing the service or charging for additional work. Do not label the person difficult because their question does not fit a short recording.

4. Explain exceptions without quietly changing the promise

An early reply can be helpful. You do not need to delay it to train independence. Explain that it does not guarantee the next early reply. If frequent immediate exchanges become the real service, review whether the written description still represents what people reasonably rely on.

Likewise, a message sent outside the primary channel may need a courteous redirection rather than a full coaching response. Check whether there was an access problem or a reasonable misunderstanding. A rule should organize professional judgment, not justify ignoring an important safety concern.

Asynchronous coaching is not continuously monitored emergency care. A person needing immediate medical or safety assistance should use the appropriate local emergency or professional route rather than wait for this inbox. A workplace security incident, legal deadline or employment decision may also need its authorized professional route. The coach does not acquire that authority by receiving a message.

Avoid speculative claims that quick replies necessarily cause psychological dependency or that a particular delay regulates a client's nervous system. The practical reasons for an availability limit are sufficient: scope, responsible review, capacity and the service actually sold.

5. Reserve time for the complete exchange

Include reading, contextual thinking, drafting, sending, notes and clarification. Listening to a two-minute recording is only one part of reviewing it. Count the client's receiving work too when designing an activity they are supposed to fit into a short break.

For a separate illustrative capacity model, six clients each use twelve coach minutes for an initial review and eight for the included clarification. Maximum modeled demand is 6 × 20 = 120 minutes. Three forty-five-minute review blocks supply 135, leaving fifteen. Orientation and service-review meetings require their own separately reserved time; they are not hidden inside this model.

These assumptions need testing. If the average initial review takes sixteen rather than twelve minutes while clarification remains eight, demand becomes 144 minutes, nine beyond the blocks. Do not keep advertising the same capacity while moving the extra work into evenings.

HSE's Demands standard concerns employee workload and achievable demands within agreed hours. That is a relevant workplace principle, not validation of this independent coaching schedule or proof that batching improves health. Measure actual work and revise the promise when needed.

Complete the fictional March messaging agreement

Every person, date, institution and result in this example is fictional. Anika coaches Joel, who volunteers with a museum newsletter. They already have a finite March 2051 messaging service, without automatic renewal. The record below makes its operating terms explicit; it is not a complete legal contract or a universal recommended allowance.

During orientation, Joel initially thinks Friday noon would mean a Friday answer. Anika checks the exact boundary: 11:59 is due that day; 12:00 is due Monday, absent a notified exception. Joel repeats the distinction correctly. They also check the 17 March leave example before any question is submitted.

Run the actual exchange, including the late answer

Receive the initial question and retain the missed deadline

On Friday 10 March at 11:40, Joel sends this focused question, within the allowance:

I want to offer a short access note for the museum newsletter, but I do not want to commit to editing the whole issue. I can give forty-five active minutes next Tuesday. I need the current approved access facts before I write. How can I make the offer and the limits clear? I planned to prepare my request between 17:00 and 17:30 today.

The agreed reply is due at 17:00 that Friday. Anika's earlier work overruns and she fails to answer by then. Joel cannot use her answer in the planned half-hour preparation window. That is a lost opportunity, not thirty minutes of active writing counted in his ledger.

Anika replies at 18:10, seventy minutes late. She apologizes for missing the promise rather than calling the message a next-window submission. Her substantive response is:

Separate your offer from an agreement already made. State the maximum time, the one note you are offering and the facts you need before starting. Ask the recipient to confirm the arrangement rather than assuming silence means yes. Who has authority to approve the wording? If that is not the person receiving your request, make that approval dependency explicit. My late reply missed the preparation period you named; this answer does not restore that time.

This was an answer with a specific clarifying question, not merely a receipt. It still missed the original deadline. Joel reads it later and does not pretend he completed the Friday preparation he intended.

Return the clarification and a complete usable response

On Monday 13 March at 11:20, Joel uses his one related clarification:

Tessa has final newsletter approval. She can supply the current approved public visitor guide; I need her to identify the right version. My contribution would be up to eighty words, not editing other articles. I still have forty-five active minutes available on Tuesday.

It belongs to the original week's issue and is sent within seven days of the first answer. Anika replies Monday at 16:40, within that day's 17:00 deadline. She proposes checking the facts and the recipient's acceptance before committing, and returns this complete draft for Joel to adapt:

Tessa, I can draft an access note of up to eighty words within forty-five active minutes on Tuesday 14 March. Could you provide the current approved access facts by Tuesday 12:00 and confirm that you own final approval? This offer does not include editing other articles. If the needed facts or time are unavailable, I will not commit the draft. Please reply by Monday 13 March, 18:00.

Joel reads the reply, decides the draft fits his intention and sends that request at 16:55. No third coach response, new topic or additional purchase is claimed. Anika has completed the two responses included for this issue.

Obtain the recipient's actual decision and finish the bounded work

Tessa replies at 17:20 that she has final newsletter approval but cannot supply the facts by Tuesday noon. She can provide them by Wednesday 15 March at 12:00. Joel checks his availability and proposes Wednesday 14:00–14:45 instead. Tessa explicitly accepts that time and the one-note scope at 17:40.

On Wednesday at 11:35, Tessa supplies the approved public guide and identifies the access facts for the draft. Joel uses the agreed 14:00–14:45 period: five minutes reading, thirty drafting, five checking and five sending and recording the status. The period is forty-five minutes of contribution work, not forty-five minutes of pure writing.

His complete fictional note stays within the agreed eighty-word limit:

Access details for the spring gallery evening: use the level South Entrance from Cedar Walk. The main exhibition and accessible toilet are on the ground floor. Ask the front desk if you need seating or help finding the quiet room. You can contact the venue before visiting to discuss access needs. These details describe the current visitor guide; please check with the venue if you need information not covered here.

On 16 March Tessa acknowledges receiving the draft and says final approval is still pending. Joel reads that reply and retains the pending status. The case does not claim publication, verified access for every visitor or final approval merely because the text was sent.

Review the service without rewriting its result

At the fifteen-minute 20 March process review, Joel says the Monday response was useful but that the Friday miss mattered. He often needs Friday evening preparation time, so he decides not to buy April messaging. Anika accepts that choice. They do not retrospectively turn the March promise into an acknowledgment-only service.

The review uses their existing messages and draft record within the fifteen minutes; no extra uncounted pre-reading or closing email exchange is added. March support remains available on its agreed terms through 31 March. Any later submission, review or end-of-month closure is outside the observed case.

The result is mixed. The second response met its deadline and the client obtained a real counterproposal and delivered the bounded draft. The first response was late, the lost work window was not restored, the newsletter remained unapproved and April continuation was declined.

Count actual effort and response performance separately

Total actual effort is 182 person-minutes against 210, leaving twenty-eight. The six-client weekly capacity illustration is a separate model, not this whole case's budget. The case includes orientation, actual recipient work and the process review; it excludes future March service and later newsletter approval.

One of two coach responses was on time. Reporting only the Monday success would hide the missed Friday deadline. A corrected outcome and a fulfilled response promise require different evidence, as do an accepted contribution window and a published newsletter.

Put the agreement into practice in Coachful

1. Make the same channel, allowance and clock visible in the agreed service information and orientation. A notification setting or an online indicator is not a contractual reply promise.
2. Use the individual client conversation for the agreed private work. The message icon on the client's profile opens that conversation. State the actual authorized audience rather than assuming all private records share the same visibility.
3. Use personal notification controls deliberately. The conversation's notification settings can reduce alerts; muting does not close the service or prevent the client sending a message. Keep your own review schedule and deadline record.
4. Deliver feedback through the client-facing route. Coach review under an opened worksheet submission is private to the coach team and is not the answer the client has been promised.
5. Record chosen follow-through without overstating it. A task does not prove a recipient accepted the request. Check recap controls separately: automatic sending is the default, approval holds new unsent recaps, session-type overrides matter and changing the setting cannot recall a recap already sent.

The Coachful features support these conversations; the agreement's allowance and clock here are human service commitments, not claimed automatic message blocking or deadline enforcement. Unshared journal pages also differ from pages the client explicitly shares. See the voice-retainer guide for a different service format and the informed-consent guide for the wider agreement conversation.

Troubleshoot an agreement that people cannot use

The client sends several topics. Identify the priority and agree what happens to the rest before additional work. Do not silently answer everything and then issue an unexpected bill.

Your quick replies became the expectation. Review the actual pattern and what was sold. Repeating a footnote may not address reliance created by your routine behavior.

The deadline falls during leave. Use the published exception and next actual date. If the exception was not communicated or conflicts with the original promise, address that gap directly.

A message needs another professional. Explain the relevant scope and appropriate route. Receiving a confidential account does not authorize taking an employment, legal or clinical decision.

Frequently asked questions

Can clients send outside review hours?

If the agreed channel permits it, yes. Explain when it will be reviewed. Permission to submit is different from a promise to read immediately.

Must every service include a clarification?

No. State the actual unit and completion rule. If clarification is included, count its work and explain how it affects the allowance and deadline.

Can I occasionally answer earlier?

Yes, when appropriate. Keep the normal planning promise clear and review the service if exceptions become its ordinary operation.

Does muting stop client messages?

It controls notifications rather than ending the service. Continue the agreed review process or formally address a needed change.

What if the client needs faster support?

Explore an actually available suitable model, a relevant professional route or an appropriate ending. Do not promise a faster service you cannot deliver.