Loading page
Loading page
Consult Engine sends the appointment state; a configured messaging workflow delivers the request.
Reviews & Reputation
Auto-send after visits
Completed-appointment events can trigger a configured messaging workflow.
Standard workflow template
The manifest documents the expected trigger, tags, and appointment states.
Integration readiness
Connection, configuration, and failed sync states stay visible to the clinic.
Receive a completed-appointment state
A supported scheduling or practice-management connection reports the appointment outcome used by the configured review workflow. No request should rely on an assumed visit status.
Apply the clinic's review rule
The workflow checks the documented trigger, location, and message settings before handing the request to the connected messaging system.
Send through the connected provider
The configured messaging provider delivers the clinic-approved request and review destination. Consult Engine supplies the event context and keeps the integration boundary clear.
Monitor the handoff
Clinic staff can review connection readiness and failed sync states. A failed external handoff stays visible instead of being counted as a sent request.
Post-visit requests
Start the configured request only after a verified completed-appointment state reaches the workflow.
Location-specific links
Route each clinic location to its approved public review destination when the connected workflow supports that mapping.
Consistent patient outreach
Use the same neutral request process for eligible completed visits rather than changing the request based on expected sentiment.
Failed-sync follow-up
Give staff a visible exception to investigate when appointment data or the messaging handoff is unavailable.
Only when a supported appointment state, clinic rule, and messaging integration are correctly configured. The workflow should not assume that a scheduled visit was completed.
The connected workflow sends patients to the clinic's configured review destination. Consult Engine supplies the appointment event and integration status.
The recommended workflow uses a consistent neutral request for eligible patients. Clinics should follow each review platform's policies and applicable rules.
The request is not presented as successfully sent. The clinic can review the readiness or failure state and use an approved fallback if needed.
Start with what is live, then add integrations and roadmap modules as they become ready.