Service Levels for an Agency Account: Response Times and Escalation Paths in Plain Words

Editorial team Spend Ledger

What a service level means

A service level is a written description of how an agency and its client will handle communication and support. It explains who receives questions, what kind of response to expect, how urgent issues are identified, and what happens when the usual contact is unavailable or does not reply within the agreed window.

It is not a promise that an advertising platform will approve an account, resolve a review, restore access, or act by a particular time. The agency can describe its own process and the support it controls; it cannot control a platform’s decisions, response times, checks, or availability. A useful agreement makes that boundary clear.

The purpose is to replace vague expectations such as “we are always available” with practical terms both sides can follow. Those terms should fit the scope of the work, the agency’s staffing, and the client’s operating needs. If the arrangement does not include continuous monitoring, the writing should not imply that it does.

A service level also helps make account management more predictable. When an agency account is used to run a client’s advertising, the parties need to know who can make decisions, who can report a problem, and how an issue moves from the day-to-day contact to someone with authority to act.

Decide who handles ordinary questions

The agreement should identify a role or team as the first point of contact for routine matters. That may cover questions about campaign setup, changes already within the agreed scope, reporting, billing administration, or the status of work in progress. The agreement need not rely on a particular person’s name; role-based wording is easier to maintain when staffing changes.

State where ordinary questions should be sent, using the communication channel the parties have agreed to use. Clarify whether a message sent elsewhere is considered received for service-level purposes. This prevents confusion when a client sends the same request through several channels and assumes that each one is being monitored.

Describe what an ordinary reply means. It might be an acknowledgment that the request has arrived, a clarification question, a status update, or a substantive answer. These are not interchangeable. An acknowledgment confirms receipt but does not mean that the requested change has been completed or that a decision has been made.

The agreement should also explain what the client needs to provide. A question may require account context, a description of the affected campaign, or relevant platform notices. The client should share information through appropriate channels and avoid sending passwords, authentication codes, or sensitive identity documents in ordinary correspondence. Any verification or account review should be handled through the platform’s official process.

Describe response windows without overpromising

A response window is the period in which the agency aims to acknowledge or address a message. It should say whether the agency is describing an acknowledgment or a substantive response. It should also state when the window applies: for example, during the agency’s stated working hours, rather than at all times.

Avoid words such as “immediately,” “always,” or “guaranteed” unless the agency can genuinely support them and the agreement defines exactly what they mean. Even then, avoid implying that the agency can control platform processing. A more honest description distinguishes the agency’s response from the time needed to investigate, make an approved change, or receive a platform decision.

The service description should cover both ordinary and urgent matters in plain language. For ordinary questions, say that the agency aims to respond within the agreed business-hours window. For urgent matters, specify a separate response window only if the agency has a real process and staffing to support it. If the agency cannot monitor messages outside working hours, say so directly.

Define how the response window is measured. Clarify which time zone applies, whether non-working days are excluded, and what happens when a message arrives outside the stated coverage period. Use the agency’s published working schedule rather than leaving “business hours” open to interpretation. If coverage changes, the parties should record the revised arrangement in writing.

The service level should distinguish response from resolution. An agency may acknowledge a concern promptly while still needing time to examine it, obtain client approval, or follow a platform’s process. A stated response window should never be presented as a deadline for a platform outcome.

Define urgency by impact, not anxiety

“Urgent” should describe a situation that needs prompt attention because of its operational impact, not simply a message marked urgent. The agreement can give examples relevant to the arrangement: loss of access to an account needed for active work, an unexpected restriction affecting delivery, a suspected unauthorized change, or a material issue that requires a time-sensitive client decision.

Examples should not be treated as an exhaustive list unless the parties intend that. The client should explain what is affected, when it was noticed, and what action has already been taken. The agency should be able to ask for more information before classifying the issue, especially where the available details do not establish the level of impact.

Some situations may be important but not urgent under the agreed service level. A request for a new campaign, a routine performance question, or a change that can wait for the next working period may belong in the ordinary queue. Clear categories help prevent genuine incidents from being lost among routine requests, while avoiding the expectation that every message receives emergency handling.

