Skip to main content

​
Getting started

Burki helps you create a business voice assistant, practice a draft in your browser, connect callers and review results. Start with one useful task, such as answering approved questions or collecting a service request.
Create your account, verify your email when requested, and open Assistants. Describe the business and desired call outcome, review the editable starter, then select Test this version. You do not need a telephone number or provider keys for eligible managed browser testing. Follow the Quickstart for the complete journey.
New assistants start with managed GPT Live, which handles speech directly. You do not need to choose separate transcription and speech-synthesis providers for this preset. Other provider configurations are available where supported; check their readiness before testing or publishing.
No. Review and test the selected draft version, then use the publishing controls when you are ready. A successful browser test does not by itself establish telephone, booking or transfer readiness.

​
Trial and billing

Eligible new workspaces can use up to three minutes of personalized browser testing, shared across sessions, with a two-minute maximum per call and one concurrent trial call. Provider-cost limits and shared daily capacity also apply. Burki shows your effective remaining allowance before a test.This is browser practice time, not cash wallet credit, 200 telephone minutes or a free phone number. Existing grants and paid balances retain their own terms. Trial actions are simulated; live external actions and stored recordings require funded usage and supported connections.
Check the browser test allowance as well as Usage & billing: trial time and wallet funds are different. Verify your email if requested and read the reason shown before testing. The allowance may be used, unavailable for the workspace, or temporarily limited by daily capacity. Your draft remains editable. If it seems wrong, use Burki’s Help or support-ticket option and include the visible message; never send provider keys.
Burki uses prepaid usage. Review the configured platform, managed-provider and telephone charges before a call. Number rental is a separate recurring charge and may continue even when the number is not used. See current pricing and your workspace’s quote for the selected configuration. An estimate or temporary reservation is not the same as the final settled charge.
The editable starter is free. Optional AI workflow generation is separately priced and requires funded usage. Review the displayed generation price before confirming; browser trial time does not pay for it.
With BYO credentials, you pay the connected provider directly for its usage. Burki platform charges and any other applicable managed or telephone charges remain separate. Use supported provider settings and check the effective quote; a provider cost that Burki cannot calculate is unknown, not free.
Open Usage & billing and choose a supported top-up amount. Review any auto-top-up setting separately; it is optional. Exhausting trial time does not automatically authorize paid calling.

​
Real calls and actions

Check the carrier-specific setup in Phone numbers. Telnyx, Twilio and Vonage configuration paths have different requirements; a connected credential or imported number does not prove end-to-end readiness. Use a number you control, resolve the displayed setup checks, and complete an authorized test before sending customer calls to it.
Configure the supported Cal.com action, select an appointment type and use funded usage for a real booking. The assistant should confirm the caller’s date, timezone and details before creating it, and only report success from the returned booking result. A simulated trial action does not create an appointment.
Funded telephone calls require an eligible carrier route, a configured number and a ready assistant version. Transfer behavior depends on the selected runtime, workflow and destination. Check the supported configuration and test the specific handoff, including rejection or timeout, before using it with customers.
Fallback behavior is configuration-specific. Do not assume a separate STT, LLM or TTS fallback applies to a GPT Live speech-to-speech session. Review the options and readiness checks for the selected provider combination.

​
Reviewing calls and troubleshooting

Open Calls and select a call to inspect its transcript, available activity and cost. Recordings are available only when recording was enabled with the required consent, permissions and storage configuration. Trial browser calls retain transcripts; they do not include stored recordings. A completed call does not necessarily mean a booking or other business action succeeded, so review the action result too.
Read the test or call error first. For browser practice, check microphone permission and trial allowance or available funds. For telephone calls, also check the assigned and published assistant, carrier readiness and provider credentials. Include the call or request ID when contacting support, without sharing keys or private caller details unnecessarily.
Compare a browser test in a quiet setting with the affected telephone call. Check the microphone, network connection, selected model and provider status. Review the transcript and timing before changing providers. Avoid assuming that a different TTS provider will affect a GPT Live session, which produces speech directly.
Check that the request uses a valid key for the correct workspace in the Authorization: Bearer YOUR_KEY header. Review its access and expiration in API keys. Keep keys server-side and never paste them into a support ticket.

​
Need help?

Use Help in your Burki workspace to review guidance or create a support ticket. You can also contact the Burki team. Include the affected page, error message and request ID if available.