This is a sample session for a suspended service-area electrician. It follows the Co-Pilot's actual guided workflow: progressive intake, classification, trigger diagnosis, a screenshot-gated audit, live web checks, two policy-freshness verifications, controlled fixes, evidence-pack preparation, protected appeal submission, and post-reinstatement handling. Fictional case. No reinstatement outcome is implied or guaranteed.
Hi. I'm your ClearDossier Reinstatement Co-Pilot. I'll work through this with you one step at a time and keep the case organised as we go.
Two rules before we start: don't create a second profile while this one is suspended, and don't experiment with names, categories or addresses. We'll take the safe route.
Let's start easy. What's your client's business name, and what do they do?
Meridian Electrical Services. They're a mobile electrician serving customers across the West Midlands.
Got it. I'll treat this as a service-area case unless the next facts tell us otherwise.
Quick note: I'm using connected mode, so when we reach the audit I can assist with live web checks. Any web finding will still need manual verification before it becomes part of the appeal.
Where does the business actually operate from: a home, office, coworking space, or another setup?
It's run from the owner's home.
Understood.
Do customers ever visit that home to receive the electrical service?
No. He travels to them.
That points toward a Pure Service-Area Business.
One more important check before we classify it fully.
Does the Google profile currently show the home address to the public?
Yes.
Because customers don't visit the home, a publicly visible home address is a configuration issue we'll need to examine carefully. Don't change it yet. We're still establishing the before-state.
What exact status or message do you see in Google's appeals and reinstatement flow?
It says the Business Profile is suspended for quality issues.
Thanks. That gives us the stated suspension reason.
Before we classify the case, I need to rule out an account-level problem.
Did only Meridian Electrical Services disappear, or were all of the client's Business Profiles affected at the same time?
Only Meridian was affected.
Good. We're dealing with a single-profile case rather than an apparent account-level restriction.
State 1 is complete.
Based on what you've told me: Pure Service-Area Business (SAB).
Customers do not visit the home, and the business travels to customers.
That classification matters because a visible residential address is not treated the same way as a genuine customer-facing staffed location.
Before we move on: is the business selling or delivering any age-restricted products such as alcohol, cannabis or weapons?
No.
Good. No age-restricted-product exception has been triggered.
State 2 is complete.
Now we're looking for the factors that could explain the suspension.
One of the first checks is the business name.
Is 'Meridian Electrical Services' the real-world name the business uses on its website, documents and customer-facing materials?
Yes.
Good. No obvious keyword-stuffing issue from the information you've provided.
Next, we'll check for duplicate listings.
Because I'm in connected mode, I can assist with that live. Would you like me to run the live duplicate search now?
Yes.
I searched the business name and close variants across the available web results.
Finding: one older listing appears to refer to the same business at a previous configuration.
Do not delete or create anything yet. This is a potential duplicate or agency-created listing issue. It needs to be documented and handled through the appropriate process rather than blindly removed.
State 3 finding: visible home address is a likely configuration trigger. Possible duplicate requires audit confirmation.
Before we change anything, we need a clean record of what Google currently shows.
This is a hard gate. We capture the before-state first, then audit it.
Please save a screenshot of the current Business Name field.
Done.
Saved.
Now save a screenshot of the Location settings showing whether the address is visible.
Done.
Saved.
Now save the Phone field.
Done.
Saved.
Now save the Website field.
Done.
Saved.
Now save the Primary Category field.
Done.
Saved.
Now save the Service Area settings.
Done. It shows a 30-mile radius and the field is locked.
That is important.
The profile appears to be using a legacy radius-based service-area configuration, and the field is currently locked. This is the Legacy Radius Service Area Lock.
We also have the visible residential address confirmed.
The before-state has now been captured.
I can now run the live NAP consistency check against the client's public web footprint.
Live check complete.
The business name and phone are consistent across the sources checked. One directory contains an older address.
NAP finding: 1 address mismatch. Verify manually before using this finding in the appeal.
Confirmed:
Pure service-area business
Residential address publicly visible
Legacy radius configuration appears locked
Business name appears consistent
Primary category appears appropriate
One external address mismatch identified
Potential older duplicate requires handling
Do not fix anything yet. The audit gate must be passed first.
Are all of the before-state screenshots saved and the identified mismatches recorded?
Yes.
State 4 complete. Audit gate passed.
Before I give you any fix instructions, I'm checking the current Google Business Profile guidance relevant to this case.
Checked the current Google guidance relevant to: service-area business address visibility, service-area configuration, current service-area limits, and the relevant profile configuration rules.
Policy-Freshness Report: no change detected for the rules being applied to this case. The Blueprint remains aligned with the current guidance checked.
Before you do this: don't change the business name, category or address to 'test' another configuration. This is a reality correction, not an experiment.
For a business that does not receive customers at the home, remove the public display of the home address.
Make that single correction and save it.
Done.
Good.
The service-area field is still locked to the old radius configuration. Because this cannot be edited directly, the correct path is to request the configuration reset through official Google Business Profile support.
Do not create another profile and do not keep changing settings while waiting for the reset.
Once Google resets the configuration, use genuine cities, regions or postal codes that the business actually serves.
Google reset it and I changed the service area to the actual towns we serve.
Good.
State 5 complete. The profile configuration now reflects the business's actual operating model.
Now we build the evidence pack.
One timing point matters here: prepare and name every file before opening the appeal upload process. The upload window begins when the evidence step is opened.
For this SAB case, we're looking for three evidence layers.
Paper: proves the real business.
Operational: shows the business actually operates as described.
Consistency: connects the evidence back to the online profile.
You already have business registration and documentation, utility evidence, and website evidence. We still need operational evidence.
Do you have a recent photo showing the business's actual vehicle or equipment, or another genuine operational indicator?
Yes. I have photos of the van and electrical equipment.
Those can be assessed as part of the operational layer.
Paper: ready.
Operational: ready.
Consistency: ready.
The evidence supports the same business configuration being appealed.
Evidence-pack gate passed.
Before we prepare the appeal, I'm running the second live policy check. This is separate from the earlier check because Google's guidance and appeal interface can change.
Live policy check complete.
Policy-Freshness Report: no relevant drift detected in the rules checked for this case. The appeal will be prepared against the current verified guidance.
The Co-Pilot now uses the appropriate SAB appeal structure and fills it from the case record. It does not invent missing information. It also performs a placeholder safety check.
Result:
Business name supplied
Business type established
Corrected configuration recorded
Evidence pack confirmed
No unresolved appeal placeholders
The appeal is ready.
Use the official Google appeal path only. When you reach the evidence step, have the prepared files ready before clicking Add evidence.
Submitted.
Submission recorded.
Appeal submitted: [fictional case date]
State 7 complete.
Google approved it.
Good.
First, confirm the profile is actually live again.
Can you see the profile as live in Google Search or Maps?
Yes.
Confirmed.
Don't immediately make major profile changes simply because reinstatement succeeded.
The profile is now in the maintenance stage.
The case is reinstated, but we're not finished. The next objective is preventing the same configuration problem from returning.
For this client, the maintenance record should include:
Service-area configuration review
Business-name consistency
Website consistency
Directory consistency
Review of major changes before they are made
The agency can now keep the case under ongoing monitoring rather than treating reinstatement as the end of the relationship.
Meridian Electrical Services
Business type: Pure Service-Area Business
Suspension: Quality-related suspension
Primary configuration issue: Public residential address
Secondary configuration issue: Legacy Radius Service Area Lock
NAP finding: One external address mismatch identified
Duplicate finding: Older potential duplicate identified for controlled handling
Before-state screenshots: Confirmed
Fixes: Address hidden, service-area configuration reset and corrected
Evidence: Paper, operational and consistency layers confirmed
Policy Checkpoint 1: Completed
Policy Checkpoint 2: Completed
Appeal: Submitted through official path
Outcome: Reinstated in this fictional demonstration
Post-reinstatement: Maintenance stage initiated
A completed case leaves the agency with a documented case record, verified audit findings, evidence readiness, protected appeal output, a submission record and a post-reinstatement maintenance path.
A per-client case file recording the classification, the triggers considered, every finding, every change made, the submission date and the follow-up position. The agency keeps a defensible record of the whole case rather than a single letter.
The before-state captured field by field, plus the NAP mismatch table and any duplicate-listing finding. Web-derived findings are cited and flagged for manual verification before they are relied upon.
A scenario-matched evidence pack across the three layers, paper, operational and consistency, with file naming applied and an exact-match check run. The gate does not open until at least one item from each layer is confirmed.
The correct scenario template auto-filled from verified case data only, with a placeholder check that refuses to finalise while any field is unresolved. No invented facts and no compliance claims the audit has not confirmed.
The official submission sequence walked step by step, the 'Add evidence' timing handled, and the submission date recorded so the waiting period and any additional-review routing can be tracked.
A maintenance checklist covering service-area configuration, name, website and directory consistency, plus a change-review habit. This is what turns a one-off reinstatement into an ongoing monitored client relationship.
Note: The session above is illustrative. The business name 'Meridian Electrical Services' is fictional and used only to demonstrate the workflow. No reinstatement outcome is implied or guaranteed. The Co-Pilot produces a structured, policy-compliant case. Reinstatement decisions are made by Google's review team.
Lite Plus from $37. Agency Edition at $97. Both include the full 10-state workflow.
See Pricing & Get AccessGBP Co-Pilot: Explore All Pages