Skip to main content
A chat channel connects a place where people talk to an agent. Every message arrives at the gateway first. The gateway checks who sent it, screens it, and only then delivers it to the agent. Replies travel back the same way. Agents do not integrate with chat providers themselves. They call one channel tool, and Tilde handles the provider’s API, credentials, and webhooks.

​
Supported channels

​
Connect a channel

1

Create a connection

In Connections, add the provider and complete its setup. See Connections.
2

Assign it to an agent

Open the agent’s Chat providers tab and assign the connection.
3

Choose who can message the agent

Set the access mode to private, public, or disabled. See End-user access.
4

Point the provider at Tilde

Copy the webhook URL that Tilde gives you into the provider’s settings.
Public chat providers deliver webhooks from the internet, so this one route needs a public HTTPS address. Nothing else does. See Network exposure.
Tilde verifies every webhook’s signature, rejects anything that fails, and ignores duplicate deliveries.

​
Build chat into your own app

Native Tilde chat lets your own applications talk to agents without a third-party provider. Your server authenticates the user and asks Tilde for an ingress token, optionally restricted to one thread. The browser never holds a management credential, and Tilde never trusts an identity that a browser supplies.

​
Realtime voice

Agents can take phone calls and speak in realtime. The Telnyx Voice channel connects a Telnyx phone number to an agent. Each call becomes a normal session, with the same access checks, audit trail, and review tools as a text conversation.
We recommend a sidecar deployment for voice agents. A caller hears every millisecond of delay. With a sidecar, runtime calls and LLM requests stay on loopback beside the agent, which gives the lowest latency between a caller finishing a sentence and the agent starting its reply.

​
Voice profiles

Voice settings belong to the agent. In the agent editor, select a voice profile, its models and voice, and a maximum call duration. With the first two profiles, your agent code does not change. It receives each spoken turn as text, and replies through the same channel tool. The OpenAI Realtime profile uses its own configured instructions, and does not inherit your agent’s tools.

​
Connect Telnyx Voice

You connect your existing Telnyx account, Voice API application, and phone number as a Telnyx Voice connection, and choose a default agent. Tilde can configure the Telnyx webhook for you, or give you the URL to set yourself. You then pick the agent’s voice profile, transcription model, voice, and language in the agent editor.
A live call is bidirectional, so Telnyx must reach your public ingress over HTTPS and a secure WebSocket. See Network exposure.
Conversation Relay needs no separate speech provider key. Your agent keeps using its own text model through an inference provider.

​
How calls behave

  • Interruptions. Callers can interrupt the agent. Tilde records what the agent generated and what the caller actually heard, so the agent’s next turn stays coherent.
  • Duration. Tilde ends a call at the agent’s configured maximum duration.
  • Recordings. Tilde stores call transcripts in the session. It does not retain audio recordings.
  • Caller identity. A caller ID identifies the participant for access control. It never authorizes access to a person’s own tools.

​
How messages are scheduled

Each agent chooses what happens when a message arrives while it is still responding. Set this in the agent’s Capabilities tab. Tilde owns this policy. Your agent code handles one invocation at a time and honours its cancellation signal.

​
How agents reply

An agent replies by calling the channel’s send tool, such as sendMessage. Each provider owns its tool’s schema and formats, so an agent on Slack can use Slack formatting, and an agent on email can set a subject. Model output is never sent automatically. A reply goes out only when the agent calls a channel tool. In Tilde Enterprise, it then passes through response guards before it reaches the provider.

​
Review conversations

Every conversation is a session. Review its messages, reasoning, and tool calls in the agent’s Sessions tab.