Loading page
Consult EngineRetainNeeds integration
Follow up with the context that created the lead
Consult Engine sends structured fields and event tags while your connected system handles message delivery.
Treatment-Aware Nurture
- Versioned manifest
- Treatment-aware fields
- Visible sync health
What it does.
Versioned manifest
Required tags, fields, triggers, and appointment states are documented in one checklist.
Treatment-aware fields
Treatment interest, visualization time, preview status, and booking URL travel with the lead.
Visible sync health
Failed contact syncs are surfaced for retry instead of silently losing nurture.
How it works.
1
Define the handoff fields
The integration manifest lists the treatment, preview status, booking URL, tags, and appointment events the connected system expects. That shared checklist keeps field names and triggers consistent.
2
Connect the delivery system
Consult Engine sends the configured context to the clinic's CRM or messaging provider. The connected provider, not Consult Engine by itself, delivers the email or text workflow.
3
Trigger follow-up from a real event
A consented lead, booking state, or other configured event can start the matching workflow. Treatment context helps the clinic continue the conversation the patient already began.
4
Keep failures visible
Connection and delivery handoffs expose readiness or failure states for clinic follow-up. A failed sync is not silently presented as a message that reached the patient.
Useful in everyday workflows.
Visualizer lead follow-up
Pass the treatment a patient previewed to the connected workflow so outreach can refer to the interest they already expressed.
Booking-link delivery
Include the clinic's configured booking URL when a direct scheduling write is unavailable or the workflow calls for patient self-scheduling.
After-hours handoff
Carry captured intent into the clinic's next-day workflow so the team can see the source and requested treatment when it follows up.
Integration recovery
Use visible sync status to identify records that need a retry or a manual handoff instead of assuming every external action succeeded.
What you get.
- Connected system owns message delivery
- Clinic-specific readiness and failure visibility
FAQs
Questions about Nurture Workflows.
No. Consult Engine supplies configured fields, tags, and events, while the connected CRM or messaging system owns message delivery.
Configured fields can include treatment interest, visualization time, preview status, booking URL, and approved workflow tags. Patient data should stay limited to the authorized operational purpose.
The integration exposes a failure state for retry or manual follow-up. The product does not label a failed handoff as a successful delivery.
The underlying pattern can be reused, but field mappings, booking links, permissions, and message content still need clinic-specific configuration and approval.
More in Retain
Works with the rest of the platform.
Ready to connect
the workflow?
Start with what is live, then add integrations and roadmap modules as they become ready.