Import your website, pricing, hours, and FAQs. Review what the agent knows, prove the conversation in the browser, then assign an inbound number—all from one operating surface.
The same browser-to-Worker voice path customers use to test an agent. No account or phone number required.
One resource model across every build surface.
Same tenant-scoped resources.
The build surface is visible end to end: ground the agent, test the conversation, route a number, inspect the call, and watch usage.
Release-test capture: these are screenshots of the deployed CloudVoice workspace UI rendered with synthetic QA data. No customer data, payment, number purchase, or production write is represented.
The current production Chromium suite exercises the public control surface and records its assumptions.
Automated media checks reach greeting, caller transcription, and spoken reply. Human listening and PSTN remain separate acceptance gates.
Tenant isolation, explicit live-route confirmation, and durable deployment history keep changes reviewable.
Current evidence is published with its limits; field p75 and production guarantees require a real-user dataset.
Evidence and release boundaries: public status · technical docs · enterprise review
An inbound agent can answer common questions, capture leads, call approved tools, book supported calendar events, and transfer when a human should take over. You control the knowledge, behavior, and route.
Route inbound calls to an agent outside office hours or while your team is busy, subject to provider health, account balance, and your configured fallback.
Connect a supported scheduling tool, test its availability and booking actions, and let the agent use only the operations you approve.
Answers approved FAQs and can call configured tools for tasks such as order status or lead capture. Unknown or sensitive cases follow your fallback policy.
Connect your systems through signed tools, webhooks, REST, or MCP. Test tool behavior before a live call and keep credentials in the encrypted vault.
Configure an approved transfer destination and the conditions that should end the automated conversation. The resulting call record preserves the operational context.
Import a public website, paste approved facts, or upload business documents. Review the extracted text before indexing and keep each source visible in the Business Brain.
Store call records, transcripts, summaries, dispositions, extracted fields, costs, and recordings according to your configured retention policy.
Agent updates create version history, publish checks surface missing essentials, and test scenarios help you inspect behavior before deployment.
Pick the engine that fits the conversation, margin, and provider requirements. CloudVoice keeps the agent, number routing, business knowledge, call records, and billing model in one workspace.
Workers route requests and WebSockets; Durable Objects hold live call state; D1 stores tenant records and billing; Vectorize supports knowledge retrieval; R2 stores configured audio artifacts.
CloudVoice separates approved business knowledge from agent instructions. Website text and documents are reviewed before indexing, and each source remains visible in the Business Brain.
During a call, retrieval supplies relevant context to the selected engine. Call records and configured caller summaries help your team understand what happened without pretending that vector search is perfect memory.
Provision or connect a number, assign an agent and inbound engine, then inspect each completed call. Outbound dialing remains disabled until the account and compliance controls are ready.
CloudVoice is designed to shorten the path between “here is how my business works” and a testable inbound voice agent. Website import, visible business facts, agent settings, browser testing, number routing, and call records live in one operating surface.
The same tenant-scoped resources are exposed through the workspace, REST API, and MCP. That means a human can configure the agent visually while an automation manages repeatable operations without creating a second source of truth.
We earn the right to call it fast through observable setup steps and successful tests — not an unsupported latency promise.
Build and test the configuration in the workspace, then fund the prepaid ledger when you are ready for metered voice usage. The dashboard shows balance and call costs.
Move the sliders to match your operation. The math updates live, using your numbers — not ours.
Pricing, security, integrations, and what happens when the AI hits its limits. If your question is not here, use the support assistant or contact the team.
Start with approved business facts, choose an engine, test the conversation and tools, then attach telephony only after the agent passes your release checklist.
For enterprise evaluation, security review, data-boundary questions, or a guided deployment plan, contact the team before routing production calls.
We ship on Cloudflare (Workers, Durable Objects, D1, Vectorize). Latency depends on your PSTN carrier, codec path, and region — our stack is built for low tail latency, not a universal SLA. Healthcare: CloudVoice makes no HIPAA-compliance claim; your deployment requires counsel, appropriate controls, and every in-scope provider agreement before PHI is used—see Privacy. Memory combines configured RAG/vector retrieval with approved business sources; it is not perfect recall. Integrations (CRM, calendars) are scoped per deployment; confirm the actions and credentials you plan to allow on live calls.
Try the public demo, then create a workspace to build from your own approved business facts. Connect a real number only after the browser agent, tools, and fallback behavior pass your tests.
AI support & product guidance