Onboarding, go-live timelines, languages, knowledge training, human handoff, notifications, booking, billing, integrations, and privacy—without the fluff.
Frequently asked questions
Create a workspace, connect telephony where your carrier allows inbound audio, configure prompts and knowledge, define routing and handoff rules, then place rehearsal calls from the dashboard. Publish to a public number only after your team signs off.
Lightweight pilots can move quickly once a number is ready and your knowledge is drafted. Complex routing, many locales, or compliance reviews extend the timeline. Treat the dashboard rehearsal phase as mandatory—not optional.
Starter and Growth bill monthly through Lemon Squeezy inside the authenticated app. Exact amounts depend on your workspace configuration and usage. Managed services are quoted after scope is understood—there is no hidden price list here.
In most setups you forward or route your published business line to the number Nyxce Core answers. Exact steps depend on your carrier and country—confirm with your provider and our setup guide before you switch a live line.
You enable the languages you are prepared to support. Quality and voice behavior depend on your agent configuration and provider setup, so rehearse each locale before exposing it on a customer-facing line.
You maintain prompts plus a structured knowledge base inside the workspace. The assistant should cite what you publish—not guess at policies. Managed engagements can include help organizing that content, but you remain the source of truth.
Yes. You define when a live teammate must take over and what context they should receive. The AI layer is meant to filter and prepare, not block access to people.
The product can alert the right owners when a conversation needs action, following the notification paths configured in your workspace. Exact channels and templates depend on what your tenant enables—verify inside the app for authoritative options.
You can configure booking or intake flows that respect the availability and rules you document. Complex scheduling may still need a human confirmation step—set expectations accordingly in your knowledge base.
Yes. Intent-based routing can prioritize emergencies or VIP scenarios to specific people or queues, with fallbacks you control so callers are not dropped silently.
Retention depends on workspace settings and your telephony provider. Use your admin documentation and contractual agreements as the source of truth; we do not quote a one-size-fits-all retention period here.
No. It extends coverage and qualification so humans spend time where judgment matters. Front-desk roles evolve, but they do not disappear overnight.
From the knowledge base and prompts you maintain, layered with live call context. If something is not documented, the assistant should escalate rather than invent policy.
Yes, when your workspace and channel configuration support WhatsApp conversations. Voice and messaging can share trained policies so follow-up stays consistent.
You define fallbacks: transfer to a human, collect a callback request, or route to voicemail as a last resort. The goal is never to leave a caller without a clear next step.
Many teams use Nyxce Core for intake, routing, and capturing context—it does not provide legal or medical advice. Configure scripts and escalation with qualified counsel for your jurisdiction and practice.
Need a walkthrough with your actual call flows?
Send a contact note with sample scenarios—we will show how routing, languages, and handoffs map to the dashboard.
