Connect to everything.
Connect documented platform resources first: agents, phone numbers, SIP trunks, conversations, analytics, API keys, and SDKs. Custom systems get an implementation path instead of a vague connector promise.
REST
Public API
OpenAPI
Spec
TS SDK
SDK Docs
API Keys
Auth
Phone Numbers
5 activeTelephony
Numbers and trunks as platform resources.
Manage phone numbers, SIP trunks, and BYOC routing requirements through the same operating model as your voice agents.
Hannah Lehmann
Acme GmbH · Procurement
h.lehmann@acme.eu
Activity
Discovery call
Tom · 18 min
Proposal sent
CRM sync · 2d ago
Follow-up scheduled
Mar 14, 10:30
Business Systems
Map the workflow before connecting.
CRM, calendar, helpdesk, and operational systems need clear data rules. We confirm what can be connected directly and what needs custom implementation.
import { Itellico } from '@itellico/sdk'
const client = new Itellico({
apiKey: process.env.ITELLICO_KEY,
})
const agent = await client.agents.create({
name: 'Reception',
voice: 'de-AT',
direction: 'inbound',
})Custom & Developer
Build on the public API.
Use the REST API, OpenAPI spec, TypeScript SDK docs, and API keys to create agents, manage telephony resources, read conversations, and pull usage analytics.
Industry connectors.
Common implementation patterns for CRM, support, and regulated workflows.
CRM & Sales
Connect conversation outcomes to contacts, leads, tasks, and follow-up work when the data model is confirmed.
Helpdesk & Support
Move unresolved conversations into support queues with context, priority, and the next action clearly attached.
Healthcare
Healthcare workflows need careful scoping. We map scheduling, identity, consent, and staff handoff rules before implementation.
How it works
Three steps to connected.
Map the resource
Start with the documented API resources: agents, phone numbers, SIP trunks, conversations, analytics, and API keys.
Confirm the auth path
Use API keys for documented access. For customer systems, define OAuth, service accounts, or a custom secure path during implementation.
Release with controls
Test the call flow, data writes, and handoffs before production. Keep every action reviewable after launch.
Developer API
Full control, programmatically.
Create agents, manage telephony resources, read conversations, and query usage analytics. The docs expose the API reference, OpenAPI spec, TypeScript SDK, and API key flow.
POST /v1/accounts/{account_id}/agents
{
"name": "Reception Agent",
"language": "de-DE",
"direction": "inbound",
"handoff": "support-team"
}
201 Created — Agent configured
Ready to connect?
Start with the documented API surface. We will map any custom system connection before implementation.
No credit card required