Known limitations

We would rather you read this before buying than discover it afterwards. Each item below is something the interface or older notes might suggest, but that version 1.0.0 does not do. Items will move off this page as they ship; the Changelog will say when.

Live phone calls#

• No live call transfer. "Transfer" records a handoff for your team to follow up; it never connects the caller to another phone. See Handoff to a person.
• Knowledge documents are not loaded into live calls. Live (Realtime) calls see the instructions, boundaries, open slots and tools. Enable search_catalog so calls can look up knowledge.
• The call-flow builder does not run on live calls. Workflows run in chat, the widget and the turn-based phone path.
• Connectors are not available on live calls, and neither are lookup_order, send_sms or the web search tools.
• Phone setup options that are saved but not applied: after-hours behaviour and message, call recording, answering-machine detection and "If a machine answers", "Speak first", maximum call duration and the per-channel toggles.
• Fixed call length caps: 15 minutes on the relay, 10 minutes on SIP.
• SIP-trunk calls skip the greeting, always use the flagship Realtime model, and are not checked against plan minutes.
• Some voices sound alike on calls. 25 voice names map onto OpenAI's 10 Realtime voices.

Carriers and outbound#

• Plivo, SIP and test lines cannot place calls. Vonage outbound is a one-way announcement.
• Telnyx outbound needs a Call Control connection ID that the import dialog does not collect.
• Twilio outbound calls are turn-based, not live: English (US) speech recognition, no interrupting, and a maximum of 8 exchanges. The outbound "First line" and the automated-caller disclosure are not spoken; put any disclosure in the greeting.
• One Plivo account per install, because signatures are checked against a single platform-wide token.
• OPENAI_PROJECT_ID is required for Plivo calls, although it is labelled optional.
• Outbound calls and campaigns are not gated by plan minutes.
• Campaign calling windows use the campaign's timezone, which defaults to America/New_York and has no setting in the interface.

Receptionists and channels#

• Template guardrails are replaced by a generic default when a receptionist is created. Review boundaries on every new receptionist.
• Booking slots do not roll forward on their own. Re-save hours (or press Generate week) to extend the diary.
• Slot times are worded in the server's timezone. Slots are generated in the workspace timezone, but the spoken and written labels follow the server's clock. Run the server in your business timezone (set TZ) if you serve a single region.
• No calendar sync. Bookings stay in Reception AI's diary; they are not written to Google Calendar.
• Widget voice is push-to-talk, not a live conversation.
• No domain allow-list in the interface for the widget.
• WhatsApp and Gmail messaging support a test send only.
• Webhooks have no signing secret, so their signature cannot authenticate them, and the call.completed event is never sent.
• Rehearsal checks tools and phrases; it does not score the greeting, and the number of scripted callers depends on the job.

AI providers and connectors#

• XAI_API_KEY is required for chat, the widget, transcription, voice previews, rehearsals and the turn-based phone path, even if another chat provider is connected.
• Connected chat providers (OpenAI, Anthropic, Together, OpenRouter) are not reliable: the Grok model name is passed to them unchanged.
• ElevenLabs and Cartesia are limited to spoken chat replies, and Deepgram is not used.
• Google Sheets export may not write rows on a real database.
• MCP support is minimal: no initialize handshake or session, so servers that require one will not work.
• Slack search and Calendly booking are not available.
• Web search tools ask an xAI model to search; they do not call a live search API.

Accounts, admin and billing#

• No password reset by email. Users can change their password while signed in.
• No team members or invitations. One user per workspace.
• No suspend, delete or impersonate in the admin panel.
• The only email sent is the first admin's confirmation link.
• PayPal is not implemented; its settings do nothing.
• Per-seat billing is not implemented; the label is display text.
• Past-due subscriptions keep their plan; nothing is restricted automatically.
• Revenue in Finance is entered by hand, and several cost types are not recorded.
• Settings with no effect: MAX_AGENTS_PER_WORKSPACE, COMPANY_ADDRESS, PLIVO_AUTH_ID, BRAND_TAGLINE and the PayPal keys.
• Deleting a workspace does not cancel its Stripe subscription.

Operations#

• Migrations are a manual deploy step. The app never migrates a real database by itself.
• Background jobs do not drain automatically under npm run dev; they do in a built server.
• The bundled DEPLOY.md refers to a fly.toml that is not included.