Working inside a client organisation
ProfilePilot Team | Sep 16, 2026 | 9 min read
Select a client in the header, connect channels correctly, run Reputation / Locations / Social Inbox, and understand Insights Connect vs paid Insights Platform tiers.
Step 1: Select the client before you work
- Use the header client switcher to select the client org.
- Confirm the name in the header matches the brand you intend to change.
- Only then open Locations, Reputation, Posts, Reports, Settings → Integrations, or Insights.
Wrong org context is the most common cause of “0 locations”, empty reviews, or pages attaching to the wrong tenant.
Step 2: Connect Google and Meta for that client
Google Business Profile
- Start Connect with the client selected.
- Use a Google account that already has access to the client’s locations (the client usually grants the agency in Google first).
- Callbacks write against the org in context.
Meta (Facebook / Instagram)
- Connect/Refresh with the client selected.
- If you see 0 / N in token, pages are already owned by another org and were skipped — ProfilePilot does not steal pages.
WhatsApp (when the client has Commerce/Auth)
- Each client needs its own WABA credentials. Do not reuse lab/env tokens across clients.
Step 3: Run day-to-day modules
With the client selected and entitled:
- Locations — listings, accuracy, photos, hours
- Reputation — reviews, red flags, Customer Satisfaction, reply SLAs
- Social Inbox (`/dashboard/comments`) — Facebook/Instagram comments (not the same as Meta page “reviews”)
- Posts / Campaigns — publishing queue and calendar
- Reports — Combined Export and chapter PDFs (agency branding applies when configured)
Product walls still apply: if the client lacks Reputation or Insights, you hit the same upgrade surfaces a client user would.
Step 4: Insights — Connect is free; Platform is paid
Do not confuse the two:
| Capability | Commercial | | --- | --- | | GA4 / Google Ads / Search Console Connect (Settings → Integrations) | Free — connecting GA does not require Insights entitlement | | Insights Platform (`/dashboard/insights` and paid modules) | Paid DIY / DIWM / DIFM (`PLN_insights_*`) — entitled per client org |
Agency overview Insights KPIs only roll up entitled clients. Opening `/dashboard/insights` for a client without Insights entitlement shows the upgrade path — not a broken Google token error.
Combined / Insights PDF chapters use the signed-in user’s access path for that client org.
Quick Tasks
- ✓Select the client in the header switcher first
- ✓Connect Google/Meta only with that client selected
- ✓Use Reputation, Locations, and Social Inbox as entitled
- ✓Treat GA/Ads/GSC Connect as free; Insights Platform as paid DIY/DIWM/DIFM
Keep learning
See the latest guides, experiments, and rollouts.