How to Bound a Service-Specific Review Request Campaign
Everyone who enquired about or booked a service is not automatically part of an appropriate review-request audience. Care Journey defines one eligible completed-experience cohort, applies exclusions, prepares a neutral approved message and sets the release cutoff and destination. The clinic can invite feedback about a named service without selecting people for expected praise or exposing unnecessary service detail.
Everyone connected to a service is not one eligible cohort
A service lead asks to invite every recent contact associated with a named service. The list contains people who only enquired, people whose bookings changed, people whose experience is still active and people with completed eligible experiences. It may also contain sensitive service detail that is unnecessary for a neutral invitation. Releasing the list as received would turn a campaign brief into an unexamined targeting decision.
The campaign's first job is to state what qualifies as the approved service experience and what must remain outside the cohort. Satisfaction, a predicted rating, complaint status and willingness to recommend cannot decide admission. Once the cohort rule is defensible, the campaign can freeze its message and hand candidate records to the separate infrastructure that checks current permission, suppression, duplicate state, destination and minimum data at release.
Use a campaign admission tree before the relay sees a record
| Decision Branch | Admit When | Exclude or Hold When |
|---|---|---|
| Named Service | The clinic-approved record identifies the in-scope service experience | The record is an enquiry, unrelated service or unclear association |
| Experience State | The approved eligibility condition is complete and current | The episode is incomplete, cancelled, disputed as a data state or otherwise outside the rule |
| Neutrality | Admission is independent of satisfaction or expected rating | Selection uses praise, complaint status, survey sentiment or willingness to recommend |
| Data Minimum | Only the fields required to decide and release are present | Sensitive detail is unnecessary, identity is uncertain or the record is over-disclosed |
| Campaign Boundary | The record falls within the frozen service and cutoff | The service, source, date boundary or intended destination does not match |
| Release Readiness | Campaign evidence is ready for the existing relay | Permission, suppression, duplicate or destination evidence must be checked or resolved by its owner |
Service-specific does not mean condition-specific targeting. The cohort can be defined around the clinic's approved evidence that the named service experience occurred, while avoiding diagnosis, treatment detail or a sensitive characteristic that is unnecessary to the invitation. Exact data and legal boundaries require the clinic's competent review; the campaign page does not decide them for every context.
An exclusion is an accounted decision, not a failed target. A record outside the named service, outside the cutoff, missing the eligibility evidence or carrying unresolved permission can close or hold without being forced into the release set. That is safer than treating every withheld invitation as lost volume.
Freeze the episode, then make a clean handoff
- Name the service experience and the clinic evidence that makes it eligible. Keep the rule independent of satisfaction, rating expectation or complaint status.
- Declare the campaign source, cutoff and exclusions. Separate enquiries, changed bookings, incomplete episodes and unclear records from approved completed experiences.
- Reduce the candidate record to the information needed for admission and release. Route unnecessary sensitive detail out of the working set.
- Approve neutral message wording, business identity and the intended review destination. Do not ask for a particular rating, wording or revision.
- Confirm that the selected channel is approved for the campaign context. Permission, opt-out and suppression evidence remain owned by the relevant channel and clinic controls.
- Submit eligible candidate records to the automated review-request workflow. That existing relay decides release, held or closed state using current event, permission, suppression, duplicate, destination and payload evidence.
- Account for admitted, excluded, held, handed-off and unresolved records at the campaign cutoff. Close without searching for a matching public reviewer.
- Route exceptions to the owner of the missing evidence, then preserve the campaign version rather than reopening it as an indefinite lifecycle programme.
The handoff should remain small in meaning even when clinic systems are complex. The campaign supplies its cohort decision, message version, destination and cutoff. The relay supplies reusable execution controls. CRM and lead management may hold the underlying operational record, while WhatsApp or another approved channel may apply its own permission and messaging rules. This page does not merge those systems into a new automation service.
What Service-Specific Review Request Campaign Covers
- This service covers one bounded review-request campaign for an eligible cohort connected to a named service experience.
- Eligibility policy, automated workflow engineering, public review outcomes and ongoing reputation management remain separate.
- The campaign keeps invitations within the eligible cohort; it cannot determine who responds, the rating or whether a platform publishes the review.
Even a neutral request can change the composition of what becomes observable. A (hospitality-platform natural experiment) found that solicitation altered review activity and content patterns. Those findings are not a healthcare, Google or UAE performance estimate. They support only the narrower rule that collection context travels with later interpretation and that this campaign cannot promise an organic-looking or representative review corpus.
Publication remains external. Google's (missing-and-delayed review guidance) describes policy checks, profile changes and other reasons a review may not appear as expected. The campaign should retain its handoff state and leave the later public identity unknown instead of labelling a missing review as a staff failure or a person as non-responsive.
Check the cohort rule before approving the message
- Can the clinic name the service experience without exposing unnecessary health detail?
- Would a critical and a favourable experience enter under the same eligibility rule?
- Are enquiries, changed bookings, incomplete episodes and unclear records handled explicitly?
- Is the message neutral, destination-specific and free of pressure or requested wording?
- Will the existing relay recheck current permission, suppression, duplicate and destination evidence?
- Can the campaign close without learning who later posts publicly?
If any answer is unknown, the campaign has found a boundary to resolve, not a reason to lower the threshold. The questions below clarify fit without defining commercial quantities, cadence or results.
Its admission rule is bound to an approved experience with the named service, and its message, destination, exclusions and cutoff are frozen for that episode. It is not a reusable rule for every clinic interaction.
No. Cohort admission should not use predicted sentiment, complaint status or willingness to praise. Google prohibits discouraging negative feedback and selectively soliciting positive reviews.
The campaign prepares an eligible, versioned candidate set for handoff. The existing release relay owns current permission, suppression, duplicate, destination and payload checks and may release, hold or close a record.
It closes when admitted, excluded, held, handed-off and unresolved records are accounted for at the cutoff. Publication, rating movement and business impact remain external and are not required for closure.
Discuss Service-Specific Review Request Campaign for Your Clinic
Tell Care Journey about the named service, completed-experience definition, exclusions, approved neutral message, destination and cutoff. We will assess whether the proposed cohort is eligible and ready for one bounded request campaign and explain the most practical next step.
Useful starting evidence
Bring the service eligibility rule, a sample candidate-record shape without unnecessary personal detail, current permission and suppression owners, the intended platform destination and the message approval route. Unknowns should remain named unknowns.