Who Receives Platform Notices on an Agency-Managed Account, and How Do You Stay Informed?

Editorial team Spend Ledger

Why notices may reach the agency first

When an agency manages an advertising account, the platform may send notices to the contact details attached to the account, the business or account structure that controls it, or the people with relevant access. Those details may have been entered when the account was created or later changed by the party responsible for administration. If the agency set up the account or handles its day-to-day administration, its staff may therefore be the first people to see policy notices, billing warnings, security messages and review outcomes.

The exact routing depends on the platform’s account structure, contact settings, access permissions and the type of notice. A message about payment may go to a billing contact, while a policy or review message may be sent to an administrative contact or shown inside the account. Some notices may be available only to people who can access a particular part of the account. Email delivery can also be affected by business filters, staff turnover, mailbox rules or outdated contact information.

This does not necessarily mean the client has no rights to receive information. It does mean that access to an advertising account and receipt of its notices are separate operational questions. A client may be able to view campaigns but not control contact settings; an agency may manage billing communications without being the account’s owner. The parties should check the actual arrangement rather than assume that every person with access receives every message.

Identify the account owner and notification contacts

Before relying on an agency to pass on notices, establish who owns or controls the account and which contacts the platform currently recognises. The account’s ownership, administrative access, billing responsibility and campaign management may sit with different parties. Clarify those roles in plain language, including who can change contact details and who is expected to monitor messages.

Where the platform permits it, the client should ask to be added as an appropriate notification contact or given the access needed to review relevant account messages. The right arrangement depends on the platform’s available roles and settings. Do not assume that broad administrative access is necessary just to stay informed: ask whether there is a narrower permission or a separate contact setting that covers the required notices.

Check whether the client’s contact information is current and whether it belongs to a person who will remain responsible for monitoring it. Personal work inboxes can become inaccessible when staff change roles or leave. If the platform does not allow the client to be added directly, agree on a reliable alternative with the agency and document it. In either case, keep access and contact details accurate. Do not use another party’s identity or misrepresent who controls the account.

Use a business-owned shared mailbox

A shared mailbox owned and administered by the client’s business can make notice handling more resilient. It should be controlled by the business rather than tied to an individual employee or to the agency. The business can decide which staff members may read it, maintain access when responsibilities change, and preserve records according to its internal procedures.

If the platform accepts a shared address as a notification contact, confirm that the address is permitted and that the account’s responsible parties can access it. Some services may require a personal contact, restrict the kinds of addresses they accept, or use different contact fields for different purposes. Follow the platform’s own requirements rather than trying to force every message into one mailbox.

A shared mailbox is useful only if someone is assigned to monitor it. Agree who checks incoming messages, how urgent items are escalated internally, and what happens when the regular contact is unavailable. Keep the mailbox secure and limit access to people who need it. A shared address should improve continuity, not become an excuse to share login credentials or weaken account security.

The business should also test the arrangement through normal, permitted account administration—for example, confirming that the contact address is saved correctly and that responsible staff can access the mailbox. Do not ask the platform to send artificial warnings or create account issues as a test. If there is uncertainty about whether a particular notice type will be delivered to the shared address, consult the platform’s official help and policy pages or its support channel.

Put the forwarding agreement in writing

Direct access to notices is preferable where the platform supports it, but it may not cover every message. The client and agency should therefore agree in writing how notices will be shared. A contract or written service schedule can state which categories of communication must be forwarded, who is responsible for checking the agency’s inbox, and how the agency will notify the client when a message requires a response.

The agreement should cover policy notices, billing warnings, review outcomes, account-access or security concerns, and other material changes that could affect campaign activity. It should also describe the communication method the parties will use and identify a backup contact on each side. Avoid relying on informal assurances such as “we will keep you updated” if the account is important to the business. A clear process helps both parties understand what timely reporting means in practice.

Make the handoff useful. The agency should pass on the original message or an accurate copy where permitted, note where it appeared, and explain any action already taken or still required. If the message contains sensitive information, the parties should use an appropriate secure channel. The agency should not edit away important context or present its interpretation as if it were the platform’s decision.

