Get Manager access to a client's Google Business Profile

Confirm the specific business listing and location the agency is responsible for. Ask the client to identify the account they actually use for the work in scope, rather than choosing from a familiar-looking name. Also agree whether the immediate objective is assessment, configuration or ongoing delivery. These details determine which permission is reasonable and what your team will check afterward. If the client is unsure which asset belongs to the project, resolve that ownership or account-selection question before they approve access to an unrelated account.

The request needs the client account that can manage the intended Business Profile and complete the permitted access action. Send the instructions to that person or ask the client to involve them. A staff member who can read a dashboard may still lack permission to invite an agency. Repeating the same request with the same insufficient role will not fix that distinction. The authorized person should review the requested asset, recipient and permission before proceeding, and retain their own independent access after the agency is added.

The onboarding flow requests Manager, which supports everyday profile work. Owner and Primary owner are outside this request, keeping business ownership with the client. Start by naming the actions the agency must carry out, then match the role to those actions. If the team only needs to inspect Google Business Profile, explain why a viewing role may be sufficient. If a later task requires more authority, make that a deliberate scope decision with the client. Avoid requesting the broadest available role simply to prevent a possible future question; the current engagement should explain the permission being requested.

After the client selects the business, Agency Pilot adds the agency Google login as Manager and connects profile performance. A listing with an access or verification problem needs that issue resolved with Google. Read the status in the context of that workflow. An invitation, a client confirmation and usable Google Business Profile access are related milestones, but they do not always happen at the same moment. Assign responsibility for the next step before marking delivery as ready. This prevents an agency teammate from arriving at a scheduled task and discovering that a required acceptance or platform action is still outstanding.

Use the agency Google login that will manage the Business Profile. Verify it before creating or sending the onboarding request, especially when the agency works through more than one account. Ask the actual recipient to confirm the identity they will sign in with. A forwarded email or a similar display name is not reliable proof that the correct account has been added. For a staffing change, arrange the replacement person’s appropriate access and remove obsolete assignments through the relevant platform process.

After the platform action, check the business name, location and listing identity, then open the profile with the agency login before changing business information. Record who performed that check and whether any required work remains blocked. Prefer a harmless viewing check over an unnecessary live edit. If a teammate cannot reach the asset, compare the actual recipient and role with the original request before asking the client to start again. Completion should mean the right person can reach the intended asset with the agreed capability, rather than only that a message or notification was received.

Profile views, calls, direction requests, website clicks and search keywords support local reporting. These profile interactions should not all be described as completed sales or qualified leads. Keep the client’s reporting expectation explicit in the service brief. If a metric is needed for a report, identify its source, date range and definition before promising that it will appear. A successful access step establishes only the capabilities described for this particular integration. It should not be used as evidence that another platform, a separate dataset or an unrelated source of business results has also been connected.

A missing business usually calls for checking the Google login and listing access. Similar business names or multiple branches make location verification especially important. Start with account identity and authority because those determine what the client can share. Write down the exact stage where the flow stopped rather than repeatedly recreating the same request. If Google Business Profile shows an account-specific restriction, the appropriate platform administrator may need to resolve it first. Avoid broadening permissions or switching to another asset just to make a completion indicator appear; verify the intended account instead.

Confirm the location identity along with the business name. Branches can share a brand while having different phone numbers, addresses or service areas. Map each listing to the relevant client reporting and delivery responsibility before editing anything. When comparing results across locations, retain that mapping so a strong result from one branch is not mistakenly reported as the performance of another.

The link requests Manager rather than Owner or Primary owner. The client should retain control of the business profile and understand which agency login has been added. If an ownership issue already exists, resolve it separately with the appropriate owner and Google. Adding an agency Manager is not an ownership recovery or transfer workflow and should not be described as one.

Agency Pilot’s public-data local tools, including geo grid scans and Business Profile audits, can support prospect research independently of the private reporting connection. Explain which source you are showing. A public ranking observation and the client’s private profile interaction data answer different questions. The ability to inspect public information should not be mistaken for permission to edit the business listing.

No. Profile interactions and recorded business outcomes belong to different parts of the customer journey. Explain the metric shown before presenting it as a lead or a sale. For operational reporting, agree how the client records qualified enquiries and sold work, then use those records alongside profile performance. This makes a local marketing review more useful than treating every visible interaction as revenue.

Establish the source of approved business information and the client contact for unusual situations. Hours, service descriptions and public replies affect what customers expect from the business. The agency’s Manager role enables work but does not supply the client’s approval of a particular statement. Keep a practical escalation path for sensitive reviews and confirm branch-specific information before applying changes across several locations.

Remove the agency Manager in People and access and end the reporting connection. For multi-location work, check every assigned listing or any separate group-level arrangement. Agree a handover point before removing access that is still needed to finish approved work. Confirm the business retains the people and permissions it needs after the agency leaves. Keep permission removal separate from decisions about delivered work or historical reporting data; those are different questions. Record which Google Business Profile assignments were removed and which, if any, remain for an explicitly agreed support period, with a clear owner for the final review.

Confirm the approved hours, contact details and responsibilities for review responses on the selected listing. Establish a reporting baseline using the available profile-performance dates, then use the separate geo grid workflow if the client needs location-based ranking evidence. Keep profile interactions and sold work distinct in the report. For a business with several branches, complete that mapping per location before proposing shared changes so the client can see which evidence supports each local recommendation.