Frequently asked questions

Repdar focuses on Google reviews and the review workflows connected to Google Business Profile locations. This deliberate scope keeps monitoring, responses, policy assessment, alerts, and reporting connected to one clear source.

Yes. A single-location team can use the same operating method as a distributed organization. Multi-location setups add portfolio structure, role clarity, local ownership, and broader reporting where those capabilities are needed.

No. Repdar is for Google review operations. It keeps review activity, response decisions, policy requests, alerts, and related action organized, while customer records and broader sales or service workflows remain in the systems your team uses for those purposes.

Collection depends on the access available for each location, and some locations need a manual check rather than a connected one. Repdar labels each check as complete, partial or blocked, and a review missing from a partial or blocked check is treated as unknown, never as removed.

No. Google evaluates removal requests under its policies and makes the final decision. Repdar helps teams identify a possible policy basis, organize the relevant context, submit a careful request, and track the resulting status.

Legitimate criticism should be handled as feedback. The team can prepare a calm public response, investigate the customer’s concern, and use what it learns to improve the experience. A policy request is not a substitute for service recovery.

The response workflow covers both. Positive replies can recognize the details a customer appreciated. Negative replies can acknowledge the concern, protect private information, avoid premature factual claims, and offer a suitable next step.

No. Repdar keeps drafts clearly labeled as drafts. Your team approves and publishes replies on Google, and the record notes what was published.

Google maintains its own guidance for prohibited and restricted content. Read the current policy directly in the Google Maps User Contributed Content Policy (opens in a new tab). Google may update its rules, so the current source should guide each assessment.

Repdar can organize newly added Google reviews, observed removal or reappearance of tracked reviews, response work, policy-request status, and urgent items. An observed status change does not by itself establish why Google made a change.

Urgency should come from content and potential impact, not star rating alone. Teams can define categories such as safety concerns, credible threats, severe operational allegations, or other issues that require prompt human review and a clear escalation path.

Yes. Local operators can retain the context needed for individual reviews while regional or central teams maintain visibility into open work, sensitive items, recurring themes, and consistent response guardrails.

No. Reporting can reveal review patterns, workflow status, and themes worth investigating. It should not claim a cause without supporting evidence. Repdar gives teams a clearer set of questions and a record they can examine alongside operational facts.

Only an explicit decision from Google. Each review counts once, even if Google sent more than one notice about it. Pending requests and reviews that simply stopped appearing are reported separately and never counted as confirmed.