The contract should also address what happens when the agency relationship ends. The parties can specify how outstanding notices, records, account access and contact settings will be handed over, subject to platform rules and the parties’ lawful rights. A written process cannot control how a platform sends messages, but it can clarify each party’s responsibilities for monitoring and sharing them.

Log each notice and the response

A simple notice log gives the client and agency a shared record of what arrived and what happened next. For each item, record the date it was received or discovered, the account or business area it relates to, the type of notice, who received it, and the action taken. Note whether the action is complete, pending, or being handled through the platform’s official process. If there is a response deadline stated by the platform, record it exactly as shown and verify it in the original notice.

Keep the log factual. Distinguish the platform’s wording from the agency’s explanation, and avoid recording speculation as a confirmed reason for a policy decision. Attach or reference the original message when appropriate, while protecting confidential details. If a notice was seen inside an account rather than received by email, record where it was found and who reviewed it.

The log is not a substitute for the platform’s own records or official communications. It is an operational aid that can reveal missed handoffs, repeated account issues and gaps in responsibility. It also helps a new staff member understand what has already been done without relying on scattered conversations or memory.

Agree who maintains the log and where it is stored. The client should retain access even if the agency manages the day-to-day entries. Keep records for as long as needed under the business’s retention practices and any applicable requirements. Do not include passwords, payment credentials or unnecessary personal information in the log.

Set a routine for checking and escalation

A notification arrangement works best when it is part of a routine rather than an occasional request. The client and agency can agree how often they review the shared mailbox, account notifications and notice log, and how they raise an urgent message. The appropriate cadence depends on the account’s activity and the platform’s communication practices; current platform requirements and any stated response windows should be checked on the platform’s own help and policy pages.

Define what counts as urgent for the business. A notice that may affect payment, account access, policy standing or campaign delivery should not sit in an unmonitored inbox while the parties assume someone else is handling it. Set a clear escalation route, including a backup contact if the usual owner is unavailable. Make sure both sides know who can pause or adjust campaigns when a notice requires a decision, while respecting the platform’s rules and the business’s approval process.

Review the routine when staff, agency responsibilities, account ownership or billing arrangements change. Confirm that former contacts no longer receive information they should not access, and that current contacts can still reach the relevant mailbox and account areas. Changes to notification settings should be made through the platform’s legitimate controls, by people authorised to do so.

Respond through official channels and fix the cause

If a notice reports a policy concern, billing problem or review outcome, first read the full message and identify what the platform says is affected. The agency and client should separate immediate containment from the explanation of the issue. For example, they may need to check the relevant account settings, payment information, advertising content or business details, depending on what the notice says. Avoid guessing at a cause or making changes that could create further confusion.

When the notice allows or requires a response, use the platform’s official appeal, review or support channel. Provide accurate information and any documentation the platform requests through its approved process. Do not submit false details, conceal account relationships, create replacement accounts to get around a restriction, or attempt to avoid a verification or review. Those actions can worsen the underlying problem and undermine the record of what happened.

The agency can help the client understand the account history and prepare a clear, factual response, but the business should know what is being submitted on its behalf. Keep a copy of the response and record the submission date and any subsequent outcome. If the platform does not provide a clear next step, consult its official help and policy pages or contact support rather than relying on unofficial workarounds.

Make notice ownership part of account governance

Notices are part of account operations, not merely administrative email. A business that depends on paid advertising needs to know who receives important communications, who can act on them, and how the outcome is recorded. This is especially important when an agency manages the account, because the person operating campaigns may not be the person legally or financially responsible for the business.

Before work begins, confirm account ownership, administrative roles, notification contacts, billing responsibility and the written forwarding process. Establish a business-owned mailbox where appropriate, assign people to monitor it, and maintain a shared notice log. Revisit these arrangements when the relationship or account structure changes.

Clear communication cannot guarantee a particular platform decision or prevent every missed message. It can reduce avoidable confusion, help the client respond through the proper channels, and make agency-managed account work more transparent. The practical goal is straightforward: the platform’s notices should reach someone authorised to act, the client should be kept informed, and each response should address the issue rather than work around the rules.