Urgent does not mean that the agency should bypass platform policies, checks, limits, or verification. It means that the agency follows its internal escalation process and helps the client understand the appropriate next step. If the issue concerns a platform decision or account review, use the platform’s official appeal or support channels and address the underlying cause.

Set an escalation path

An escalation path shows how a concern moves to someone who can review it or make a decision if the usual contact is unavailable, the issue is unresolved, or the impact changes. It should be specific enough to use, but not so elaborate that the client has to guess which route applies.

A practical path identifies the day-to-day contact, the next responsible agency role, and the person or function responsible for account-level or contractual decisions. The client should know how to reach the next level and what information to include. The agency should also say whether the client is expected to wait for a response from the first contact before escalating an urgent issue.

The path should include a fallback for absence or staff changes. A shared team inbox or designated backup role may work better than relying on one individual. The agreement can state that the agency will tell the client when the primary contact changes and provide the appropriate replacement channel.

A short clause to adapt might read:

> The client sends routine questions to the agency’s designated day-to-day contact through the agreed channel. The agency aims to acknowledge routine messages within the response window stated in this agreement during its published working hours. For an urgent matter, the client uses the agreed urgent channel and describes the affected account, the operational impact, and any relevant platform notice. If the day-to-day contact is unavailable or the urgent matter remains unacknowledged within the agreed urgent response window, the client may contact the agency’s designated escalation role. Contractual or account-level decisions are referred to the agency’s responsible decision-maker. The agency will record the issue and provide a status update when it has meaningful information. Platform reviews and decisions remain subject to the platform’s own processes.

The parties should replace general phrases such as “agreed channel,” “response window,” and “designated role” with their actual arrangements before relying on the clause. Do not leave operational details implicit.

Record missed expectations and follow through

A service level is useful only if both sides can tell whether it was followed. Keep a simple record of the date and channel of a request, its category, the time it was acknowledged, the next action, and whether the matter was resolved or remains open. Record relevant context without collecting unnecessary personal information.

When an expected response window is missed, note that fact neutrally. The record should distinguish between a late acknowledgment, a delayed substantive answer, and a matter that remains unresolved because the agency is waiting for information or a platform response. This makes it easier to identify a communication failure without misrepresenting a platform delay as agency inaction.

The next step should be practical: notify the agreed escalation contact, request a status update, or review whether the matter was correctly categorized. Repeated missed expectations may indicate that the coverage arrangement, staffing, or agreed channel needs revision. The parties can discuss a change and record it in writing rather than allowing informal expectations to accumulate.

Avoid treating every missed target as proof of misconduct or as an automatic entitlement to a particular outcome. The agreement should say what happens when service expectations are not met, such as a review meeting or a written corrective plan, if those remedies are appropriate to the arrangement. Any remedy should be explicit and mutually understood.

Keep platform responsibilities separate

Agency support and platform support are different. The agency can explain what it has done, help organize information, and guide the client toward the platform’s official support or appeal route. It cannot promise how quickly the platform will respond or what decision it will make.

If access is restricted, an ad is rejected, or an account is subject to verification or review, the service-level clause should not suggest workarounds. Do not create replacement accounts to evade a restriction, conceal relationships between accounts, or submit inaccurate information. Follow the platform’s rules and provide truthful information through its official channels.

The agreement should also clarify who is responsible for client approvals, access administration, payment arrangements, and the accuracy of materials or claims supplied for advertising. These responsibilities affect how quickly the agency can act. If a required approval or piece of information is missing, the agency should communicate what is needed and explain that work may be paused until it is provided.

Review the arrangement as the work changes

A service level that fits a small, defined scope may not fit a larger or more time-sensitive operation. Review it when the account structure, campaign workload, operating schedule, or contact responsibilities change. The purpose is not to imply that more coverage will produce better advertising outcomes; it is to ensure that the communication process matches the work actually being done.

Before agreeing, check that the wording answers practical questions: who receives routine messages, what counts as urgent, when the response window applies, what an acknowledgment means, who handles escalation, and how missed expectations are documented. Confirm that the agency can support the coverage it describes.

Keep the final terms in the written agency arrangement, along with any operational details needed to use them. If the platform’s current rules, support routes, or account requirements matter to a specific issue, consult the platform’s own help and policy pages. A clear service level sets expectations for communication; it does not replace platform rules or guarantee an account outcome.