Rivercrest questions, answered.

No. Rivercrest is designed to support clinic teams by handling repetitive administrative communication, follow-up, qualification, scheduling support, and record updates. Clinic staff remain responsible for conversations requiring clinical knowledge, judgment, empathy, or personal attention.

Rivercrest is intended for administrative communication. It can provide clinic-approved information about services, scheduling, preparation, pricing ranges, or general processes when configured to do so. Clinical, sensitive, urgent, or patient-specific medical questions should be escalated to qualified clinic staff.

Rivercrest can connect with supported CRM, calendar, phone, messaging, and lead-generation systems. Integration requirements, limitations, data access, and implementation scope are reviewed before launch.

Yes. Depending on the selected implementation, Rivercrest can support approved outbound calling and messaging for new inquiries, dormant leads, missed calls, no-shows, cancellations, and reactivation campaigns. Exact capabilities depend on the clinic's approved workflows, integrations, communication volume, and applicable requirements.

Rivercrest can flag, route, transfer, or assign conversations according to clinic-defined rules. Staff can be notified when a conversation is urgent, sensitive, complex, high-value, clinically specific, or when the patient requests human assistance.

Timing depends on clinic size, workflow complexity, integrations, communication channels, and approval requirements. A detailed implementation plan is provided before launch.

Yes. Multi-location workflows, reporting, routing, and visibility can be configured for qualifying clinic groups.

Supported configurations may include phone, SMS, email, website chat, forms, calendar systems, and CRM workflows. Exact channel availability depends on the clinic's implementation.

No. Rivercrest connects communication, automation, booking, follow-up, visibility, and operational intelligence. It may work with an existing CRM or include a configured CRM layer.

Pricing depends on package, clinic size, locations, communication volume, integrations, and implementation scope. Package structure is previewed on the pricing page and confirmed during a demo.

Communication usage (such as call minutes and messaging) may vary by volume and configuration. Usage considerations are reviewed during implementation planning.

Workflows, messaging, qualification rules, and escalation paths are configured with the clinic and reviewed before launch. Updates can be made as the clinic's needs change.

Patient information is handled according to the clinic's configuration and applicable agreements. Data access and handling are reviewed during implementation.

Custom voice options can be available through selected implementations, depending on configuration and requirements.

Conversation intelligence can review calls and messages for objections, response quality, escalation needs, and next-step recommendations, based on the clinic's approved configuration.