Skip to main content

Integrations

AI receptionist workflows for your medical spa stack

Eva fits around the booking, calendar, and CRM workflows medical spas already use, so AI coverage can support the existing operating model.

How to use this library

Keep the AI receptionist close to the systems your team already uses.

Front desk automation works better when it follows the practice's actual calendar, booking, and CRM workflows. These integration pages explain how Eva can fit around common medical spa operating stacks without asking the team to rebuild every process first.

8

focused pages in this cluster

24/7

phone coverage across workflows

Voice + SMS

follow-up beyond the first call

Front desk workflows

Explore the integrations library

Book a demo

Before you choose

What to verify in an integration workflow

Use these criteria before booking a demo, comparing vendors, or changing your front desk workflow.

  • Can appointment offers respect live availability, provider rules, and location-specific workflows?
  • Can call outcomes and patient context reach staff or follow-up systems?
  • Can the setup evolve as the practice moves from simple calendars to practice-management software?

FAQ

Questions operators ask about this cluster

Does Eva replace practice-management software?

No. Eva sits around the front desk communication workflow and can connect with scheduling, calendar, and CRM systems where appropriate.

Can different locations use different systems or rules?

Yes. Multi-location workflows can use different hours, services, providers, and escalation paths by location.

What if the practice changes systems later?

Eva is built around booking-provider abstractions, so the front desk workflow can evolve as the operating stack changes.