ELAYGENT does not claim "full review management" in marketing because parts of that phrase are not literally true today. This page lists exactly what we do, what is bounded by Google or Yelp upstream limits, and what we do not do at all.
Yelp Fusion exposes at most 3 review excerpts per business. Google Places API exposes up to ~5 most-helpful reviews per place. These are platform limits — no review-management product can read more than the upstream API exposes.
Google review snapshot ingestion
Google
Shipped (with upstream limits)
Pulls the most-helpful reviews and aggregate rating for a configured Google Place ID on a schedule, upserts into the shared `ExternalReview` table.
Upstream / config limits
Google Places API v1 returns at most ~5 most-helpful reviews per place per request — this is a Google product limit, not an ELAYGENT cap. Full review history is not exposed by this API.
Per-location, config-gated by `Location.googlePlaceId` and `Location.googleIngestionEnabled`. Only runs when a Google Places API key is configured.
What it does NOT do
Not a complete Google review archive. The Places API does not return one.
Does not post review replies. (See 'Review reply workflows' row.)
Does not include Google Business Profile owner-side metrics (insights, photos, posts) — those require GBP OAuth, which is on the roadmap, not shipped.
Yelp review snapshot ingestion
Yelp
Shipped (with upstream limits)
Pulls the bounded review snapshot exposed by Yelp Fusion's Business Details endpoint for a configured Yelp business ID.
Upstream / config limits
Yelp Fusion returns at most 3 reviews per business per request, and each review's `text` is truncated to roughly 160 characters. This is a Yelp product limit, documented in their API reference.
Per-location, config-gated by `Location.yelpBusinessId` and `Location.yelpIngestionEnabled`. Only runs when `YELP_API_KEY` is configured.
What it does NOT do
Not a complete Yelp review archive. Yelp does not expose one publicly.
Reviews are excerpts, not full text — full text is only viewable on Yelp itself.
No Yelp ad/campaign analytics.
Does not post review replies. (See 'Review reply workflows' row.)
Outbound review request (SMS + email)
ELAYGENT
Shipped
After a completed appointment, ELAYGENT can send the patient a private-feedback link by SMS and/or email. Patients who give positive feedback are funneled to the clinic's public review URL; patients who give negative feedback are routed back to clinic staff for direct follow-up.
Upstream / config limits
Honors the per-phone SMS opt-out list — opted-out numbers are not contacted.
Requires the public application URL to be configured so the feedback link resolves correctly.
One request per appointment per channel; not a drip campaign.
What it does NOT do
Does not gate negative reviews from being posted publicly. The patient is always free to post wherever they want — we route negative feedback to staff for service recovery, not to suppress it.
Does not promise a specific lift in star rating. Outcomes depend on baseline service quality and are not guaranteed by code.
Review reply workflows
Any provider
Not implemented
ELAYGENT does not currently post replies to Google or Yelp reviews on the clinic's behalf. Replies must be authored by clinic staff in the respective platform UI.
What it does NOT do
No Google review replies via API.
No Yelp review replies (Yelp Fusion does not expose a reply endpoint).
No AI-drafted reply suggestions UI today. This is a candidate for a later release; it is not shipped.
Google Business Profile OAuth (owner-side)
Google
Not implemented
GBP OAuth would unlock owner-side data (insights, posts, photo uploads, reply API access) for a verified Google Business Profile. ELAYGENT has not implemented the OAuth flow yet.
What it does NOT do
Today we read public review snapshots through the Places API only; the clinic does not need to grant ELAYGENT access to their GBP.
Once OAuth ships, it will be opt-in per location, not silent.
Cross-provider reputation analytics
ELAYGENT
Shipped
Reviews ingested from Google and Yelp land in the shared `ExternalReview` table and are exposed in the `/intelligence` reputation audit so admins can see rating, volume, and trends across providers in one place.
Upstream / config limits
Analytics are only as complete as the underlying ingestion. Yelp shows 3 excerpts; Google shows up to 5 most-helpful — the analytics inherit those limits.
Sentiment classification, if shown, is heuristic — not a clinical or legal judgment about the review content.
What it does NOT do
Does not include reviews from sources we do not ingest (Healthgrades, Vitals, RealSelf, Facebook, etc.).
Does not produce a 'reputation score' that anyone outside ELAYGENT recognizes as a standard.