One console for every account

The CallPages admin console now lists both page-owner accounts and consumer accounts, lets an admin log in as an owner or an end user to see exactly what they see, and edit the settings of any call page — real administration, not a read-only report.

Support used to be blind. When an owner wrote in with a problem inside their account, the team could see the platform’s side of the story but not the owner’s — and a consumer’s problem could not even be looked up in the same place, because owners and end users lived in different lists.

Help requires sight

Illustration: a support specialist seeing owners and consumers in one console and fixing a page on the owner’s behalf

“Have you tried—” is not support. An admin who can open the exact account, in the exact state the owner left it, skips the twenty questions and goes straight to the problem. Login-as exists in mature platforms for one reason: most account problems are invisible from outside the account.

Power with a paper trail

Illustration: an abstract admin console with owner and customer account cards side by side, a magnifier, and a settings gear

Stepping into someone’s account is serious, so it is built seriously: admin sessions are visibly marked, and every impersonation is written to an audit log. The feature is a support tool with receipts, not a skeleton key — which is what makes it safe to use it generously.

How it works

Owners and consumers in one console: every page-owner account and every end-user account, searchable from a single admin surface.
Login-as, both ways: an admin can step into a business page owner’s account or an end user’s account and see the product exactly as they see it — with the session marked as an admin session and an audit trail of the visit.
Edit any page’s settings: the same settings an owner controls, reachable by the admin for every call page, so a fix does not have to wait for instructions over the phone.