Skip to content

AI receptionist

Your front-desk rules, in a conversation.

Understand what the receptionist can decide, which actions need setup and where a person remains responsible. Start with a useful intake, then add supported scheduling or routing.

01 · Configure

A receptionist that knows your approved information.

Your saved greeting, services, policies and qualifying questions guide the call. Unknown answers should become a staff question—not an invented business fact.

02 · Act within limits

Booking and routing need more than a voice.

Configure appointment types and Callenova availability for supported scheduling. Starter and Growth transfers need valid US or Canada destinations; test your main-line and department fallback. Direct transfers do not guarantee an answer or warm handoff. If an action fails or needs approval, collect the request for staff review.

03 · Review

See what was requested and what actually happened.

Review available call records, transcripts and summaries. A requested time and a confirmed booking are different outcomes; the record should make that distinction clear.

Appointment business · Incoming inquiryIllustrative example

CALLER · Jordan

“Could I arrange a consultation next Tuesday afternoon?”

RECEPTIONIST

“I can record your preferred time and consultation request. What is the best way for the team to reach you?”

Captured details

Caller
Jordan
Service
Consultation
Day
Tuesday
Preference
Afternoon

Consultation request

The team reviews the request and confirms the next step with Jordan.

Example only. No call placed, booking confirmed or notification sent.

Connection boundaries

Know which calendar the call uses.

Voice scheduling

Voice uses the availability configured in Callenova. Google Calendar supports dashboard and public-booking availability and appointment sync; Google busy data does not drive voice availability.

Other tools

CRM events use configured webhooks or Zapier. Outlook is coming soon. Fresha and Booksy store booking links rather than native booking availability.

Before the first customer call

Give it your playbook.

Save your business details, knowledge, hours and time zone. Set booking availability or transfer destinations only for the actions you intend to use. Complete activation and review a test call.

Complete activation and test your greeting, intake and fallback. Verify forwarding with your carrier; voice forwarding does not forward texts.

Review setup

Know where people take over.

Booking requires a supported plan and configured availability. Requests and callbacks are not automatically confirmed bookings. Call records and recordings depend on availability and applicable consent requirements; these examples do not certify a live provider result.

Lite covers configured business hours. Starter and Growth include 24/7 inbound answering; scheduling requires a supported plan. Lite takes messages and does not transfer; transfers go only to numbers you set. If a person is unavailable, capture a callback request; do not promise an immediate response.

Ask about your requirements

Need a simpler capture-first workflow?

Explore coverage and message intake without assuming every request can be resolved during the call.

AI answering service →

Check fit before you subscribe.

Review included minutes, overages and eligibility on Pricing. For an unusual workflow or a setup question, contact the team; existing customers can use dashboard support.

Talk through your requirements →

Test the conversation before you choose.

Try a consent-based demo call, or compare the plan requirements.