Answer the enquiry. Check the rules. Leave a result the team can use. Evarmont brings the phone conversation and its business outcome into one reviewable workflow.
An inbound call is resolved to the business that owns the phone number. The voice assistant uses configured locations, services and policies to understand the caller’s intent and determine the next step.
For a new enquiry, that may mean collecting context for a consultation. For an existing appointment, it may mean verifying booking access before making a change. Lead qualification is a structured intake workflow, not an unverified score or an automatic promise.
Service duration, resource availability, buffers, minimum notice and booking horizon shape the options a caller can receive. The backend validates the final start and end time and commits the booking before it is treated as confirmed.
Creation, rescheduling and cancellation use explicit transactions and idempotency protection. Requests to manage an existing booking follow access checks; knowing a booking identifier is not permission to change it.
Calendar mirrors, CRM contacts and team notifications have implemented adapters and connection settings. These integrations are in development and require provider setup and live verification before customer use.
A business can choose eligible connections by organization or location. An ambiguous or unavailable destination produces a refusal. Durable follow-through runs after the booking commits, so a notification failure does not erase a valid appointment.
Transfer requests and callback workflows give the assistant an escalation path when configured. A transfer request does not mean staff answered, and a callback is governed by consent, calling windows and bounded attempts.
Staff can review call history, appointments, customers and unresolved outcomes in the dashboard. A finished phone call and completed business work are always separate facts.
What happened, what is healthy, what needs attention, and what to do next. The console shows the call's transport status and its business outcome as two separate facts, because they are.
Built from the console's own components at the console's real scale, with a sample business. Not a screenshot.
Evarmont46% conversion · 6/13 calls booked
Call status describes the phone call. Business outcome describes what the call achieved. They are recorded separately.
Connections are checked on request, never guessed. When one fails, the console says what stops working and what to do.
Access was revoked at the provider. Reconnect to restore availability reads and appointment writes.
If disconnected: appointments will stop being mirrored and availability will no longer be read from this calendar. Existing bookings are unaffected.
A callback is dialed only inside your calling windows and only with a recorded consent basis. Without either, it waits and says why.
See where it can lead, and what your team can review afterward.
