A practical operating system for requesting reviews, separating sensitive feedback, replying safely, and turning recurring learner issues into owned changes.
A review request sent to the wrong person can create more work than the review is worth. A parent may have paid for a teen package, the learner may have completed the lesson, and an operations manager may own the scheduling problem. One contact record does not tell you who should receive which message.
Driving school reputation management solves that operating problem. It connects a declared lesson or course event to an eligible recipient, a policy-safe request, a privacy-safe reply, and a named owner when feedback exposes a real process issue. The goal is a defensible feedback system, not a promised star rating.
This guide is deliberately specific to driving instruction. It covers teen and adult learners, guardians, classroom and online courses, behind-the-wheel packages, road-test preparation, defensive-driving programs, vehicles, instructors, locations, and state-specific operating claims.
You will build:
- an audience-and-product map that separates learner, payer, and contracting party;
- a truth card for licensed entities, course labels, locations, vehicles, and approved claims;
- eligibility, permission, suppression, response, and escalation workflows;
- a theme ledger and measurement dictionary with evidence at every stage.
The operating chain: completed eligible event → verified recipient and permission → neutral review request → public or private feedback → privacy-safe response → sensitive-case escalation → coded theme → owned change → documented closure.
1. Define What Driving School Reputation Management Controls
Driving school reputation management controls how feedback is requested, received, routed, answered, coded, and closed. It does not control what a learner writes, whether a platform displays a review, or whether a reader enrolls. Treat the public rating as an external signal while managing the underlying workflow as an internal operation.
The cleanest system begins with distinct lanes. A public review is visible platform content. A private satisfaction survey is internal feedback. A complaint asks the school to resolve a service issue. An incident report may activate a separately governed safety process. A refund request, licensing concern, HR issue, and platform dispute each need their own intake route and owner.
Where schools go wrong is dropping every unhappy message into a “negative review” queue. That label encourages a public-response mindset when the actual task may involve a dual-control vehicle concern, a missed pickup, an instructor employment matter, or an approved-course representation. The queue should be chosen by subject and sensitivity, not sentiment.
| Feedback channel | Intake route | Visibility | SLA owner | Escalation | Record system | Never put in public |
|---|---|---|---|---|---|---|
| Public review | Platform alert or manual check | Public | Reputation owner; school sets timing | Operations for service facts | Platform export + response log | Learner identity, lesson, route, test, account, accommodation |
| Private survey | Declared survey form | Internal | Quality owner; school sets timing | Course or location owner | Survey system | Any survey detail quoted without permission |
| Complaint | Dedicated email, phone, or case form | Private | Operations owner; school sets timing | Manager or compliance owner | Case or CRM log | Account history, instructor allegation, resolution terms |
| Incident or safety report | Dedicated incident route | Restricted | Named safety owner; school sets timing | School policy, insurer, regulator, or counsel as applicable | Separately governed incident system | People, vehicle, route, collision, injury, or findings |
| Refund or billing issue | Billing support route | Private | Billing owner; school sets timing | Operations or finance | Billing case record | Payment, package, refund, or account facts |
| Platform dispute | Platform reporting process | Platform-controlled | Reputation owner; platform controls timing | Compliance or counsel when needed | Dispute log | Speculation about reviewer identity or legality |
| Instructor HR matter | Restricted HR route | Restricted | HR or owner; school sets timing | Employment process | HR system | Employment status, discipline, or investigation |
Use the broader review-management framework for platform-wide monitoring and governance. This guide narrows that framework to the instruction lifecycle and the privacy boundary created when a learner, guardian, payer, instructor, and licensed school can all touch one service record.
2. Map Audiences and Instruction Products Before Requesting Feedback
Map the participant, payer, contracting party, service owner, and feedback recipient before sending anything. A teen learner and guardian can describe different parts of the same package, while an adult refresher may hold every role. The eligible recipient depends on the completed service and permission record, not the easiest email address to reach.
Build the matrix from the actual catalog. A six-lesson behind-the-wheel package creates several possible milestones. A one-off road-test-prep session creates one. A classroom or online defensive-driving course may have completion rules distinct from attendance. Fleet instruction has a buyer and participant population. Applicants and vendors have experiences, but they are not customers and should not enter the customer-review workflow.
The hard operational detail is deciding what experience each person can genuinely describe. A guardian might assess booking, pickup communication, billing, and observed professionalism. The teen can assess instruction, but the school must decide whether and how it contacts that learner. An employer buyer may assess coordination while drivers assess instruction. Never combine those perspectives into one assumed “customer.”
| Audience or product | Likely payer | Participant | Service owner | Eligible trigger | Privacy risk | Exclusion |
|---|---|---|---|---|---|---|
| Teen behind-the-wheel package | Often guardian; verify | Teen learner | Instruction operations | Declared completed lesson or package milestone | Age, route, permit or test detail | No verified recipient relationship or permission |
| Parent or guardian | May be contracting party | Not necessarily the learner | Enrollment or operations | Completed milestone they can genuinely assess | Learner identity and account facts | Cannot verify authority or experience |
| Adult first-time learner | Usually self; verify | Adult learner | Course or instruction owner | Completed lesson or declared course milestone | Route, test, accommodation, account | Unresolved incident or refund |
| Refresher learner | Self or third party | Adult learner | Instruction owner | Completed refresher session | Reason for refresher, disability, incident history | Unverified experience |
| Road-test preparation | Learner or guardian | Learner | Location or instructor operations | Completed prep session, not test result | Test date, route, result | Do not condition on passing |
| Defensive driving or traffic school | Learner, employer, or other party | Course participant | Course administrator | Declared completed course milestone | Driving record, court or points context | Attendance alone if policy requires completion |
| Classroom or online course | Learner or guardian | Enrolled learner | Course administrator | Declared completion event | Age, progress, credential status | Incomplete or disputed completion |
| Fleet or employer buyer | Employer | Drivers | Account owner | Closed delivery milestone | Employee performance or incident facts | Participants without approved contact basis |
| Instructor applicant | Not applicable | Applicant | HR | None in customer workflow | Application and employment data | Always exclude from customer requests |
| Vendor | Contract-dependent | Vendor staff | Procurement or owner | None in customer workflow | Commercial terms | Always exclude from customer requests |
Do not turn a passed road test into the request trigger. That selects recipients by outcome and ignores learners who received genuine instruction but did not pass. Use the completed prep session or another declared milestone. Likewise, a private survey cannot become a filter that sends happy respondents to Google and diverts unhappy respondents to support.
Need a practical review workflow for your school’s service mix? Map the eligible events, recipient rules, and public-response boundary before choosing automation.
3. Create a State-and-Service Truth Card
Create one truth card for every operating state and licensed entity or location. It should connect the regulator, legal business identity, precise course label, credential owner, operational constraints, and approved public claim to dated evidence. Review responders and request operators should use this card instead of recalling compliance details from memory.
Driving-school regulation is not one national template. As a clear example, the California DMV driving-school page describes separate licensing roles for owners, operators, and instructors providing compensated motor-vehicle instruction. That evidence supports a California statement only. It does not prove that another state uses the same roles, requirements, course terminology, or approval process.
The truth card also prevents accidental overstatement during busy periods. Summer demand, school breaks, permit deadlines, test dates, bad weather, instructor calendars, pickup zones, and dual-control vehicle availability can tighten capacity. Those conditions do not justify advertising an unavailable course, implying guaranteed test access, or letting a responder confirm a learner’s schedule publicly.
| Truth-card field | Required entry | Example of acceptable evidence |
|---|---|---|
| Operating state | Full state name; never “nationwide” by default | Licensed operating record |
| Regulator URL | Current official state page | Dated URL capture or compliance register |
| Licensed business name/location | Exact entity and covered location | License or regulator lookup record |
| Course/service label | Exact approved or internal name | Course approval, catalog, or policy |
| Requirement owner | Named role for instructor, vehicle, and classroom requirements | Responsibility matrix |
| Approved claim | Sentence responders and marketers may use | Compliance-approved claim bank |
| Evidence location | Stable record path or system ID | Compliance repository reference |
| Review date | Date the evidence was checked | Review log |
| Approver | Named role, not a shared inbox | Approval record |
Keep a separate row per state, entity, location, and course where the evidence differs. The failure mode is one “licensed and approved” sentence copied into every location response. If a reviewer alleges a licensing problem, the public reply should not litigate the claim from the truth card. It should acknowledge the concern and move the matter to the named compliance route.
4. Choose Lifecycle Triggers and Exclusions
Choose review triggers from completed, verifiable lifecycle events and apply the rule consistently. Suitable events can include a completed lesson, declared course milestone, road-test-prep session, or closed recovery case. Exclude records with unresolved incidents, unclear recipient identity, duplicate requests, suppression, or a service state that does not meet the written rule.
A trigger needs more precision than “after service.” For behind-the-wheel instruction, define whether eligibility begins after lesson one, after a package milestone, or after package completion. For an online or classroom course, define the system event that represents the approved milestone. For road-test prep, the trigger is the completed session, never the test result. The scheduling or course system should supply the event ID and timestamp.
Set exclusions before launch. No-shows, cancellations, refunds, unverified participants, employees, vendors, and duplicate records do not enter the request queue. An unresolved complaint, collision or safety event, licensing issue, or active service-recovery case stays on hold under its own governance. Closing a recovery case may create eligibility only if the written policy says so and the request remains neutral.
| Eligibility field | Required check | Evidence |
|---|---|---|
| Completed event | Named event meets the service rule | Event ID and completion timestamp |
| Recipient relationship | Learner, guardian, buyer, or contracting party is verified | Relationship field |
| Genuine experience | Recipient can assess the named service | Enrollment or contract link |
| Channel permission | Permission covers the selected channel | Consent or communication record |
| Last request date | Retry ceiling and spacing rule pass | Request log |
| Suppression status | No active stop or suppression record | Suppression list |
| Unresolved case | No open governed complaint or incident | Case-system lookup |
| Employee/vendor flag | Recipient is not in an excluded relationship | CRM or HR/vendor match |
| Incentive check | No reward tied to posting or sentiment | Campaign configuration |
| Sender | Named school or location identity | Approved sender record |
| Decision | Send or do not send, with reason code | Eligibility log |
Run the worksheet on every record, not only the difficult ones. A neutral rule means the school does not inspect a survey score, instructor note, pass result, or complaint tone to decide who receives the public-review link. For more generic request formats, use the separate guide to asking local customers for Google reviews after this driving-school eligibility layer is complete.
5. Build the Request, Permission, and Suppression Workflow
Build each request as an auditable message event with a known sender, verified recipient relationship, permitted channel, direct platform link, send date, retry ceiling, stop signal, and suppression owner. Keep it separate from lesson reminders, course marketing, referral incentives, and private surveys so consent and purpose remain clear in the record.
The request itself can be short: identify the school or location, name the completed service at a safe level, ask for an honest review, provide the direct link, and include the channel’s required stop method. Avoid “five-star,” “positive,” or wording that implies a discount, test benefit, certificate, extra lesson, or referral credit depends on the response.
Google’s review guidance allows businesses to ask genuine customers for reviews but prohibits incentives for posting, changing, or removing them. The FTC Consumer Reviews and Testimonials Rule Q&A addresses fake or false reviews, sentiment-conditioned incentives, undisclosed insider relationships, and suppression. Write the school policy to meet these minimums, then have the appropriate adviser assess other applicable requirements.
Neutral request example
“Thank you for completing your road-test preparation session with [School/Location]. If you would like to share an honest review of your experience, use this link: [direct review link]. Your feedback is optional. [Channel stop instruction].”
Set a retry ceiling as an internal policy, not a portable industry benchmark. One school may permit one reminder; another may permit none for certain programs. The system should record the ceiling, previous send, next eligible date, and stop event. Once a recipient opts out or the relationship becomes uncertain, the suppression owner resolves the record before any further request.
What actually breaks here is data reuse. A marketing platform imports the payer email, a course system holds the learner, and a scheduling tool marks a lesson complete. Joining those records without relationship and permission checks can message the wrong person. Require a stable service record ID and recipient-role field before automation runs.
6. Route Reviews and Complaints Without Exposing Learners
Route feedback by subject and sensitivity before drafting the reply. Public responses may acknowledge the message and offer a private contact path, but they must not confirm learner identity, age, lesson, route, test, accommodation, account, incident, instructor HR, or licensing facts. Sensitive allegations move immediately to the named internal owner.
A verified Business Profile can read and reply to reviews where the feature is available, according to Google Business Profile help. The reply is public. That makes restraint more useful than a detailed rebuttal. Even if the reviewer names an instructor, pickup point, or test date, the school should not validate those facts in its response.
| Review type | Public response boundary | Private escalation owner |
|---|---|---|
| Positive | Thank them without confirming lesson, learner, result, or route | None unless content reveals sensitive facts |
| Neutral or vague criticism | Acknowledge and offer the standard private contact path | Location or service owner |
| Scheduling or pickup problem | Do not confirm booking, zone, instructor, or time | Scheduling operations |
| Vehicle or classroom issue | Do not confirm vehicle, defect, room, attendance, or findings | Fleet, facilities, or operations owner |
| Instructor complaint | Do not confirm employment, assignment, discipline, or investigation | Operations and HR |
| Billing or refund dispute | Do not state package, payment, balance, or resolution | Billing owner |
| Factual dispute | Do not publish account evidence or argue record details | Operations or compliance |
| Personal data in review | Do not repeat it; use platform process where appropriate | Privacy or compliance owner |
| Safety or incident allegation | Acknowledge concern only; do not announce investigation or finding | Safety owner and separately governed process |
| Licensing or legal allegation | Do not diagnose legality or cite private case facts | Compliance or counsel |
| Spam or policy issue | Avoid identity speculation or threats | Reputation owner uses platform dispute route |
A safe response pattern is: “Thank you for raising this concern. We do not discuss learner or service details publicly. Please contact [private route] so the appropriate team can review the matter.” Adjust the acknowledgement without adding facts. Do not say a report is false, defamatory, unlawful, removable, or resolved unless the authorized owner has approved exact public language.
Google notes that reviews can be delayed, removed, or unavailable for policy, profile, category, or regional reasons. Its current review-availability guidance includes education-related restrictions, but a school must check its actual profile and the current rule rather than generalize one restriction to every driving school.
Review replies need a public boundary and an approval rule. theStacc’s Local SEO module covers Google Business Profile posts, review replies, citations, rank tracking, and approval rules; your school still owns incidents, licensing, consent, refunds, HR, and service recovery.
7. Turn Themes Into Owned Operational Changes
Code feedback into a declared ledger that preserves course or job type, location, category, severity, evidence confidence, owner, action, and closure evidence. Review patterns over a fixed window with the sample shown. The ledger should help an operator investigate scheduling, instruction, vehicle, classroom, billing, or communication processes without publishing blame.
A useful code is specific enough to act on. “Communication” is too broad. “Road-test-prep pickup-zone instructions unclear before weekend session” points to an asset and owner. “Instructor bad” is a conclusion. “Adult refresher learner reports lesson objective was not explained” is a coded observation that can be checked against the lesson record and curriculum.
Separate evidence confidence from severity. A single safety allegation may be high severity even before facts are established, so it moves into the incident process. Five vague comments may show repetition but supply little diagnostic detail. A theme ledger is not an investigation record, and a public review is not proof of instructor performance.
| Ledger field | What to record |
|---|---|
| Coded theme | Stable, documented code with plain-language definition |
| Course/job type | Behind-the-wheel, road-test prep, classroom, online, defensive driving, fleet, or other declared type |
| Location | Licensed or operating location tied to the service record |
| Category | Instructor, vehicle, classroom, scheduling, billing, curriculum, communication, or process |
| Date window | Declared start/end dates and cohort basis |
| Sample caveat | Eligible count, missing records, and any small-sample warning |
| Supporting records | Case IDs, schedule records, course records, or approved evidence references |
| Owner | Named accountable role |
| Action | Specific change, test, or investigation |
| Review date | Next decision date |
| Closure evidence | Approved policy, revised message, completed training, fixed asset, or documented disposition |
Review themes on a declared 90-day window when using the repeat-theme formula below, and display the eligible sample. If the school changes its coding taxonomy halfway through, restate the window or map the categories transparently. Do not rank instructors or locations from tiny, unmatched samples. Course mix, learner audience, seasonal capacity, and location operations can all change what feedback appears.
The operational payoff is a closed loop. If repeated comments point to unclear pickup-zone instructions, the owner updates the confirmation message, records the approval, and checks the next declared cohort. If the evidence remains mixed, keep the issue open. The ledger is designed to support decisions, not manufacture certainty.
8. Measure the System Without Promising Stars or Enrollments
Measure review operations as their own evidence chain, then compare them carefully with acquisition and course operations. Keep impression, click, call click, form, qualified enquiry, booked job, and completed job in separate rows and source systems. A review interaction may be associated with movement, but it cannot be credited as the sole cause.
The funnel dictionary prevents category errors. A call click is a browser event, not a connected call. A form is a submission, not a qualified enquiry. A booked lesson is not a completed lesson, and neither is a completed course. Define “booked job” and “completed job” in the school’s own terminology while retaining the distinct stages required for analysis.
| Stage | Business definition | Timestamp | Source system | Owner | Exclusions | Allowed relationship to review evidence |
|---|---|---|---|---|---|---|
| Impression | Declared search or profile appearance | Platform-recorded time/window | Search/profile reporting | Marketing | Unsupported estimates or duplicate exports | Trend beside review evidence; no sole-cause claim |
| Click | Declared website or profile click | Analytics event time | Web or profile analytics | Marketing | Bots and declared internal traffic | Associated observation only |
| Call click | Tap on a tracked call control | Event time | Web/profile analytics | Marketing | Duplicate or test events | Never treated as a connected enquiry |
| Form | Valid intake form submission | Submission time | Form system | Intake | Spam, tests, duplicates | Never treated as qualified or booked |
| Qualified enquiry | School-defined request meeting declared fit and contact criteria | Qualification time | CRM or intake log | Intake owner | Spam, duplicates, out-of-scope requests | Compared by cohort; no review attribution |
| Booked job | Lesson or course reservation accepted under school policy | Booking time | Scheduling/course system | Enrollment operations | Canceled, test, or duplicate bookings as declared | Not a completed service |
| Completed job | Declared lesson or course completion event | Completion time | Scheduling/course system | Instruction operations | No-shows, cancellations, incomplete milestones | May create request eligibility under written rule |
Google Analytics recommends distinct lead events such as generate_lead, qualify_lead, working_lead, and close_convert_lead. Use the GA4 event guidance as a reference, then document the school’s offline definitions. Do not rename a review, profile view, or call click as a customer outcome.
Four operational formulas with complete evidence fields
| Formula | Numerator | Denominator | Evidence window | Source system | Owner | Exclusions |
|---|---|---|---|---|---|---|
| Eligible-request coverage | Unique completed service records meeting the written eligibility rule that received one request | All unique completed service records meeting the same rule in the same window | One declared 28-day completion cohort | Scheduling/course system + request log | Operations owner | Canceled, no-show, refunded, unresolved incidents, duplicates, employees/vendors, suppressed contacts, ineligible service types |
| Review-response coverage | Unique eligible public reviews receiving a logged approved response | All unique eligible public reviews first detected in the same window | One declared calendar month + stated moderation lag | Platform export + response log | Reputation owner | Removed/unavailable reviews, duplicates, spam under active dispute, reviews compliance or counsel says not to answer |
| Escalation closure rate | Unique feedback cases opened in the cohort and closed with documented owner and disposition | All unique feedback cases opened under the written escalation rule in the same cohort | One declared 28-day intake cohort + school’s stated case-maturation lag | Case/CRM log | Operations or compliance owner | Duplicates, platform-only disputes, open cases not yet mature, records transferred to a separately governed incident process |
| Repeat-theme rate | Unique coded feedback records containing the declared theme | All unique coded feedback records eligible for theme analysis in the same window | One declared 90-day analysis window, with sample size shown | Coded feedback ledger | Quality/operations owner | Uncoded records, duplicates, spam, employee/vendor feedback, categories changed mid-window unless restated |
None of these formulas has an approved portable benchmark. Compare the school with its own declared prior cohorts only after checking that eligibility rules, service mix, moderation lag, and coding have not changed. For the wider relationship between reviews and search activity, see the separate guide to SEO reputation management; do not turn association into a ranking promise.
Frequently Asked Questions
These answers cover policy and operating choices that remain after the workflow is designed. They add boundaries for timing, recipients, incentives, sensitive replies, platform availability, attribution, and multi-location comparison. Apply them through the school’s written policy, current platform documentation, state-specific evidence, and advice appropriate to the school’s operating jurisdictions.
What is driving school reputation management?
Driving school reputation management is the operating system for requesting genuine reviews, collecting private feedback, replying within public privacy limits, escalating sensitive cases, and assigning recurring issues to an owner. It controls the process and evidence around feedback. It cannot control a rating, platform decision, learner response, ranking, or enrollment outcome.
When should a driving school ask for a review?
Ask only after a completed event named in the school’s written eligibility rule, such as a finished behind-the-wheel lesson, completed course milestone, or closed service-recovery case. Do not ask after a no-show, cancellation, refund, unresolved safety matter, or duplicate request. Apply the same trigger regardless of whether the experience appeared positive or negative.
Can a driving school offer a discount for a five-star review?
No. A discount conditioned on a five-star or positive review is a sentiment-conditioned incentive. Google prohibits incentives for posting, changing, or removing reviews, and the FTC rule addresses conditioned incentives and false reviews. Keep tuition discounts, referral offers, and review requests separate. If counsel approves any neutral promotion, disclose and govern it independently.
Should a parent or the learner receive the review request?
Send the request to the verified person whose relationship and channel permission match the service record and school policy. For a teen package, that may be the contracting guardian; for an adult lesson, it may be the learner. Never guess from the payer field. Record participant, payer, contracting party, recipient permission, and the completed event separately.
How should a driving school reply to a review about an instructor or safety issue?
Acknowledge the concern without confirming the learner, instructor, route, vehicle, lesson, or incident details. Invite the reviewer to use a private contact route, then send the case to the school’s named safety, compliance, or operations owner. Do not investigate in the reply, announce findings, diagnose legality, or ask the reviewer to remove the post.
Why might a Google review be delayed, removed, or unavailable?
Google says reviews can be delayed, removed, or unavailable because of policy enforcement, profile status, or category and regional availability. A missing review is not evidence that the reviewer failed to submit it or that the school did something wrong. Log the observation, check official guidance, and use Google’s process without pressuring the reviewer to repost.
Do more reviews guarantee better rankings or more enrollments?
No. Review activity does not guarantee a ranking position, enquiry, enrollment, booked lesson, or completed course. Measure each stage in its own source system and treat reviews as associated evidence only. Compare review operations with search, intake, scheduling, and completion records, but do not credit a rating or review count as the sole cause of movement.
How should a multi-location driving school compare feedback fairly?
Compare locations only after aligning the course mix, analysis window, coding rules, evidence maturity, and eligible sample. A road-test-prep site with seasonal weekend demand is not directly comparable to a classroom location running longer approved courses. Show the count behind every theme, flag small samples, and investigate process differences before assigning location or instructor blame.
A 30-Day Driving School Reputation Management Plan
Use the first 30 days to define and test the operating chain, not to chase a rating target. Establish ownership and truth in week one, map events and recipients in week two, test requests and response routing in week three, then audit evidence and fix gaps in week four before expanding.
- Days 1–7: set boundaries. Name the reputation, operations, safety, billing, HR, compliance, and platform-dispute owners. Build one state-and-service truth card per applicable entity, location, and course. Approve the public privacy boundary and private intake routes.
- Days 8–14: map the lifecycle. List each behind-the-wheel, classroom, online, road-test-prep, defensive-driving, and fleet product. Define its eligible completion event. Record payer, participant, contracting party, service owner, permitted recipient, retry ceiling, stop signal, and exclusions.
- Days 15–21: test a controlled cohort. Run the eligibility worksheet on a declared set of completed records. Check every send decision manually. Test praise, scheduling, billing, instructor, vehicle, safety, licensing, personal-data, and spam routes without inserting real sensitive details into test records.
- Days 22–30: audit the evidence. Reconcile completion records with the request log. Review suppression and duplicate handling. Confirm public replies reveal no learner or account facts. Start the theme ledger, publish the funnel dictionary internally, and record baseline operational formulas with all seven required fields.
At day 30, expand only the parts whose owner, source record, exclusion rule, and escalation path are clear. Review performance again at 14, 30, 60, and 90 days using real query and engagement data, but keep ranking and enrollment as observed business outcomes rather than guarantees.
Build the review layer after the school’s truth, eligibility, and escalation rules are explicit. That order protects learners and gives operators evidence they can improve.
Sources & references
- Google Business Profile — tips to get more reviews
- Google Business Profile — review availability and restrictions
- Google Business Profile — read and reply to reviews
- FTC — Consumer Reviews and Testimonials Rule Q&A
- California DMV — driving-school occupational licensing
- Google Analytics — recommended lead events
Rank in the Map Pack, collect reviews, and keep every location active — on autopilot.