Every client account, one link

Start with the assets the agency needs to deliver the agreed service. A local SEO engagement may need Business Profile and Search Console access, while paid media work may need advertising and analytics accounts. The integration directory shows how each supported connection works. It also distinguishes client access from tools connected for the agency’s own operations, such as billing or communications.

Read the access method, available role, and reporting coverage separately. A provider can support a guided invitation without supplying the same reporting data as another integration. Likewise, an account connection does not imply that Agency Pilot edits every object inside the provider. The individual integration pages describe those boundaries so you can set a request the client understands.

Automatic access uses a provider-supported flow to add or invite the agency at the selected role. Guided access gives the client the steps and agency details required to complete the task in the provider’s interface. Both belong in an onboarding plan, but they should not be described as identical. Allow time for the authorised account owner to perform the guided steps.

After the request, verify that the intended account or property was selected and that the agency can perform the agreed task. If the wrong person connects, they may see no assets or only a subset of the expected ones. Resolve that ownership or permission issue with the client instead of requesting broader access than the work needs. A clear account inventory prevents repeated guesswork.

For each requested platform, record the asset the agency expects to use. A Google Analytics property, a Search Console property, a Business Profile location, and a Meta ad account are different objects even when they belong to the same business. Ask the client to confirm the authorised identity for each. Match the request to the role choices documented on that integration page. This makes selection easier and prevents a broad list of familiar provider names from concealing uncertainty about the actual accounts.

Explain the completion process in the client’s terms. An automatic invitation may still require attention to the correct recipient, while a guided step requires action in the provider interface. Make clear who should notify the agency when a step is done and who will verify it. When the connection becomes part of reporting, check the selected asset again before interpreting the first result. Keep the inventory current as accounts or staff change. At offboarding, use the same list to review provider permissions separately from Agency Pilot connections. A well-maintained inventory gives the integration directory a practical role throughout the engagement, rather than treating it as a setup page that is never revisited.

Before moving a workflow into a new system, identify the information it needs. Account identifiers, campaign results, customer contact details, and recordings have different uses and different audiences. Share only what is needed for the task. An example used in training can often use fictional names or a demonstration account instead of a real customer's personal details. If you are preparing a support request, describe the problem first and remove passwords, access tokens, and unrelated records from screenshots or attachments.

Review the published privacy and security information alongside your own client commitments. Ask for clarification where a requirement is not answered, such as a procurement questionnaire or a specific processing arrangement. Do not assume that a feature description establishes a certification, a legal conclusion, or a custom contract term. When an engagement ends, review both the application connection and any permissions granted directly in third-party platforms. Those are separate places where access may exist. Keeping a clear inventory makes the offboarding conversation more concrete and helps the client understand which actions are theirs to complete.

Choose a client with a clearly identified account owner and a small set of representative platforms. Include an automatic flow and, if your service uses one, a guided flow. Before sending the link, record the expected asset and role for each. Watch whether the client understands the request and can select the correct account. Do not rush past a missing asset or ambiguous identity just to finish the trial. Those are precisely the situations an onboarding process needs to handle clearly before delivery begins.

After completion, ask the specialist who will use the account to verify access. Separately check the reporting coverage documented for that provider; an invitation alone does not establish that every metric will appear. Record what worked, what required provider-side action, and who will maintain the connection. Finally, rehearse the explanation of offboarding: which connection belongs to Agency Pilot and which permission lives directly with the provider. You do not need to disconnect a working client unnecessarily to understand that distinction. The outcome of this pilot should be a reusable access checklist with clear ownership, rather than a generic declaration that all integrations work the same way. Expand only when the team can repeat the verified process.