Agree What Happens to Client Work Outside the Agency's Service Hours
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A client sends a message after the agency has closed: “Urgent—can someone handle this tonight?” One person reads it, another starts work, and the account lead learns about the promise the next morning. The problem is not simply the late request. It is that nobody has agreed whether the agency is available, what qualifies for an exception, or who can accept the work.
Set a clear default: requests received outside published service hours enter the next service period unless an authorised person explicitly accepts a defined exception. Give clients one route for requesting that exception, explain whether that route is monitored, and distinguish business impact from the time a message arrives. An urgent label requests a decision; it does not create coverage.
The filled worksheet below shows how to make that agreement usable. It separates receiving a request, deciding whether to accept it, and authorising the work—without implying continuous availability.
1. Define the coverage commitment before defining urgency
Start with what the agency actually provides during its normal service hours. Availability to receive messages is not the same as active monitoring. Monitoring is not acceptance, and acceptance is not completion.
Your agreement should distinguish these states:
- Received: the request has reached the agreed channel.
- Reviewed: someone has assessed its impact, scope and required decision.
- Accepted: an authorised agency representative has confirmed the specific work the agency will undertake.
- Deferred or declined: the request will wait for normal service or cannot be taken on.
Publish the time zone, working days, holiday treatment and channel used for changes to coverage. Avoid relying on phrases such as “normal business hours” when the client and agency may interpret them differently.
Then state what happens outside those hours. If nobody is assigned to monitor a channel, say so. Do not call an unmonitored inbox an emergency desk. A client can be allowed to submit an exception request without being promised that someone will see it before the next service period.
This creates a trade-off worth making explicit: a limited-coverage agency cannot also offer dependable access at any hour. If a client requires continuous coverage, that is a separate service requirement to resolve—not something to conceal behind reassuring wording.
2. Test urgency against the consequence of waiting
The useful question is not “Does the client want this quickly?” It is “What material business consequence will occur before normal service resumes, and what agency action could reduce it?”
Use a short test when reviewing an exception request:
- Current impact: What is happening now, and who or what is affected?
- Consequence of waiting: What changes if the request waits until the next service period?
- Evidence: What observable information supports that assessment?
- Agency relevance: Is the requested action within the agency's agreed work and authority?
- Safe scope: Can a limited action address the immediate concern without creating an uncontrolled new assignment?
A routine request does not become urgent because it was submitted late, copied to senior people or described in capital letters. Equally, a request should not be dismissed solely because the client could have raised it earlier. Present impact and responsibility for late notice are separate questions.
Hypothetical contrast: a client asks on Friday evening for new wording to be ready for an internal review on Monday afternoon. That is normally a scheduling request. By contrast, the client reports that a currently public agency-managed document contains an incorrect commercial offer and asks whether the agency can withdraw it before normal service resumes. That warrants exception assessment because it describes a live business impact and a bounded action. It still does not establish that the agency is available or authorised to act.
3. Filled hypothetical coverage worksheet
Fictional worked example: the following worksheet describes a made-up agency-client arrangement. The hours, roles and decisions are illustrative, not a recommended coverage level for every agency.
Coverage and intake
- Account: Northbank Studio supporting Alder House's client-facing sales materials.
- Normal service hours: Monday to Friday, 09:00–17:30, Europe/London local time. The named time zone governs seasonal clock changes.
- Closures: the agency shares its closure calendar with the client through the account email thread. Closure notices specify the next service opening.
- Routine request route: the shared account email thread. Requests received outside service hours are considered during the next service period alongside existing commitments.
- Exception request route: the same account email thread, marked “Exception requested,” with the impact brief below. Personal messages to individual staff are not an alternative coverage route.
- Monitoring commitment: no routine monitoring outside service hours. The client should not rely on an exception request being read before the next service period.
- Receipt wording: any receipt notice confirms submission only. It does not confirm review, acceptance or work starting.
Urgency and authority
- Candidate for exception review: an active business impact expected to worsen before service resumes, where a specific action within the agency's scope could reduce that impact.
- Normally deferred: new creative requests, preference changes, status enquiries and internal deadlines that do not identify a material consequence of waiting.
- Client authority: the client's named marketing lead may request an exception and approve its scope and any additional charge. A deputy must be named in the account record before acting in that role.
- Agency authority: the account director may accept or decline an exception after confirming that suitable capacity, permissions and client approval exist. Other staff may forward or record the request, but cannot commit the agency.
- Default if no decision is received: the work has not been accepted and remains for the next service period. Silence is not approval.
Accepted exception and closure
- Accepted scope in this hypothetical case: withdraw the identified public sales document from the agency-managed location, once the client's authorised lead approves that action. Replacement copy is excluded.
- Commercial treatment: any additional charge must be agreed before work starts. No charge is inferred merely from submission or review.
- Confirmation: the account director records the accepted action, exclusions, client approver and who will communicate the outcome.
- End of exception: the agency reports whether the accepted action was completed, could not be completed or requires a further decision. Replacement work returns to normal service planning.
- Review trigger: repeated requests of this kind prompt a coverage discussion rather than an assumption that the exception is now standard service.
The worksheet deliberately offers limited coverage. It is useful only if the client understands that limitation and can operate within it. Where that is not workable, change the service arrangement before relying on this document.
4. Give clients an impact brief, not just an urgent label
Ask for enough information to make a decision without demanding a lengthy form during a genuine problem. The brief should identify the consequence of waiting and the requested action, not ask the client to diagnose an internal agency process.
Hypothetical filled client message brief:
Subject: Exception requested — incorrect offer in public sales document
What is happening: The current public sales document includes an offer our commercial lead has confirmed is incorrect.
Business impact before service resumes: Prospective customers can continue viewing that offer while the document remains public.
Evidence and location: The document title, location and affected passage are identified in the existing account thread.
Requested limited action: Assess whether the agency can withdraw that document from the location it manages. We are not requesting replacement copy tonight.
Client approval: I am the named marketing lead and approve withdrawal if the agency accepts the request. Please confirm any additional charge before starting.
Fallback: If the agency cannot accept this, we will assess the actions available within our own control. We understand that this channel is not routinely monitored outside service hours.
Now compare a routine after-hours submission:
Subject: Next service period — sales document wording request
Please review the attached wording changes during normal service. They are for an internal review on Monday afternoon; there is no current public-facing issue. Please advise how this fits with the existing work plan.
The difference is not politeness or seniority. The first message supplies a current impact, a consequence of waiting, an authorised decision-maker and a bounded request. The second supplies a scheduling preference without presenting it as emergency coverage.
5. Make acceptance a separate, explicit decision
Even when an exception request is seen, avoid replying with “We are on it” before someone has authority to make that commitment. That phrase can turn an assessment into an apparent acceptance.
Use wording that matches the actual state:
- Seen, not accepted: “I have seen the request and passed it to the authorised decision-maker. No work has been accepted at this stage.”
- Accepted within limits: “We accept the withdrawal action described in this thread, subject to the recorded approval and agreed charge. This does not include replacement content or additional revisions.”
- Not accepted: “We cannot provide out-of-hours support for this request. It remains for review during the next service period; please do not rely on agency action before then.”
Record the decision in the shared account record, not only in a personal conversation. Include who authorised it and what ends the exception. If a client expands the request, treat that as a new scope decision rather than a natural extension of the original approval.
Do not let the person who happens to notice a notification become the default approver. Visibility, account familiarity and willingness to help are not substitutes for authority.
6. Introduce the agreement without suggesting a service cut
Present the agreement as a way to make decisions predictable, while being honest about any difference from past practice. If staff have regularly responded at night, the client may reasonably believe that support is available then. A new document alone will not reset that expectation.
Discuss the proposed hours and exception route with the client, identify previous informal expectations, and agree when the new arrangement takes effect. Update the account brief and routine onboarding materials so that different contacts do not receive conflicting instructions.
Hypothetical client announcement:
Our agreed service hours are Monday to Friday, 09:00–17:30, Europe/London local time, excluding the closures shared in our account calendar. Requests received outside those hours enter the next service period unless we explicitly accept an exception.
If waiting would create a material business impact, send an exception request in this account thread using the impact brief. The thread is not routinely monitored outside service hours, so submission does not establish availability. Only our account director can confirm acceptance. Any accepted action will have a defined scope and approval record.
Ask the client to confirm who can request and approve exceptions. Also ask whether the stated coverage leaves a business need unresolved. That question is more useful than asking only whether they have read the policy.
7. Recover when someone bypasses the agreement
The first bypass is a test of the process. If a client contacts an individual privately, move the request into the agreed account route and state its current status. Do not require the client to reconstruct the entire message if the agency can preserve it accurately.
If a staff member has already promised work without authority, tell the authorised account lead promptly. Clarify what was promised, whether anything has started and what decision is now needed. Correct the client expectation directly; do not leave the client assuming acceptance while the agency debates responsibility internally.
If an exception grows beyond its approved scope, pause additional work until the expanded request is decided. Report the status of the original action separately so that “still discussing the next step” does not obscure whether the accepted task was completed.
Repeated bypasses may reveal a weak contact route, unclear wording or a genuine mismatch in coverage. Review those causes before treating every occurrence as client misconduct.
8. Test the agreement against the next real requests
Before publishing, have the account lead and client contact classify a routine late request and a request describing active business impact. They should reach the same conclusion about the route, the decision-maker and the default if nobody responds.
Then review the next group of after-hours submissions using a small decision log: submission time, stated impact, route used, authorised decision, accepted scope and final disposition. Measure whether each request had a clear status and whether any work began without recorded acceptance. A low request count alone does not show that the agreement works.
Your next action is to complete the worksheet for one account and ask its named client approver to confirm the coverage limits. If either side cannot explain what happens when an urgent message receives no reply, the agreement is not ready to use.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications