SGA Dental Partners / Growth
Product Brief · 2026-05-28

Driving Google Business Profile and Google Reviews from the SGA Content Engine

A product brief on what PromoRepublic and Gen4Engage actually expose, what we can and cannot do programmatically today, and the three paths to make GMB management and review responses a first-class workflow inside our AI Dashboard.

Bottom line up front

The capability exists. PromoRepublic (which powers Gen4Engage) already publishes to Google Business Profile, monitors Google reviews from 130+ sources, and replies to reviews with an AI Reply Assistant. The gap is not the feature surface. The gap is the connection layer: PromoRepublic does not publish a public API, so driving these actions from the Content Engine depends on either an undocumented MCP shim, a partner-tier API conversation, or going around PromoRepublic and calling Google directly.

Recommendation: verify the Gen4Engage MCP tool set this week (15-minute test). If it covers posts and review replies, we ship the integration in days. If it does not, the practical move is a Google Business Profile API integration owned by SGA, with PromoRepublic continuing to serve the franchisee-facing UI.

01What PromoRepublic and Gen4Engage actually do today

PromoRepublic markets itself as an "agentic local marketing platform" for multi-location and franchise brands. Gen4Engage is a Gen4 Dental Partners branded surface that sits on top of the same engine (the gen4engage.com login experience is a white-labeled PromoRepublic instance). The capability matrix below was assembled from PromoRepublic's own help center and product pages.

Capability matrix

Capability area Inside PromoRepublic dashboard Detail
GBP posts (Updates, Offers, Events, CTAs) Yes Auto-publishes with location-specific name, offer, booking link. One brand calendar fans out across 200+ locations with localized variants.
Read Google reviews Yes Review Manager pulls reviews from Google plus 130+ other sites, location-by-location, with sentiment analysis and category tagging.
Reply to Google reviews (manual) Yes "Reply" button on each review or open the thread in a side panel. Replies post to Google.
AI-drafted review replies Yes "Review Reply Assistant" generates personalized, context-aware drafts in two clicks. Multi-language. Brand voice tunable.
Automated reply rules (rating, source, location) Yes Reply Assistant supports trigger-based automation: e.g. 5-star Google reviews on a specific location auto-reply with one of three templates.
Listing data sync (NAP, hours, services, categories) Partial Listing Management writes to 130+ directories including Google, Apple Maps, Yelp. Specific GBP field coverage (Q&A, attributes, products) is not publicly itemized. Voice optimization and duplicate suppression are documented.
GBP photo uploads Yes "Local Posting" surfaces support photos, menus, products, services, payment options, and hours.
Social inbox (FB / IG comments and DMs) Yes Unified inbox across connected social accounts. Not specifically tied to Google.
Analytics (review performance, listing health) Yes 2026 release added "Location Insights" and "Review Performance Analytics" rolling all online reputation data up by region and brand.
AI Assistant for content drafting Yes Drafts captions in brand voice, adapts for local context, flags off-brand wording before publish.
What this means
PromoRepublic / Gen4Engage already does, inside its own dashboard, almost every workflow we would want to drive from the Content Engine. We are not asking "can the feature exist?" We are asking "can we drive it from our UI instead of theirs?"

02The integration gap

PromoRepublic does not publish a public REST or GraphQL API. Three independent sources confirm this:

This is the operative constraint. PromoRepublic has the capability. They just have not exposed it to third parties on a self-serve basis. To drive their feature set from the Content Engine, we need one of three workarounds.

03Three integration paths

Path A. Gen4Engage MCP shim Recommended (pending verification)

An MCP server is already running at gen4engage.com/mcp with OAuth + Dynamic Client Registration. The scopes documented in our internal notes are posts, analytics, inbox, media, and ai. If the actual tool list under those scopes includes a reply_to_review or equivalent, this is the cleanest path.

EffortDays
CostSGA dev only
ConfidenceUnverified
CeilingWhatever PR exposes

How it would work: the SGA Content Engine adds Gen4Engage to its MCP server registry alongside Granola and Notion. Practice users connect once via OAuth. Claude / the AI Dashboard call tools/list and surface the available actions as workflows (draft reply, post update, schedule offer).

What we need to confirm: exact tool names and parameters under each scope. The inbox scope is the load-bearing assumption: reviews on PromoRepublic route through the social inbox, so review-reply tools are most likely living there. If they are not, this path is reduced to GBP posts only.

Path B. PromoRepublic partner API Slower fallback

PromoRepublic has demonstrated partner-level API capability with Yext. There is almost certainly a private API behind their own iOS app and dashboard. A direct conversation with their multi-location sales team would establish whether SGA (260 practices, growing) qualifies for a partner integration, what scopes are available, and pricing.

EffortWeeks to months
CostLikely contractual
ConfidenceUnknown
CeilingFull PR feature set

Why it matters even if Path A works: Path A depends on a server SGA does not own. If gen4engage.com/mcp is deprecated, rate-limited, or stripped of scopes during a PromoRepublic platform change, Path A breaks silently. A direct partner relationship is the long-term durable answer.

Path C. Google Business Profile APIs (bypass PromoRepublic) Independence play

Google's eight Business Profile APIs are fully documented and active in 2026. The Reviews API supports list, read, and reply. The Local Posts API supports create. The Business Information API supports hours, photos, attributes, services. SGA could build a direct GBP integration that the Content Engine drives end-to-end, with PromoRepublic continuing to serve franchisee self-service.

