Phone
Answer and route calls, capture voicemail context, qualify intent, and move eligible callers toward booking through the approved voice connection.
FRONT DESK OS / INQUIRY TO BOOKING
Answer and coordinate inbound questions across phone, text, website chat, approved social media messaging, web forms, and email—then move each inquiry to a booking, qualification, or explicit human handoff.
ONE FRONT DESK / EVERY APPROVED CHANNEL
Front Desk OS brings each connected channel into one attributable operating record. Channel providers are selected during implementation; consent, identity, delivery, and escalation rules remain visible.
Answer and route calls, capture voicemail context, qualify intent, and move eligible callers toward booking through the approved voice connection.
Respond inside consent, quiet-hour, and opt-out policy while preserving the complete customer-visible message history.
Answer from approved knowledge, collect required context, qualify, book, or request a human inside the website experience.
Respond to supported social media messages through approved connections and route public or unsupported interactions to a person.
Read inbound requests, prepare or send approved replies, collect missing information, and assign the next operational state.
Acknowledge submissions, create the inquiry record, apply routing and qualification rules, and notify the correct owner.
THE OPERATING WORKFLOW
The system never collapses everything into “processed.” Each inquiry remains answered, waiting, booked, suppressed, escalated, failed, or closed with a reason.
Capture the channel, contact, location, message, source, and consent context.
Use approved taxonomy and show the source message supporting the decision.
Use published knowledge or collect the required fields for that service.
Confirm a valid slot or route the exception to a named person or team.
Show what reached the customer, what failed, and who acted.
APPROVED KNOWLEDGE / ROUTING / REVIEW
Published knowledge can support routine responses. Conflicting, sensitive, expired, or unsupported information moves to review with the source and customer consequence attached.
Only published, effective, scoped answers support automatic response.
Required fields and source messages remain visible beside the outcome.
Channel and purpose permissions are checked before customer-visible action.
A person can take control without duplicate automated messages.
STRONG FIT
NOT THE FRONT DESK BOUNDARY
FRONT DESK SYSTEMS REVIEW
Bring the channels, booking rules, locations, ownership, and exceptions. The review identifies the correct first operating workflow.
Review your front desk