Hosted handoff
Hosted ChatInfra
The default hosted path, with a crawlable handoff to explore supported setup.
Start with the outcome you want
Host AI agents. Connect them everywhere.
Choose one useful outcome, launch it in a hosted agent workspace, and connect it to people over messaging and voice with guided tool setup. If you can describe what you want to happen, you can start here, then inspect, configure, connect, or take more direct control whenever it helps.
Hosted first, with room to grow
Whether you run a business or are working toward your own goals, the homepage presents the same Hosted ChatInfra handoff and safe-start journey. That handoff does not establish current public registration or paid self-service. ChatInfra Edge and ChatInfra Sovereign remain visible for qualified, contact-led conversations.
Hosted handoff
The default hosted path, with a crawlable handoff to explore supported setup.
Contact-led
Talk with us about a qualified deployment closer to the systems and people it supports.
Contact-led
Talk with us about qualified deployment needs that call for greater infrastructure control.
Choose your path
Pick the next step that matches your goal. Every path stays crawlable, shareable, and tied to an existing product, integration, messaging, or setup route.
Support
Start with messaging support that answers FAQs, summarizes threads, and hands off edge cases to a person.
Scheduling
Give your AI a safe place to help with scheduling, follow-up, and contact context across your rollout.
Setup help
If you are not sure which first workflow fits, start with setup support and choose a smaller launch plan with help.
One shared safe-start journey
Use this guide to launch a workflow for your business or for a project of your own. It describes the intent of a safe start, not a fixed onboarding interface or a promise about specific product screens.
Name the useful result you want before choosing tools, channels, or a larger rollout.
Give one focused agent a clear job so the first launch stays understandable and reviewable.
Teach the agent how to help, define its limits, and add only the tools or channels the outcome needs.
Review how the agent behaves in practice, then adjust its direction and boundaries.
Add agents, connections, and autonomy only after the first behavior has been observed and refined.
Why teams can start safely
ChatInfra keeps the first rollout scoped and reviewable, then states where the behavior sits on the on-rails to autonomous dial before teams expand it. Owners can start with guided support, then choose when to inspect configuration, connect more tools, or take more direct control.
On rails
Pick one useful outcome, keep the first launch scoped, and leave human handoff clear before expanding.
Dial
ChatInfra frames behavior as an on-rails to autonomous dial so every rollout can state how much freedom the agent has.
Worked example
Calbot is ChatInfra's appointment-making AI concierge for the hosted core. Its current production state and its WhatsApp messaging and Twilio voice channels require their own evidence.
Evidence boundaries
A hosted-core observation was recorded on July 14, 2026; it does not establish current public registration, first-party agent selection, checkout, trial creation, card collection, conversion, charging, or paid self-service. XMPP and JMAP account substrate plus WhatsApp messaging and Twilio voice connector implementations exist, but their availability is gated pending named evidence gates. Calbot’s current production state and channels require their own evidence.
The July 14, 2026 observation does not establish current public signup, first-party agent selection, or paid entry.
Account-substrate implementations exist; availability is gated pending account evidence.
Connector implementations exist; their availability is gated pending named evidence gates.
Roadmap-only channels and product lines are presented as coming until their status changes.
Once you know the first outcome you want, the same core building blocks keep the launch reviewable and easy to explain to the rest of the team.
A supported place to host, review, and improve the agent workflows you launch first.
Outcome-driven, shareable capability pages that explain what each agent can do before setup starts.
Guided help connecting calendars, contacts, and tools safely around the first workflow.
Implemented WhatsApp messaging and Twilio voice connectors with gated availability, plus roadmap channels marked coming.
Pick the first outcome you want to launch and the guide, integration, or support path that fits it.
Add messaging connectors and tools only where they help the first workflow. Keep it minimal at first.
Use a hosted agent workspace to refine behavior, keep human handoff, and expand once the rollout is stable.
Start with the curated paths that best match the current product and setup journey.
Product
Understand the agent workspace, setup support, and review loop that make a first rollout manageable.
Integrations
Review verified-live, gated, and coming integrations before setup starts.
Messaging
Compare built-in messaging and connector options for pilots that need clear human handoff.
We can support connector setup, tool setup, and launch readiness for a focused first rollout.