Enquire CRM Integration — Lead Lifecycle in the Operating Record
Purpose-built CRM for senior housing & care — bridged into the SeniorCRE operating record so lead → tour → application → bed assignment flows through one canonical resident lifecycle.
Capabilities
- Lead capture from web, phone, and referral
- Tour scheduling and follow-up cadence
- Application packet workflow
- Bed-assignment hand-off to operations
- Source attribution and ROI by campaign
- Family communication tracking
- Pipeline forecasting and conversion analytics
- Multi-community scoping
How it works
- Enquire account configuration — Confirm Enquire API entitlement, obtain credentials, and align tenant scoping.
- Stage and field mapping — Map Enquire pipeline stages and fields to the SeniorCRE canonical lead lifecycle.
- Webhook + bridge — Roadmap design intent: evaluate vendor-supported events, operator scope, freshness, reconciliation, and acceptance criteria.
- Validation exercise — Roadmap design intent: validate a bounded lead-to-move-in dataset before any operator-production acceptance decision.
Integration facts
- Interface basis — Vendor-documented design
- Current connection — Roadmap · not operator production
- Timing — Determined after validation scope
- CRM stages — Up to 9 configurable
Frequently asked questions
- Does the integration replace Enquire's CRM UI?
- Not by default. The operator may keep Enquire authoritative for sales records; a future SeniorCRE interface would govern how those records contribute to cross-domain decisions.
- How does attribution work?
- Source, campaign, and referrer travel with the lead record from first touch through tour, application, move-in, and lifetime revenue.
- Is multi-community supported?
- Yes. Each community scopes its own pipeline; portfolio rollups aggregate via the Entity hierarchy.
https://seniorcre.com/integrations/enquire