Core Concepts
How Agents, Channels, and Tools work together in Taliiq
Taliiq separates what the agent is, where it runs, and what it can do. Your dashboard sidebar follows the same model.
The three pillars
Agents
Prompt, voice stack, guardrails, and tools — configured on Brain, Voice, Actions, and Guardrails tabs. Test in Agent Console.
Channels
The front door — web widget, SIP, or phone routes that connect end users to a published agent.
Tools
The hands — HTTP actions, MCP servers, and integrations the agent can call during a conversation.
Outbound
Batch voice campaigns with CSV or contact-book dial lists.
Contacts
Shared contact book — search, CRUD, and outbound linking on all plans.
Agents
An agent is a published configuration (active, not draft) with at least:
| Piece | Purpose |
|---|---|
| System prompt | Personality, rules, and business logic |
| Capabilities | Voice, chat, or both |
| Brain | System prompt, model, first message, knowledge files |
| Voice | Speech-to-text, language model routing, text-to-speech (voice agents) |
| First message | How the agent greets the user |
You create agents under Build → Agents. The quickstart walks through the wizard without requiring custom integrations.
Channels
A channel binds one agent to a delivery surface:
| Channel | Typical use |
|---|---|
| Web widget | Chat or voice on your site |
| SIP / phone | Inbound or outbound telephony |
An agent must be deployed before a channel can use it. One agent can power multiple channels.
Tools
Tools are optional. They let the agent call your APIs or MCP servers mid-conversation.
Attach tools on the agent Actions tab, or manage shared tools under Build → Tools.
Supporting pieces
| Area | Role |
|---|---|
| Voice Library | Pick voices for the TTS pipeline |
| Files | Knowledge documents for RAG or inline context |
| Contacts | Org-wide contact book for widget, outbound, and CRM |
| Integrations | Bring your own providers — not required for first tests |
| Logs | Sessions, webhooks, and audit history |
Typical lifecycle
Design — Create an agent in the wizard; test in Agent Console.
Deploy — Mark the agent active so channels and campaigns can use it.
Connect — Add any channel (web widget, SIP, phone, or outbound) pointing at that agent.
Operate — Monitor Logs; iterate on prompt, tools, or knowledge files.
Automate — Use API Keys and the API Reference for production integrations.
Member docs match the live dashboard: Build, Operate, Manage, and Observe in the left sidebar.