Effort2 to 4 weeks
CostSGA dev + Google quota
ConfidenceHigh
CeilingEverything GBP supports

Tradeoff: SGA owns the integration fully, including the unglamorous parts (token refresh, rate-limit handling, GBP location verification, the new April 2026 reply-moderation rules). PromoRepublic is no longer a dependency for the AI Dashboard, but it remains useful as the franchisee-facing UI where they can still see the same data. Two systems writing to GBP requires conflict-resolution rules (last-writer-wins, or "Content Engine wins for AI-drafted replies, PR wins for franchisee manual replies").

Path D. Embedded iframe / SSO Stopgap only

Mount the Gen4Engage UI inside the Content Engine as an embedded panel with single sign-on. Ships in a day. Works today. Loses everything that makes the question interesting: no AI automation, no unified workflow, no cross-system reporting. Every action is still a manual click inside a borrowed UI.

EffortHours
CostNone
ConfidenceHigh
CeilingHuman-driven only

Use case: as a placeholder for the four to six weeks between deciding on Path A or C and shipping it. Not a destination.

04Recommendation

Stack Path A on top of Path C, with Path D in the gap. Concretely:

  1. This week. Verify the Gen4Engage MCP tool list. One person, one OAuth connect, one call to tools/list. The output answers the central uncertainty. Cost: under an hour.
  2. If MCP covers posts AND review replies: ship Path A as the immediate integration. Two weeks. The Content Engine gets workflow-grade access to GBP posts and review replies without writing any Google API code.
  3. If MCP covers posts only (or nothing useful): ship Path C for review replies and listing edits. Three to four weeks. Path A still gets used for whatever it does cover.
  4. In parallel: open the Path B conversation with PromoRepublic. SGA at 260 practices is a real partner-tier prospect. Worst case the answer is no and we have lost nothing. Best case we get a documented contract and Path A becomes durable instead of opportunistic.
  5. Path D is a fallback only. If a stakeholder demands "we ship something in week one," the iframe is the answer. Not the AI Dashboard answer.

05Open questions to close before build

# Question Why it matters
Q1 What tools does gen4engage.com/mcp actually expose under the inbox and posts scopes? Determines whether Path A is days of work or a non-starter.
Q2 Who at Gen4 / PromoRepublic owns the MCP server, and can they commit to a stability window? Without ownership clarity, Path A is permanently fragile.
Q3 Are all 260 SGA practices' GBP locations claimed inside the Gen4Engage workspace, or only Gen4 inherited ones? Coverage gap. If non-Gen4 practices aren't onboarded, Path C may be required for those even if A works for Gen4.
Q4 Are we in scope for PromoRepublic's "Multi-Location" custom-pricing tier already, or do we need a procurement cycle? Path B is gated by commercial relationship. Knowing where we stand changes the timeline.
Q5 If we go Path C, who owns the conflict rule when both Content Engine and PromoRepublic want to reply to the same review? Avoids the dual-system race condition that breaks production for franchisees.

06Risks and non-obvious tradeoffs

Risk 1 — Google's 2026 review-reply moderation
Google began moderating review replies in early 2026 to prevent AI-generated spam from corrupting Place summaries. Both PromoRepublic-routed and direct-API-routed replies are subject. If we ship AI-drafted replies at scale, we need an internal review step (or a sufficiently conservative draft style) to avoid replies being silently filtered. This applies to every path, not just one.
Risk 2 — Path A is opportunistic
An undocumented MCP we did not commission can be changed or removed at any time without notice. Treat Path A as a low-cost win, not a load-bearing dependency. Path B or Path C is the durable layer behind it.
Tradeoff — UX ownership
Today PromoRepublic / Gen4Engage owns the franchisee experience. If we drive these actions from the Content Engine, we are also taking on the user-experience burden: notification design, draft-review queues, conflict resolution, analytics surfaces. Every workflow we move into the AI Dashboard becomes a workflow we are responsible for maintaining.
Tradeoff — Two systems writing to GBP
If Path C ships alongside an unchanged PromoRepublic, both systems are writing to the same GBP locations through different OAuth tokens. Google handles concurrent writes but our internal data model needs to know "who wrote this reply" so the activity log makes sense. Solvable, but it is design work, not just plumbing.

07Next steps

  1. Run the Gen4Engage MCP probe. Connect once, dump tools/list, share the output. Owner: Dakota · This week
  2. Confirm GBP coverage in Gen4Engage. Audit which of the 260 SGA practice locations are claimed and connected today. Owner: Korrine · Within 2 weeks
  3. Open the partner-API conversation with PromoRepublic. Email their multi-location sales team. Position the ask as "SGA with 260 locations exploring deeper integration; what does your partner API surface look like?" Owner: Sarah / Dakota · This week
  4. Define the conflict policy. Write a one-pager: who wins if both Content Engine and PromoRepublic try to reply to the same review? (Recommendation: Content Engine wins for AI-drafted replies, PromoRepublic wins for any franchisee-initiated manual reply.) Owner: Dakota · Before any Path C build
  5. Schedule the build decision. Reconvene once Q1 and Q4 are answered. Pick A, A+C, or C, and lock the build sprint. Owner: Dakota · 2 weeks out

Sources used