AI Receptionist Trial: Test Burki Before Taking Live Calls

Burki's personalized trial is for practicing a business conversation in your browser before connecting real callers. It is not a bundle of free telephone minutes, and the historical 200-minute offer described at this URL is no longer the current offer.

For eligible workspaces on the personalized trial, the allowance is up to three minutes in total, shared across sessions, with up to two minutes per call and one trial call at a time. Provider-expense and shared daily-capacity limits also apply, so the time available before a particular call can be smaller. Your workspace's preflight and billing screens are authoritative for your eligibility and remaining allowance.

Start with the right kind of test

An AI receptionist trial is most useful when you know what you want to learn before opening the microphone. Hearing a pleasant voice answers one question. Finding out whether your assistant keeps a corrected callback number, admits a missing fact and explains the next step accurately answers a more useful business question.

Burki has several ways to try a conversation. The public demo offers predefined scenarios. Personalized practice lets an eligible workspace try its own draft within the allowance shown before the call. A funded browser call can use configured integrations and create real external changes. The fact that you are speaking through a browser does not make every session a simulation.

For this guide, start with eligible personalized practice. Check the session type and displayed allowance before testing. If you later choose a funded session, review the connected actions first, just as you would before allowing a real caller to use them.

What you can do first

Create an unpublished assistant from a business description, review its instructions and practice a specific caller request. You do not need to buy a telephone number to do a browser test. The free starter is editable, so a useful first experiment does not require paid AI generation.

Choose one task: answer a supplied business question and collect a callback request. Then change one detail during the conversation. This tests whether the assistant preserves the correction and describes the next step honestly.

The receptionist setup worksheet gives you a starting brief. Avoid spending the whole allowance asking generic questions unrelated to your business.

Trial time is different from wallet money

Older workspaces may retain an earlier offer. A wallet grant and personalized trial time are not interchangeable, and renaming an assistant or creating another workspace does not create a fresh sponsorship entitlement.

What needs funded usage?

Paid AI-assisted drafting is a separate operation with its own displayed price and limits. Live telephone calls, number resources, IVR exploration, real external actions and stored recordings are not included simply because browser trial time remains.

During free trial practice, supported calendar actions are simulated and should be labeled accordingly. Other tools may make a configuration ineligible for the free path. A simulated calendar result helps you inspect the conversation; it does not create a real appointment. Adding “book an appointment” to a prompt also does not connect a calendar.

Before funding a live workflow, check its actual integrations and usage pricing. For carrier costs, separate the platform bill from any account you pay directly.

Use one short, repeatable caller scenario

Write down the business facts first. For a fictional repair business, you might supply weekday opening hours, a service area and a rule that staff confirm all appointment requests. Leave prices unspecified. Give the assistant a clear instruction to collect a callback request without promising a booking.

Then try this conversation in your own words:

I need someone to look at a leaking tap. My name is Sam. Can someone call me tomorrow afternoon? Actually, make that tomorrow morning.

Use a fictional name and a callback number you control. If the assistant needs more details, answer naturally. Ask for an exact price that you have not supplied. You are checking whether it can handle a correction and an unknown without restarting the whole intake or inventing a quote.

Do not squeeze every edge case into one short call. Pick the one failure that would cause the most work for your team, then use any remaining allowance to retest it after an edit. The limits above are maximums, so prepare before starting rather than assuming every session will run for the full two minutes.

These are suggested acceptance checks, not a claim that every draft passes them automatically. Keep the prompt version and your notes so a second attempt tests the change you actually made. For sample wording, use the AI receptionist script template.

Know when a browser call can create a real booking

A connected action is a separate step from the assistant speaking. LiveKit's tool documentation describes how an agent can call functions and external APIs. That technical capability does not establish that a particular Burki assistant has the right connection, permissions or successful result.

In Burki, free practice, demo and builder sessions simulate calendar actions. Funded browser calls can use a connected calendar after caller confirmation. A real booking requires a successful calendar result. Adding funds does not connect an account, select an event type or make a failed action succeed.

Before a funded calendar test, inspect the assistant's integration setup. Choose an appropriate test slot and details you control. Confirm the date, time zone, attendee details and intended action during the call. Then inspect the actual calendar record. If the result is unavailable or failed, the assistant should describe that outcome honestly instead of announcing a confirmed appointment.

Keep three observations separate in your notes: what the caller asked for, what the assistant said, and what the connected system saved. A simulated success belongs in the practice column. A spoken success without a corresponding record needs investigation. This is also why a good free conversation is not sufficient evidence to start taking bookings from customers.

Why might a trial call be unavailable?

The account may be ineligible, the allowance may be exhausted, the previous call may still be finishing, or the shared trial capacity may temporarily be unavailable. The assistant can also have a configuration that is not eligible for the available trial path.

Read the reason shown before microphone access. Keep the draft and use the corrective action provided rather than repeatedly starting new requests. If the account appears to have the wrong entitlement, contact support with the workspace and visible request identifier; do not send provider keys or card details.

A temporarily unavailable trial is not permission to charge paid usage automatically. Choose prepaid testing explicitly when you decide to continue.

Make a small trial useful

Prepare the facts and one expected outcome before the call. Use your first conversation to find the largest problem, then edit the instructions and use the remaining available time on that same case. Review the available call details and distinguish a completed conversation from a completed business action. Free practice does not include stored call recordings. Your own checklist is useful even when a recording is unavailable.

You do not need a live number to decide whether the draft understands your request. Once it does, fund the next appropriate step and separately verify telephone readiness. Use the browser versus telephone acceptance guide for that later check; a browser test alone does not verify your number routing or carrier audio. Create a practice assistant to see the offer available to your workspace.