Connect your stack
Channels share one data plane: one contact identity, one conversation history, durable delivery for async sends. Agents book on a native calendar, call your APIs over HTTP, and can run on your own model keys.
Plans open the whole platform. Usage is billed as you go.
Explore the capabilities and controls behind this part of your deployment.
Inbound messages normalize at the edge into one canonical shape and run one pipeline: dedup, identity, middleware, conversation, brain, persist, deliver. Adding a channel touches one adapter file and one webhook route. Nothing else changes.
Identity resolution maps each channel address to one contact before the agent runs. A caller who texts later is the same contact with the same history, and a web chat visitor links up once they share a phone or email, so agents answer with context instead of starting over.
Async sends queue in a durable outbox instead of firing and forgetting. A minutely cron claims pending rows atomically and retries failures with exponential backoff. Exhausted or non-retryable sends are marked failed with the provider error attached to the message.
The native calendar is the system of record: working hours, buffers, lead time, booking horizon, seats per slot, blackout dates. Assistants check real availability and write bookings directly. External sync is write-behind: a failure marks the booking, never blocks it.
Custom tools give agents HTTP access to your systems mid-conversation: URL, method, headers, and JSON-Schema parameters, with variable substitution across URL, query, headers, and body, and an SSRF guard that blocks private-network URLs. One tool definition serves voice and chat.
Bring your own model keys for OpenAI, Anthropic, or OpenRouter; they are stored server-side and read back only as masked hints. Platform API keys are scoped read-only, read-write, or admin, hashed with SHA-256, and shown once at creation.
At scale
Connecting a channel means pointing its webhook at one route. Web chat, SMS, and voice share contact identity and conversation history from the first message, with no per-channel plumbing to rebuild.
Sandbox is separated end to end: sk_test_ API keys and environment-stamped conversations, calendars, and tools. A full-loop simulator replays redeliveries, blocked senders, retries, and permanent failures.
The durable outbox absorbs provider flakiness. Atomic claims, backoff from 30 seconds to an hour, and a minutely retry cron turn a slow provider into delayed delivery instead of dropped messages.
Observability is per-record: each booking carries its sync status and last error, every outbox row keeps its attempt count and last provider error, and failed sends attach that error to the message.
Under the hood
Your questions
Each channel is two pieces: an adapter that renders and sends outbound messages, and a webhook route that parses the provider payload into a canonical envelope. Identity, conversations, the agent brain, and delivery retries are shared, so nothing else changes when a channel is added.
Outbound messages sit in a durable queue, not a fire-and-forget API call. Retries back off from 30 seconds to an hour across 5 attempts, and a minutely cron sweeps stuck deliveries. Calendar bookings write to the native calendar first, so an integration outage never blocks a live booking.
The native calendar is the system of record, so a booking never depends on an external system. Calendar sync is write-behind: each booking records its own sync status and error, and a failed sync re-drives with one API call. For CRMs and other systems, agents call your APIs directly through HTTP tools during a conversation.
Yes. Connect OpenAI, Anthropic, or OpenRouter keys in settings; they are stored server-side and read back only as masked hints. Turns on your own keys are not metered as platform LLM usage. Platform pricing stays usage-based: $0.02 per message, published voice rates, free pay-as-you-go signup.
Environments are stamped through the stack: conversations, calendars, and tools carry an environment column, and API keys are prefixed sk_test_ or sk_live_ per environment. You can exercise the full pipeline in sandbox before pointing production traffic at it.
“I feel confident injecting Assistable into all my clients' accounts; it does what it needs to do. I've been using it for over a year now, and I wouldn't switch to any other platform.”
Karl BrussoloAssistable customerBring your workflow. We’ll work through the requirements together.
