Call admission
The AI voice agent evaluates every inbound call before the caller hears a greeting. This article explains how to configure the limits and rules that govern which calls the agent accepts, and what callers hear when a call is not admitted.
Audience: Center administrators who configure the AI voice agent for their center.
On this page
- Before you begin
- Steps
- Understand admission checks
- Set the concurrent call limit
- Set the daily call limit
- Configure call transfer rules for anonymous callers
- Manage the blocked caller list
- Configure inbound call settings
- Configure call recording
- Configure call transfer settings
- Configure call handling schedule
- Configure inbound settings
- Configure feedback collection
- Tips
- Troubleshooting
- Related articles
Before you begin
- Onboarding with Zenoti must be complete and your agent must exist in the dashboard before you can adjust these settings.
- You must have edit access to the AI Receptionist dashboard. If the dashboard displays a read-only view, contact your administrator.
- Understand the five guest states the agent uses to classify callers β see Guest states β before adjusting admission rules, because some checks depend on whether a phone number resolves to a guest profile.
Steps
Understand admission checks
Before a caller hears anything, the agent runs admission checks in order. A call ends as soon as any check fails. The checks are:
- Agent status β The call is rejected silently if the agent is inactive (status is Offline). No audio plays.
- Anonymous caller β If the caller withheld their number and no call transfer is configured, the agent plays: "Thank you for calling. Our team will call you back as soon as possible." The call then ends. If a call transfer is configured, the call is transferred instead of ended.
- Blocked caller β If the caller's number is on the agent's blocked list, the call is flagged in the call log and continues normally. The caller is not notified and the call is not ended.
- Concurrent call limit β If the number of calls currently in progress has reached the configured limit, the call is rejected. No audio confirmation of the reason is played to the caller.
- Daily call limit β If the agent has already handled the maximum number of calls for the current day, the caller hears: "We've reached our maximum number of calls for today. Please try again tomorrow." The call then ends.
Note: Admission checks run before greetings, guest identification, or any booking flow. A caller who passes all checks then hears the agent's configured greeting.
Important: The concurrent call limit and daily call limit both default to unlimited. A caller on the blocked list is flagged but their call continues β the blocked list does not end or redirect calls.
Set the concurrent call limit
The concurrent call limit controls how many inbound calls the agent handles simultaneously. When the limit is reached, additional callers cannot connect until an active call ends.
- In the AI Receptionist dashboard, select your agent to open its settings.
- Locate the Concurrent call limit field.
- Enter the maximum number of simultaneous calls you want the agent to handle, or leave the field at its default to allow unlimited concurrent calls.
- Select Save.
Tip: If your center receives unpredictable call bursts, consider setting a concurrent limit that matches your typical peak capacity rather than leaving it unlimited. Review the Call Logs page regularly to identify dropped calls.
Set the daily call limit
The daily call limit caps the total number of calls the agent handles in a single calendar day. Callers who reach the agent after the limit is exhausted hear the daily-limit message and the call ends.
- In the AI Receptionist dashboard, select your agent to open its settings.
- Locate the Daily call limit field.
- Enter the maximum number of calls per day, or leave the field at its default to allow unlimited daily calls.
- Select Save.
Important: The daily limit resets at the start of each calendar day in your center's configured time zone. Callers who are turned away do not receive a callback automatically β your front desk team must follow up manually if needed.
Worked example: A center sets a Daily call limit of 200 calls. By 4 PM, 200 calls have been handled. The next caller at 4:01 PM hears: "We've reached our maximum number of calls for today. Please try again tomorrow." At midnight the limit resets and the agent resumes accepting calls normally.
Configure call transfer rules for anonymous callers
When a caller withholds their number, the agent cannot identify them or look up a guest profile. If no call transfer is configured, the call ends with the anonymous-caller message. If a call transfer destination is configured, the agent transfers the call to that number instead.
To route anonymous callers to your front desk rather than ending their call:
- In the AI Receptionist dashboard, select your agent.
- Navigate to the Handover rules section (labeled Handover to human in the dashboard).
- Enable Handover to human for business hours, after hours, or both as appropriate.
- Enter the destination in the Handover phone number field.
- Select Save.
With a call transfer configured, anonymous callers are transferred rather than heard the "call you back" message.
Note: Call transfer configuration is covered in full in Greetings and opening message and the Capabilities settings article. The steps above address only the admission-check interaction with anonymous callers.
Manage the blocked caller list
Callers on the blocked list are flagged in the call log, but their calls are not rejected β the call continues normally. The blocked list is a monitoring tool, not an admission gate.
To add a caller to the blocked list:
- In the AI Receptionist dashboard, open Call Logs.
- Locate the call from the number you want to block.
- Open the call detail and select Block User.
- Confirm by selecting Block User in the confirmation dialog.
The number is added to the blocked list. Future calls from this number are flagged as Blocked in the call log. The caller does not hear any indication that they are on the list.
To remove a caller from the blocked list:
- In the AI Receptionist dashboard, open Call Logs.
- Locate a call from the blocked number.
- Open the call detail and select Unblock User.
- Confirm by selecting Unblock User in the confirmation dialog.
Important: The blocked list flags calls for your team's awareness β it does not prevent the agent from answering or interacting with the caller. If you need to prevent a caller from reaching the agent entirely, use your telephony provider's call-blocking features before the call reaches the AI voice agent.
Configure inbound call settings
The Settings screen's Inbound call section controls which calls the AI voice agent takes and when it is active.
- Open AI Receptionist in HyperConnect, then go to Settings.
- Select the Inbound call tab.
Who should AI Receptionist talk to?
Under Who should AI Receptionist talk to?, select one option:
- New customer only β the agent answers calls from callers whose phone number does not match any existing guest record.
- Existing customer only β the agent answers calls from callers whose phone number matches an existing guest record.
- Both β the agent answers calls from all callers regardless of guest state.
- None β the agent does not answer any calls. Use this option to pause the AI voice agent without taking it offline entirely.
Note: The options on this screen use the word "customer" to match the product UI. Throughout the rest of AI Receptionist, the equivalent term is "guest".
Should AI Receptionist handle
Under Should AI Receptionist handle, select one option:
- All incoming calls β the agent answers every inbound call routed to it.
- Only the calls missed by your front desk β the agent answers only calls that your front desk did not pick up.
If you selected All incoming calls, a slider appears below the options. Use the What percentage of your incoming calls would you like AI Receptionist to handle autonomously? slider to set the share of inbound calls the agent handles. At 100%, the agent takes every call; at lower values, a proportional share is passed to your front desk instead.
Note: The percentage slider is not available when Only the calls missed by your front desk is selected.
When should AI Receptionist be active to handle calls?
Under When should AI Receptionist be active to handle calls?, select one option:
- 24/7 (All Day) β the agent is active at all times.
- During business hours β the agent is active only when the center is open.
- Outside business hours β the agent is active only when the center is closed.
- Custom schedule β the agent follows a schedule you define.
If you selected Custom schedule, configure the schedule:
a. Set the Start Date and End Date for the schedule window.
b. Select a Day and enter the Start Time and End Time using 24-hour format (
HH:MM).c. Select a Recurrence pattern for the day.
d. Select + Add Recurrence to add additional days and time windows.
e. To remove a day, select the remove control next to that entry.
Select Save to apply your inbound call settings.
Configure call recording
Call recording is turned on by default for each agent and can be turned off individually.
- Open AI Receptionist in HyperConnect, then go to Settings.
- Locate the Call recording section.
- Review the toggle labeled Turn on the toggle if you want to record the call.
- To disable recording for this agent, turn the toggle off.
- Select Save.
Important: Call recording settings apply per agent, not across all agents. If your organization runs more than one AI voice agent, verify the recording setting on each agent separately.
Configure call transfer settings
The call transfer section controls what the AI voice agent does when a caller requests a person or when the agent cannot complete the request on its own.
Set the handover action for business hours
Open AI Receptionist in HyperConnect, then go to Settings.
Under Handover rules, locate the Business Hours row.
Select the action the agent should take when a call transfer is requested during business hours:
- Handover to human β the agent forwards the call to a staff member.
- Take a note β the agent records the caller's request and ends the call. A note is added to the guest record for your team to follow up.
Set the handover action for outside business hours
Locate the Non-Business Hours row.
Select the action the agent should take when a call transfer is requested outside business hours:
- Handover to human β the agent forwards the call to a staff member.
- Take a note β the agent records the caller's request and ends the call.
Note: When Take a note is selected for both business hours and non-business hours, the agent never transfers a call. It records a note for every transfer request and your team follows up after the call.
Enter the handover phone number
- In the Handover phone number field, enter the phone number that inbound transfer calls are forwarded to. Include the country code (for example,
+14155551234).
Important: If the number you enter is the same number that AI Receptionist calls are forwarded from, a call loop will occur. The dashboard displays a warning when this condition is detected.
Configure handover messages
In the Handover greeting field, enter the message the agent plays to the caller before transferring them during business hours β for example, "Please hold while I connect you with a member of our team."
If your agent's non-business-hours action is set to Handover to human, enter a message in the corresponding field for the message played outside business hours.
If your agent's action is set to Take a note, enter a message in the Take note greeting field β for example, a message explaining that the team will follow up.
Optionally, enter additional instructions in the Handover message field. These instructions are appended to the agent's default transfer rules and let you specify situations where the agent should transfer calls beyond the four built-in triggers.
Select Save.
Tip: The agent initiates a call transfer automatically β without the caller requesting it β when any of the following occurs: the caller explicitly asks to speak with a person, the request is outside the agent's capabilities (such as membership purchases or refunds), the caller rejects three or more suggested appointment time slots, or an internal action fails. You do not need to configure these triggers; they are always active.
Worked example
Scenario: A center is open Monday through Saturday, 9 AM to 7 PM. The owner wants the AI voice agent to handle all missed calls from both new and returning guests during those hours, record every call, and transfer any caller who requests a person to the front desk phone during business hours. Outside business hours, the agent should take a note instead of transferring.
The following table shows the configuration for this scenario. Enter these values in the Settings screen as described in the sections above, then select Save.
| Setting | Value |
|---|---|
| Who should AI Receptionist talk to? | Both |
| Should AI Receptionist handle | Only the calls missed by your front desk |
| When should AI Receptionist be active to handle calls? | Custom schedule |
| Custom schedule days | Monday β Saturday, 09:00 β 19:00 |
| Call recording | On (default) |
| Business Hours β action | Handover to human |
| Handover phone number | +14155550100 |
| Handover greeting | "Please hold while I connect you with our front desk." |
| Non-Business Hours β action | Take a note |
| Take note greeting | "Our team is currently unavailable. I'll pass your message along and someone will be in touch during business hours." |
With this configuration, the AI voice agent is active only during the custom schedule window, handles only missed calls from all guest types, records every call, forwards transfer requests to the front desk while the center is open, and leaves a note for after-hours transfer requests.
Configure call handling schedule
When you click Go Live, the AI voice agent displays a schedule configuration dialog before the agent goes live. Use this dialog to define who the agent talks to, which calls it handles, and when it is active.
Who should AI Receptionist talk to?
Select the guest types the agent is permitted to assist:
- New customer only β the agent handles calls only from callers who have no existing guest profile.
- Existing customer only β the agent handles calls only from callers whose phone number matches an existing guest profile.
- Both β the agent handles calls from all callers regardless of guest history.
Should AI Receptionist handle
Select which calls the agent intercepts:
- All incoming calls β every inbound call routes to the agent. When this option is selected, a slider appears so you can set what percentage of incoming calls the agent handles autonomously.
- Only the calls missed by your front desk β the agent answers only after your front desk does not pick up.
Note: When a phone tree is published with an AI Receptionist node, call routing is managed through the phone tree. The agent cannot transfer calls to a human when it is set to handle missed calls only; instead, it captures a note for every call that requires follow-up.
When should AI Receptionist be active?
Select when the agent is available to answer calls:
- 24/7 (All Day) β the agent is active at all times.
- During business hours β the agent is active only within your center's configured business hours.
- Outside business hours β the agent is active only outside business hours.
- Custom schedule β the agent is active during a date range and specific recurring time windows you define.
Set a custom schedule
When you select Custom schedule, two additional fields appear:
Enter a Start Date using the format
YYYY-MM-DD.Enter an End Date using the format
YYYY-MM-DD. The end date must be after the start date.Under Recurrence, select + Add Recurrence to add one or more active time windows.
For each recurrence, configure the following:
- Day β select the day of the week from the dropdown.
- Start Time β enter the time in
HH:MM(24-hour) format. The start time must be before the end time. - End Time β enter the time in
HH:MM(24-hour) format.
Repeat step 3 for each additional day or time window.
Tip: To remove a recurrence entry, select Remove Day next to the row you want to delete.
Configure inbound settings
Inbound settings control how the agent handles specific situations that arise during or after an inbound call. To reach these settings, open AI Receptionist in HyperConnect, go to Settings, and select Inbound call.
Deposit and card-on-file link expiry
When your center collects deposits or requires a card on file, the agent sends a secure payment link to the guest during booking. If the guest does not act on the link before it expires, configure what happens to the reservation:
- Keep reservation β the appointment remains in the system. Your front desk can follow up to collect payment.
- Cancel reservation β the appointment is automatically cancelled.
Set each behavior independently:
| Link type | Setting | Options |
|---|---|---|
| Deposit link | What happens when the deposit link expires unused | Keep reservation / Cancel reservation |
| Card-on-file link | What happens when the card-on-file link expires unused | Keep reservation / Cancel reservation |
Select Save after making your changes.
Note: Payment links are always delivered via SMS regardless of other guest detail collection settings. If the guest is calling from a landline or the SMS cannot be delivered, the agent follows your configured call transfer rules instead of sending a link.
Configure feedback collection
The Feedback Collection section controls whether the agent sends a post-call feedback request by SMS after inbound calls. To reach this section, open AI Receptionist in HyperConnect, go to Settings, and scroll to Feedback Collection.
Enable feedback collection
Toggle Enable Feedback Collection on to activate post-call feedback SMS.
The description reads: Send a feedback SMS after incoming AI Receptionist calls where the guest manages their appointment via AI Receptionist.
When the toggle is on, the Feedback Message field appears.
Feedback Message
Enter the message text that the agent sends to the guest after an eligible call. The field is limited to 200 characters.
Worked example: A center enables feedback collection and enters the following message: "Hi, thank you for calling. Please rate your experience: [link]. Your feedback helps us improve. Reply STOP to opt out." At 97 characters, this fits well within the 200-character limit and includes an opt-out instruction.
The feedback SMS is sent only when all of the following conditions are met:
- Feedback collection is enabled for the organization and the center.
- The call was a real inbound call with a caller phone number (test calls are excluded).
- The guest has opted in to transactional SMS messages.
- A booking was confirmed during the call.
- No feedback SMS has been sent to this guest in the previous 24 hours.
- No feedback SMS has already been sent for this specific call.
If any condition is not met, no feedback SMS is sent for that call.
Select Save after configuring the feedback message.
Tips
- Leave limits unlimited during initial deployment. When you first go live, leave both Concurrent call limit and Daily call limit at their defaults. Monitor call volume for two weeks using the Call Logs page before introducing limits, so you set values based on actual traffic rather than estimates.
- Set the daily limit above your historical peak. If your call log shows a maximum of 150 calls on your busiest day, set the daily limit to at least 180 to avoid cutting off legitimate callers on unexpectedly busy days.
- Configure a call transfer for anonymous callers before going live. Centers that handle inbound calls from landlines or privacy-protected numbers should configure a call transfer destination so those callers reach a person rather than hearing the anonymous-caller message and disconnecting.
- Review flagged calls weekly. The Blocked flag in call logs is useful for spotting repeated unwanted calls from the same number. If a pattern appears, consider addressing it at your phone carrier level.
- Concurrent and daily limits are independent. Reaching the daily limit does not affect the concurrent limit, and vice versa. Both checks must pass for a call to be admitted.
Troubleshooting
Callers report they heard "We've reached our maximum number of calls for today" but the limit was not intentionally set.
The daily call limit was set to a low value and was reached. Check the Daily call limit field in the agent settings. If it shows a value that does not match your intended configuration, increase it or remove the limit. If the field shows unlimited, contact Zenoti Support β the agent may have encountered an internal configuration issue.
Anonymous callers report they heard the "call you back" message but you expected them to be transferred.
The call transfer is either not configured or not enabled for the relevant time period (business hours or after hours). Verify that Handover to human is enabled and that a valid Handover phone number is entered. If after-hours callers are affected, confirm that after-hours call transfer is also enabled.
A caller you blocked is still able to interact with the agent normally.
This is expected behavior. The blocked list flags the call in your Call Logs but does not prevent the agent from answering. To prevent the caller from reaching the agent, use your telephony provider's call-blocking or caller-rejection features.
The agent is inactive and callers are not hearing any message.
When the agent status is Offline, admission fails silently β no audio plays and the call ends without explanation. This is by design. If you want callers to hear a message when the agent is unavailable, configure a fallback at your telephony or phone tree level before the call reaches the AI voice agent.
Calls appear to be dropping at high volume even though no limit is configured.
The concurrent call limit and daily call limit both default to unlimited, but your telephony plan may have its own concurrent call constraints. Check with your telephony provider to confirm there are no carrier-level caps on simultaneous inbound calls to your AI Receptionist phone number.