Evergreen guidance for teams building voice agents and conversational bots on OTIMO — practical starting points, not a fixed publishing calendar.
A handful of solid entry points, whichever product — or both — you're building with.
From choosing a telephony provider to placing your first automated call: what to configure first, and why BYOK teams should decide on their LLM/STT/TTS stack before they touch the flow builder.
Read the overview →Start simple, then expand. A single trigger → AI intent node → response is enough for a working v1 — resist the urge to model every edge case before you've tested the happy path in Preview.
Read the overview →Both run the same platform underneath. Self-hosted suits teams with data-residency or compliance constraints who want to bring their own keys; managed suits teams who want the fastest path to production.
Compare deployment models →WhatsApp, RCS, Telegram, Messenger, and Instagram all run on the same node library. Build one flow definition and it renders natively per channel — no separate builder per channel.
See supported channels →Healthcare (emergency triage, identity verification) and debt collections (FDCPA disclosure, dispute rights) templates give regulated teams a safer starting point than a blank canvas.
See starter templates →If you operate multiple brands or business units, keep bots, connections, contacts, and analytics scoped per workspace from day one — retrofitting isolation later is far more work than starting with it.
Read about governance →Dive into the developer overview or talk to us about your use case.