Self-serve
Hosted
The default path for launching one agent in a supported ChatInfra workspace.
Start with the outcome you want
Host AI agents. Connect them everywhere.
ChatInfra helps technical and less-technical buyer/owners choose one useful outcome, launch it in a hosted agent workspace, and connect it to people over messaging and voice with guided tool setup. Start without building the whole stack from scratch, then inspect, configure, connect, or take more direct control when it helps.
Hosted first, with room to grow
Small-business owner-operators and individual buyer/owners have equal standing here. Both can begin with the same self-serve Hosted path and the same safe-start journey. Edge and Sovereign remain visible for qualified, contact-led conversations.
Self-serve
The default path for launching one agent in a supported ChatInfra workspace.
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.
Automation
Pair a chat-first experience with n8n so requests can trigger automations without building a custom app.
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
This guide applies equally to a small-business owner-operator and an individual buyer/owner. 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 the appointment-making AI concierge running in production on the hosted core over WhatsApp messaging and Twilio voice.
Live today
The current live set is the hosted core, the XMPP + JMAP substrate, WhatsApp messaging, and Twilio voice. Calbot is the worked example: an on-rails appointment-making AI concierge live in production on that stack.
Start on the hosted SaaS core without standing up your own agent workspace stack.
Provisioned messaging and account foundations are part of the live hosted core.
The live connector set reaches people over WhatsApp messaging and Twilio voice.
Channels and product lines outside the live set are presented as coming until they are ready.
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.
Live WhatsApp messaging and Twilio voice connectors, plus the substrate to add more channels as they come online.
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 live and coming messaging, automation, calendar, and contact 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.