A sample client you can show on a sales call
Every partner now has a seeded demo client with seven months of realistic campaign history, built for sales calls and never counted among your real clients. Approvals also stopped appearing for pages a client cannot see.
Most of today was about what a partner shows someone who has not signed yet, and about making the places a client clicks agree with each other. A few of the changes underneath were about our own agents learning to finish an investigation instead of handing it off.
For our partners
- A Sample account under Settings > Client Portal gives you a fictional client, in your niche, with seven months of campaign history to show on a call.
- The client Approvals page now follows your page toggles, so a client is never asked to sign off on a plan they cannot see.
- Adding a contact now ends with that client’s approval settings, so approvals can no longer be switched on with nobody to send them to.
- A brand can carry its own Overview wording for every client in it.
- The client activity feed gives each flagged check its own row and explanation.
1. Sample account
Pick a niche (home services, dental, legal) and you get a complete client: pages, tracked keywords and their positions, content, link and Business Profile plans with finished and pending items, approvals waiting to be clicked, more than a year of traffic history, stored monthly reports and an AI visibility history that starts thin and thickens as the campaign goes. The work log reads like a real campaign, down to the audit that flagged something and the fix a few days later.
It opens through the same View as client door and the same no-login link as a real client, in your branding, with your page toggles. A switch decides whether the demo has approvals a prospect can actually click. Everything resets overnight, so yesterday’s demo clicks are gone and the numbers have moved.
The sample client is never listed in your roster, never counted, never worked on and never appears anywhere a real client would.
3. Add contact ends with approvals
Which approvals reach a client is a delivery setting; who receives them is everyone on the contact roster. Those two drifted apart. The add dialog now shows one switch per approval type, pre-set to what that client has today, wherever you open it. The Contacts and Delivery tabs say which approvals every contact is sent, and flag it when approvals are on and the roster is empty.
4. Brand Overview copy
A brand’s Portal tab now has its own Overview copy. Write the phase writeups once there and every client in the brand reads them; leave a section alone and it keeps the workspace wording. A client’s Contacts tab points you at the brand page when the client belongs to one.
Behind the scenes
We spent the day settling where things live. The SEO service now sits under the website it is sold on, which matters because a client is no longer one campaign on one site: they might have a second site, or a website service and no SEO at all. Every old address forwards, and every link we build (tasks, approvals, digests, alerts, the agents’ own links) now carries the website rather than relying on a forward. The partner sidebar follows the same logic: one list per service, Clients as the roster.
The portal menu used to be written out by hand in six places and had quietly drifted; one surface said “Other Tasks” where every other said “SEO Tasks”. There is now one definition, and a test that fails the build the next time they disagree.
The better story is page monitoring. A third of all open content-change alerts across the fleet were two call tracking numbers rotating and nothing else. Two causes: call tracking hands every visit a different number from a pool, and we were sometimes comparing a page as the server wrote it against the same page as a browser rendered it, which makes every script-injected string look like an edit. We now always compare the rendered page, and a line that differs only in its phone number is not a change. Replayed against real captures from the last three days, the old comparison raised 84 alerts and the new one 41, with nothing lost that the old one would have let pass.
We also taught the agent that triages escalations to read what happened on a campaign after the run, not just before it, and to finish the investigation rather than write “look into this” on a person’s list. It had been handing people questions it could have answered itself.
Get these updates by email
A short note when something changes on the platform, plus whatever else you pick.
Check your inbox to confirm your subscription.