To set up Nextiva AI Receptionist, create your XBert account, review your business information, define call handling rules, connect an eligible calendar and test appointments and human handoffs. Then route a limited set of business calls to the AI number, check the results and expand coverage after the workflow works reliably.
A useful Nextiva XBert setup starts with the outcome your caller needs: an accurate answer, a confirmed appointment or a clear next step with a person. This guide explains how to prepare that workflow, what to check in your account and how to avoid launching a receptionist that sounds ready before its booking and transfer paths are ready.
How To Set Up Nextiva AI Receptionist: Preparation And Requirements
Decide which part of your phone workload the AI receptionist should handle first. Answering every incoming call is a different project from catching calls when the front desk is busy. A booking assistant for 1 consultation type is also easier to validate than a receptionist expected to handle every service, employee and exception on its first day.
Write a short launch statement before opening the configuration screens. For example: “Handle routine appointment requests when the office cannot answer, collect a callback number and transfer existing customers with urgent account questions.” This is a proposed business scope, not a prebuilt XBert template. It gives your team a concrete standard for deciding which instructions and integrations belong in the initial setup.
Check Which Nextiva Product You Have
Standalone XBert, XBert AI Classic and the wider NEXT platform have different interfaces. Use the standalone XBert instructions for that account, applying its stated exceptions when a linked NEXT article differs.
This matters when someone shares an older tutorial or a screenshot from another subscription. A missing menu does not prove your account is broken. Before changing anything, compare the product name on your account, the help article’s product label and the feature your order actually includes. Ask support to identify the appropriate setup path if those 3 items do not agree.
Gather Your Setup Information In 1 Place
Prepare a working document that an employee can review without logging into the phone system. Include your approved business name, service area, opening hours, appointment categories, transfer destinations and message recipients. Separate public information from internal instructions. A private escalation number belongs in a routing record, while a public address can belong in customer-facing answers.
| Setup Area | Prepare Before Configuration | Your Acceptance Check |
|---|---|---|
| Business Knowledge | Approved services, hours, locations and pricing rules. | Answers match the information staff would give. |
| Call Handling | Initial coverage, direct staff destination and fallback owner. | A caller reaches a useful outcome without a forwarding loop. |
| Appointments | Calendar owner, eligible appointment, duration and time zone. | A test event appears in the intended calendar with correct details. |
| Follow-Up | Required intake fields, callback owner and response commitment. | Staff can act on the message without repeating the entire intake. |
| Launch Control | Test numbers, route record and restoration instructions. | An authorized employee can restore the previous call path. |
Set A Realistic Budget Before Connecting Traffic
XBert Premium is advertised from $100 per month on an annual plan billed monthly, with 100 conversations included and $0.99 per additional conversation within the published tier. Premium+ starts from $2,500 per month. These are starting offers, not a complete quote for your integrations, usage or implementation requirements.
Ask what counts toward billing during your test period, whether repeated contacts count separately and what happens at a spending cap. Include carrier forwarding charges, implementation work and employee review time in your budget. A low subscription price does not tell you how much a particular call flow costs to operate.
Annual plan billed monthly; confirm your selected package, usage allowance and trial terms.
Start Free TrialStep 1: Create Your XBert Account And Complete Initial Training
New standalone accounts begin with onboarding and AI Training. Supply your website or business details, personalize the agent and retain its assigned number. The initial training pages cover channels, business details, products and services, then finishing setup. SMS requires completed 10DLC registration.
Work through this initial information as an editor, not just an installer. A website can contain retired services, several locations and an old promotion. The important task is deciding what the AI receptionist should say for the particular number you are launching. Assign someone who knows your daily operations to approve that information before public calls are connected.
Choose A Greeting Callers Can Understand
Use your familiar trading name and identify the purpose of the conversation. A proposed greeting might be: “Thanks for calling Oak Street Services. I’m the AI assistant. I can help with general questions or request an appointment. How can I help?” Replace the sample name and promises with your approved wording and enabled capabilities.
Keep the greeting short enough that a returning customer does not have to listen to a sales introduction. If booking is still being tested, say the assistant can collect an appointment request rather than promising to book. The greeting should describe the workflow you have actually approved, including any required recording notice reviewed for your situation.
Separate Initial Training From Detailed Configuration
The linked NEXT AI Employee guide describes 5 configuration stages covering identity, business information, skills, testing and channels. Those stages are distinct from the initial standalone training pages. After setup, standalone editing is available from the Home card’s Edit action or Settings → AI Employees.
Do not interpret reaching the end of onboarding as proof that every business process is finished. Keep a separate checklist for the actions you need: capture details, request a staff callback, transfer a call or create a calendar event. For each action, identify the connection, permission and test that make it usable in your business.
Step 2: Train The AI Receptionist On Approved Business Knowledge
Start with the questions your team answers most often. Review a small, representative set of recent inquiries and group them by intent: opening hours, service eligibility, appointments, existing bookings, pricing and speaking to a person. Use those groups to decide what information belongs in your training material. Avoid copying a large document simply because it is available.
Write answers in plain language and make the limits explicit. “We offer residential drain cleaning within these ZIP codes” is more useful than “We provide complete plumbing solutions.” The first statement tells the AI receptionist what it can safely communicate and gives your testing team a clear answer to check.
Resolve Conflicting Information Before Launch
If your website says Saturday appointments are available but the office stopped offering them, correct the source material and the approved receptionist information. Do not rely on staff remembering to explain the exception later. Keep a short record of which business owner approved the change so future editors can resolve similar conflicts without guessing.
For prices, distinguish a fixed fee, a starting price and a quote that requires staff approval. Your proposed instructions should forbid turning a starting price into a guaranteed total. Include what the price covers and which exceptions require a person. This protects the caller from receiving an answer that sounds precise but leaves out essential conditions.
Define What The AI Receptionist Must Not Promise
List commitments that require human approval: refunds, guaranteed arrival times, service outside your territory, same-day emergency availability or exceptions to cancellation policies. Explain the next step for those requests. A restriction without a fallback can leave the caller stuck; a restriction with an owner and a callback process preserves a useful outcome.
For regulated or sensitive workflows, have the appropriate person approve both the information collected and the systems receiving it. A receptionist setup should not become an improvised clinical, legal or payment-advice process. Keep initial intake limited to what your team needs to route the inquiry, then use your approved procedures for anything more sensitive.
Step 3: Write Skills And Intake Instructions Around Real Outcomes
A useful instruction set explains what the assistant should accomplish, which details it needs and when it should stop. Avoid a long paragraph mixing brand voice, appointment rules, escalation priorities and sales messages. Organize the requirements so you can test each outcome separately and identify which instruction needs revision when a call goes wrong.
The following is a business instruction example to adapt to the configuration options available in your account. It is not executable code, a hidden system prompt or a guarantee that every action is enabled on your subscription.
Help callers identify the service they need. Collect their name, callback number and a short description. Check whether the location is within our approved service area. Offer booking only for eligible appointment types using the authorized calendar. If eligibility is unclear, the connection fails or the caller requests a person, use the approved handoff or callback process. Never describe an appointment as confirmed without a successful booking result.
Collect Enough Information Without Turning Calls Into Forms
Choose a minimum useful intake record. For a service inquiry, that could be a name, callback number, general location, reason for calling and preferred contact time. A professional consultation might require a different qualification question. Ask why each field matters before adding it. Unnecessary questions increase the chance that a caller leaves before reaching the useful part.
Have the AI receptionist confirm important details in a natural way. Read back a callback number when it may have been misheard, and clarify a time rather than assuming whether the caller means morning or evening. Your acceptance test should include corrections halfway through a conversation, because callers often change a date, spelling or number after first saying it.
Give Every Unfinished Inquiry An Owner
A captured message is only useful if someone takes responsibility for it. Decide who reviews new requests, who covers breaks and who handles messages received overnight. State a realistic callback commitment that your employees can meet. Do not tell callers to expect immediate contact simply because an automated notification is sent immediately.
In a proposed 3-person office workflow, the receptionist might review new inquiries at opening, the office manager might handle booking exceptions and the owner might receive service complaints. Those are operational responsibilities to establish with your team. They do not assume that standalone XBert provides a separate inbox or permission level for each employee.
Step 4: Design Your XBert Call Flows Before Changing Routing
A call flow describes what happens from the moment someone dials your public number until the inquiry reaches a useful outcome. It includes the existing carrier, the AI receptionist, the human destination and the fallback. Draw that sequence in your working document before configuring it. You do not need a complicated diagram to identify a missing handoff.
The examples below are proposed business logic. Implement each step through the supported carrier settings, XBert configuration and integrations available to you. They are not instructions for an assumed visual flow builder, and they should not be treated as proof that every account includes the same scheduling or routing controls.
Call Flow 1: Busy Or Unanswered Calls
- A customer calls your established business number.
- Your existing phone service gives staff the opportunity to answer.
- The carrier’s supported unanswered or busy forwarding rule sends eligible calls to the AI destination.
- The assistant handles approved questions or gathers the required intake.
- A person handles exceptions through the tested destination or callback process.
This is a practical pilot when your employees already answer most calls well. Choose the forwarding condition carefully: a busy rule and an unanswered rule can behave differently. Test both conditions from an outside phone. Record how long the caller waits overall, including the original ringing period, so an apparently efficient assistant does not sit behind an unnecessarily long delay.
Call Flow 2: After-Hours Answering
- Your supported routing schedule sends eligible closed-hours calls to the assistant.
- The greeting makes the office’s availability clear.
- Routine inquiries receive approved information.
- Eligible booking requests follow the calendar process.
- Other requests become a staff follow-up with an honest response expectation.
Separate office hours, appointment availability and on-call coverage. Those 3 schedules may not match. A closed office can still accept a booking for a later day, while an emergency response might depend on a real person being available. Do not use a single “open” label as a substitute for defining each decision.
Call Flow 3: Appointment-First Reception
- The assistant identifies the requested service.
- It checks your approved booking eligibility requirements.
- It uses the authorized calendar action to identify suitable availability.
- The caller chooses a time and confirms required details.
- The system result determines whether the outcome is a confirmed appointment or an unconfirmed request.
Keep this initial call flow narrow. A business with several services can begin with 1 simple appointment type before adding appointments that require special equipment, several staff members or an address-based service duration. The purpose of the pilot is to validate a complete process, not to advertise the largest possible menu of options.
Call Flow 4: Requests That Need A Person
Standalone XBert documents external-number transfers or summary notifications, not internal transfers. Choose a direct destination that does not return calls to the same public route. Keep a separate fallback owner for unanswered handoffs.
Ask the vendor what the live call does if the target is busy, declines or reaches voicemail. Do not assume the assistant automatically resumes the conversation or tries several destinations. Test the behavior that your account actually produces, then choose wording and coverage appropriate to that behavior. A callback request can be preferable to an unreliable transfer during a pilot.
Step 5: Connect Your Business Number Without Creating A Loop
Keep a written record of the existing route before changing it. Note the public number, carrier account owner, current forwarding destination, voicemail behavior and any schedule already in use. Have the authorized person confirm how to restore those settings. This is especially important when a web agency, office manager and phone provider each control different parts of the setup.
Use your carrier’s instructions for the exact number and forwarding condition involved. Avoid copying dialing codes from an unrelated carrier or old tutorial. If you need background on routing terminology, review our call forwarding guide before selecting the behavior you want.
Keep The Human Destination Outside The Forwarding Loop
A common design error is sending business calls to the AI receptionist, then using that same business number as the human escalation destination. The second leg can return to the assistant instead of reaching a person. Use a verified direct destination and test it with the public forwarding rule active, rather than testing each number only in isolation.
Also test what staff see when the transferred call arrives. They need enough context to answer appropriately without assuming that a displayed caller number or notification will always contain everything required. Decide how employees will identify these calls and where they should look for the intake record before the pilot becomes routine.
Treat Number Porting And SMS As Separate Decisions
Forwarding calls, porting a number and enabling business text messaging solve different problems. Do not start a number transfer merely to run a forwarding pilot unless your provider confirms that it is necessary. Ask which party controls the number, which services move and what happens to existing voicemail, fax or messaging arrangements.
Routing voice calls does not establish that messages sent to your original number will reach the new receptionist workflow. Test voice and SMS independently using the intended public number. Record the sender and recipient for each test so staff do not mistake a successful text to a new number for successful messaging on the established business line.
Step 6: Connect A Calendar And Define Appointment Booking Rules
In the NEXT AI Employee configuration guide, calendar setup uses Add apps → Calendar during guided setup; an administrator Meetings route is also documented. Standalone XBert does not expose that Meetings menu. Use its available integration controls or ask support to confirm the appropriate connection path.
The guide lists Google availability, retrieval, creation, updating and deletion for 1 calendar per tenant. Outlook lists availability, creation and retrieval for the primary calendar. It also specifies the tenant time zone. Verify the actions enabled on your account before offering changes or cancellations.
Choose The Calendar That Represents Real Availability
Connect a calendar your business actively maintains. A nearly empty calendar can make the AI receptionist appear effective while creating appointments that conflict with work recorded elsewhere. Before enabling booking, ask staff where unavailable time, leave, travel and existing commitments are actually recorded. Resolve that operational gap before treating free space as bookable space.
Use an account owner appropriate for the business, with a documented recovery process. Avoid building a critical workflow around a temporary employee’s personal login. Agree who can reconnect the integration if authorization expires and who receives notice that bookings are no longer being created. The ownership decision is as important as the initial authorization.
Define The Appointment Before Allowing Booking
Write down the appointment name, duration, location, eligible customers, advance notice and any preparation instructions. If you need buffers, capacity limits, round-robin staff assignment or travel-based availability, ask whether the selected integration enforces them. A written instruction should not be mistaken for a scheduling constraint that the connected system cannot actually apply.
For example, a proposed consultation workflow might allow a 30-minute introductory appointment during approved office hours. It might require a name and email, prohibit same-day booking and send existing customers to staff for account-specific work. These are sample business requirements. Validate every requirement in your actual setup rather than presenting the example as a product preset.
Distinguish Confirmed Bookings From Requests
Use 3 separate outcome labels in your operating procedure: confirmed appointment, booking request awaiting review and booking link sent. Only the first means that an event has been successfully created in the intended scheduling system. A friendly closing sentence, a captured preferred time or an outgoing link does not establish that a booking exists.
Require the person testing the AI receptionist to open the destination calendar and inspect the saved event. Check the start and end time, customer details, appointment type and location. Then check the customer-facing confirmation. If any part disagrees, keep the workflow in request-only mode until the team understands and fixes the cause.
Test Time Zones And Booking Changes Explicitly
Use callers who describe times in different ways: “tomorrow afternoon,” “Friday at 3” and a time in another city. Ask the assistant to clarify ambiguity and confirm the agreed local time. Include a test near a date boundary and review how your business handles seasonal clock changes where relevant. An apparently small time-zone mismatch can create a completely unusable appointment.
Test rescheduling and cancellation separately from creating a new event. Success with creation does not prove permission to modify an existing record. Define what the AI receptionist should do when it cannot complete a requested change: collect identifying information through an approved process, mark the request unconfirmed and send it to the responsible employee.
Step 7: Configure Channels, Notifications And Lead Follow-Up
Start with the smallest useful channel scope, then add another channel only after staff can manage its conversations. A successful voice pilot does not automatically validate messaging consent, written responses or website chat deployment. Each channel needs its own owner, test contact and definition of a completed outcome.
For SMS, verify registration status, sending identity, consent handling and the delivery of the actual messages you plan to use. Ask the vendor which requirements apply to your number and destination countries. Do not interpret an enabled checkbox as proof that a customer received a confirmation or that every proposed message is permitted.
Make Summary Notifications Actionable
A useful handoff should tell the employee who called, why they called, what was attempted and what remains unresolved. Use your test conversations to judge whether the summary supports action. If staff repeatedly need to replay the full call just to find a callback number, adjust intake requirements and the review process before increasing volume.
Decide which notification destination is monitored outside office hours. A personal email address that nobody checks overnight may be suitable for routine follow-up but unsuitable for time-sensitive service requests. Align the promise made to the caller with the employee coverage that really exists, and keep backup ownership explicit.
Keep Inbox Records And CRM Actions Distinct
Standalone XBert uses a shared General Inbox; added users are administrators, and its tickets are created manually. Give access deliberately and assign follow-up responsibilities outside any assumed departmental inbox structure.
If you connect a CRM, test the specific record action you need. Start with a fictional contact clearly labeled as a test, then inspect the name, phone, source and notes in the destination system. Check what happens when that contact calls again. A contact record, a support ticket and a calendar event are separate outcomes and should each have an acceptance check.
Step 8: Test Your Nextiva AI Receptionist Before Launch
Test complete caller journeys from an external phone. A preview can help with wording, but it does not replace testing your public number, carrier forwarding, handoff destination and calendar together. Ask someone who did not write the instructions to play the caller. They are more likely to use unexpected wording and reveal assumptions your setup team missed.
The following checklist is an editorial test plan to run on your own account. It is not a claim that we completed these tests or measured XBert’s performance. Record the expected outcome and the observed result for every scenario, including the destination record when the call is supposed to create one.
| Test Scenario | Expected Outcome | Evidence To Inspect |
|---|---|---|
| Routine Question | Approved answer without an unsupported promise. | Conversation wording compared with the approved business record. |
| Eligible Booking | Correct appointment or an explicitly unconfirmed request. | Calendar event, time zone, attendee and confirmation. |
| Unavailable Time | An eligible alternative or useful staff follow-up. | No conflicting event or false confirmation. |
| Human Request | Tested direct handoff or clear callback process. | Receiving phone, conversation record and responsible employee. |
| Integration Failure | Honest explanation and an unconfirmed request. | No claim of success without a saved destination record. |
| Caller Correction | Updated details used in the final outcome. | Final callback number, name, time and destination fields. |
Include Difficult But Ordinary Conversations
Try an unclear service request, a caller who interrupts, background noise and someone who asks for an unavailable service. Have another tester change their preferred time after availability is discussed. These are ordinary conversations, not attempts to defeat the assistant. Your goal is to find where clarification or human support should replace an automatic answer.
Test a dissatisfied existing customer separately from a new sales lead. The person may not want qualification questions or another appointment. Write down the intended response and escalation path before evaluating the AI receptionist. Otherwise, a fluent conversation can look successful even though it fails the customer’s actual purpose.
Set Launch Gates Your Team Can Apply
Use concrete acceptance rules: the confirmed booking appears correctly, the transfer reaches the intended person, the callback record contains a usable number and the assistant does not invent an unsupported commitment. Treat a critical failure as a reason to pause that workflow. Do not average a false booking into a larger score and call the result acceptable.
Keep a simple test log with the scenario, result, issue owner and retest status. Make 1 meaningful change at a time where practical, then repeat the affected journey. This gives you evidence that a fix addressed the problem without requiring an elaborate software-testing project for every wording adjustment.
Step 9: Launch In Stages And Keep A Rollback Route
Choose an initial traffic segment your team can watch closely, such as unanswered calls during staffed hours. Tell employees when the pilot starts and who can change routing. Avoid launching immediately before the responsible person leaves for several days. A business process involving customers needs someone available to inspect real results and respond to unexpected behavior.
Before expanding coverage, review the first available sample of genuine conversations, their follow-up records and any appointments created. Look for repeated confusion, abandoned requests and staff work that the original design overlooked. Expansion should follow a working process, rather than a preset date or the fact that the assistant has an active status.
Prepare A Short Restoration Checklist
- Identify the employee authorized to change the public number’s routing.
- Record the previous destination and the carrier’s restoration procedure.
- Keep a working fallback such as staffed answering or the established voicemail route.
- Confirm how pending appointment requests and callbacks will still be handled.
- Retest the public number after restoring the previous route.
Restoring routing does not remove obligations created during the pilot. Staff still need to contact people who requested help, review uncertain bookings and correct any misleading confirmation. Keep that cleanup process separate from the technical routing change so a successful rollback does not leave customers waiting for follow-up.
Step 10: Maintain Call Flows, Booking Rules And Business Knowledge
Assign a named owner to review business information whenever your operations change. A new service area, a holiday closure or a revised cancellation rule should trigger a receptionist review. Keep a brief change log describing what changed, who approved it and which caller journey was retested. That is usually more useful than a large document nobody maintains.
Measure useful outcomes rather than the number of conversations alone. Track whether appointments were accurate, callback requests reached an employee and transfers connected to an appropriate destination. Ask staff whether summaries reduce repetition or create extra cleanup. The best maintenance priorities come from those outcomes, not from assuming that longer or shorter calls are inherently better.
Interpret Analytics With Care
Standalone analytics are under More → Analytics and use Sessions; notification escalations can count as transferred sessions. Reconcile reporting with your billing definitions rather than assuming that every dashboard total represents the same unit.
For your own management review, keep separate counts for confirmed bookings, appointment requests, completed callbacks and failed handoffs. You can begin with a simple spreadsheet maintained by the person reviewing conversations. Use consistent definitions so an apparent improvement does not merely reflect that the team started labeling outcomes differently.
Common XBert Setup Problems And Practical Fixes
The Assistant Gives An Outdated Answer
Compare the answer with the approved information first. Look for conflicting service descriptions, old promotions or missing exceptions. Correct the source of the confusion, then repeat the same question in several ordinary phrasings. Avoid adding several competing instructions when a single clear business rule would resolve the issue.
The Caller Hears A Booking Confirmation But No Event Appears
Pause confirmed-booking language for that workflow. Inspect the destination account, authorization, selected calendar and event details. Ask support to help identify whether the action failed or the record was created somewhere unexpected. Until the saved result is dependable, collect appointment requests with explicit human confirmation instead of allowing an uncertain success message.
A Human Handoff Returns To The Assistant
Review the entire number chain with the carrier route active. Check whether the destination redirects to the public number, whether staff voicemail forwards elsewhere and whether a schedule introduces another leg. Change only the relevant route, then test again from an external phone. Keep the documented fallback available during the repair.
The Setup Screens Do Not Match A Tutorial
Confirm the account variant and the tutorial’s product scope. Send support the exact feature you are trying to configure and a description of the menu you see. Avoid upgrading, deleting an agent or rebuilding the account simply to reproduce a screenshot. Request the supported path for your subscription and document it for the next employee.
Messages Are Captured But Nobody Follows Up
This usually needs an ownership fix before another automation. Identify who reviews new inquiries and who covers absences, then test a message from capture through completed callback. If several people receive the same notification, define who takes responsibility so the customer is neither ignored nor contacted repeatedly by different employees.
Frequently Asked Questions About Nextiva AI Receptionist Setup
What Is The Best Way To Start An XBert Pilot?
Choose 1 narrow, useful outcome and a call segment your team can monitor. Prepare approved information, define the fallback and test the whole journey. Expand only when staff can verify that the caller reached the intended result and that unfinished work has a responsible owner.
Should I Let The AI Receptionist Answer Every Call Immediately?
That depends on your business coverage and test results. Starting with overflow can help you validate the process while staff remain available. Full-time reception should follow successful testing of routine inquiries, difficult requests, human handoffs and failure conditions, rather than being the automatic first step.
How Do I Know Whether Appointment Booking Is Working?
Inspect the actual event in the intended calendar and compare it with the caller’s agreement. Check time zone, duration, service, customer details and confirmation. Treat a collected preferred time or a sent booking link as a different outcome from a successfully created appointment.
How Long Should I Allow For Setup?
Allow time for preparation, permissions, integration checks and retesting, not just account creation. A simple information-and-callback workflow needs less validation than multi-service booking. Ask the XBert team to confirm the implementation work and dependencies for your proposed call flow before setting a launch commitment.
Can I Use The Same Instructions For Every Location?
Reuse common policies only where they are actually shared. Location-specific hours, services, calendars and contact destinations need clear separation. Before expanding, test callers who name the wrong location or do not specify one. The workflow should clarify the destination rather than guessing and creating work for another branch.
What Should I Compare Before Choosing An AI Receptionist?
Compare the outcomes you need, the supported integrations, the human fallback and the total operating cost. Our AI receptionist software guide can help build a shortlist. Then ask each shortlisted provider to demonstrate your own booking and handoff scenarios using the exact package being offered.
Customer Feedback: Turn Review Themes Into Setup Questions
Use customer feedback to identify questions worth asking, rather than treating a general platform review as evidence that your particular XBert workflow will work. Look for comments about onboarding help, configuration clarity, billing explanations and support follow-through. Check which product the reviewer actually used and whether the described workflow resembles your own.
For this setup guide, no star score or first-hand performance result is assigned. A useful next step is to ask the implementation team to walk through your real call flow, demonstrate the calendar result and explain who handles a failed integration. Those answers provide more decision value than a broad rating detached from your required setup.
Affiliate Disclosure: We may earn a commission if you purchase through our recommendation links, at no additional cost to you. This guide combines published product information with proposed business workflows and test checklists; it does not report hands-on testing.


