Too many client emergencies? Set agency response times that protect your team

Find which requests are driving evening and weekend work

Review recent out-of-hours messages with your team. Include email, client chat, personal messages and calls. For each interruption, note what the client needed, the actual consequence of waiting and whether anyone had explicitly agreed to provide cover. Keep this a process review, not an exercise in blaming the person who replied.

Group the requests by cause: a live problem, a late approval, an unclear brief, an agency mistake or work brought forward unexpectedly. Then choose a practical change for each recurring pattern. For example, agree an approval cut-off before a launch, or make the consequences of a late decision explicit in the delivery plan. Ask team members about time spent checking messages as well as time spent doing the work.

• What was affected, and was the impact immediate?
• Was the request inside the agreed scope and support window?
• Who responded, and what work or personal time was displaced?
• What could have prevented the interruption or routed it more appropriately?

Define an emergency separately from a routine request

Write an emergency definition around material, immediate impact within the service you provide. Depending on your remit, proposed examples might include a failed client website you maintain or an active campaign spending against an incorrect setting. Check those examples with each client: do not imply that your agency covers every technical, reputational or business incident.

Separately describe important requests that can wait for the agreed service window. A new creative preference, a progress update or a deadline brought forward should not automatically qualify for emergency handling. Ask the client to describe the impact and available workaround rather than simply choosing an urgent label.

Treat suspected security incidents or other specialist matters separately from ordinary agency support. Agree who the client should contact if the issue falls outside your competence or contract. Do not present your escalation route as a substitute for specialist incident arrangements.

Set response targets that match your staffing

Build your response targets around actual availability, including delivery work, leave and the skills needed to assess a problem. Specify the service days, hours and time zone, and explain when the response clock starts for messages received outside that window. Choose targets only after checking whether someone can realistically meet them without relying on the owner’s evening availability.

Distinguish acknowledgement, assessment and resolution. An acknowledgement confirms receipt; an assessment explains the understood impact and next step; resolution means the problem has been addressed. Avoid presenting an initial response target as a guaranteed fix, particularly where you need client access, approval or help from another supplier.

Use wording you can complete with your real arrangements: “We review routine requests during [service window] and aim to provide an initial response within [agreed target]. We confirm delivery timing after assessing the request. Messages outside that window are reviewed when service resumes unless separately agreed cover applies.” Have a professional adviser review any wording intended to create contractual commitments.

Create one escalation route with clear ownership

Choose an escalation route that your team can actually monitor during agreed cover. It might be a designated phone number or shared inbox, but make the monitoring window explicit. Do not describe an unmonitored inbox as an emergency service, and do not make personal contact details the unofficial fallback.

Name the duty owner internally for each covered period. Give them responsibility for assessing the report, involving the right person and confirming the next update to the client. Define who can authorise pausing activity, changing live work or accepting additional costs. Only name a backup if that person has agreed to be available.

Tell clients what happens if they cannot reach the duty owner. Any fallback should be a separately agreed route or relevant supplier contact, not an assumption that the whole agency is standing by. For requests outside cover, state plainly when your team will next review them.

• Ask for the affected service, page or campaign and a clear description of the impact.
• Request the time the issue was noticed and relevant screenshots, without passwords or unnecessary sensitive information.
• Identify a client contact who can answer questions and approve action.
• Confirm the next update after assessment, even if the resolution time remains uncertain.

Agree out-of-hours cover, fees and recovery time

Offer out-of-hours cover only where you can staff it deliberately. Consider defined launch cover or another limited support window rather than an open-ended availability promise. If you cannot provide dependable cover, say so before the client relies on it and discuss whether a suitable specialist supplier is needed.

Set out what the client is buying: the covered period, eligible incidents, response target, exclusions and authorised contacts. Agree whether the fee pays for reserved availability, work undertaken or both. Make any GBP charges, minimum charges and spending approval arrangements clear before the cover begins; avoid introducing an unexpected emergency fee after doing the work.

Plan the team’s recovery time alongside the cover. Decide what delivery work will move if someone is called out, and who will handle their next commitments. Check GOV.UK or a professional adviser about working time, rest, pay and employment arrangements, and seek advice before changing existing contract terms. This is general operational information, not legal, tax or financial advice.

Introduce boundaries to existing clients and review workload

Start with a conversation rather than a surprise announcement. Explain the service window, response target and emergency route in terms of what the client can expect. The supplied boundary-setting guidance recommends clarifying requirements, maintaining respectful communication and setting clear client boundaries. Apply that approach without presenting your new process as an agreed contract change.

Try this wording: “We’d like to agree a clearer support arrangement so you know where to send requests and when to expect a response. Routine work would stay within our agreed service hours. For qualifying incidents outside those hours, we can discuss separately scheduled cover where capacity allows.” Check existing commitments and seek professional advice where necessary before confirming the change.

After introducing the arrangement, review out-of-hours requests, time spent responding, missed targets and displaced delivery work with the team. Ask clients where the route was unclear. If interruptions remain frequent, revisit the underlying scope, approval process, staffing or support package rather than quietly asking everyone to stay available again.

1. 1Check existing commitments and compare them with actual staffing.
2. 2Discuss proposed service windows and emergency examples with each client.
3. 3Document agreed arrangements and explain them to everyone handling requests.
4. 4Review interruptions and adjust the service deliberately rather than making informal exceptions.

How Capacity planning helps

Use HappyNoodle’s Capacity planning to balance available time against committed work and expected revenue before agreeing client support windows. Review whether a proposed cover arrangement leaves enough room for existing delivery commitments, and account for planned recovery time when considering availability. If the balance looks too tight, narrow the support offer or move other work before making the promise. This supports the staffing decision behind your response targets; keep the emergency definition, escalation route and client agreement documented separately.