A voice agent that resolves common tickets
Attach a knowledge base, collect the issue details, call internal APIs, and send a webhook when the session ends.
Design the agent, connect tools and knowledge, test live sessions, and publish a versioned realtime agent. Talqing handles the LiveKit runtime, session records, webhooks, usage, and operational glue.
Built for teams replacing manual conversations
From agent idea to live session, without a worker repo.
Talqing turns no-code configuration into a running realtime agent, then keeps every call observable and versioned.
Talqing keeps agent authoring, runtime configuration, testing, and publishing in one place, so teams can improve behavior without shipping a new service.
Talqing is built around the same primitives engineers use in LiveKit agent code, but exposed as product controls that non-engineers can actually operate.
Realtime browser calls with STT, LLM, TTS, VAD, interruption settings, transcripts, and usage tracking.
Avatar-backed sessions for face-to-face experiences, configured from the same no-code agent model.
An embedded AI builder that can update prompts, models, tools, hooks, knowledge, and publish state.
Compose HTTP calls, code steps, frontend RPC, MCP/provider operations, handoffs, and webhook actions.
Crawl, review, build, and attach knowledge so agents can fetch grounded answers at runtime.
Review calls, transcripts, tool invocations, final userdata, provider usage, and cost breakdowns.
Turn repeatable customer conversations into agents that can answer, collect data, trigger actions, and hand off when needed.
Prototype a new conversational experience without waiting for a custom LiveKit worker or tool integration sprint.
Give customers a voice-first front door backed by your docs, CRM actions, and clear call history.
Keep control over models, tools, hooks, webhooks, secrets, and runtime behavior without becoming the bottleneck for every edit.
Voice and video agents become valuable when they can remember session state, take actions, and leave an auditable trail.
Attach a knowledge base, collect the issue details, call internal APIs, and send a webhook when the session ends.
Ask adaptive questions, store lead fields, trigger a CRM action, and hand off to another agent when the buyer is ready.
Use the same agent definition with a video channel, a selected avatar, and frontend actions for interactive UI moments.
Talqing is for building voice, video, and text AI agents that can talk to users, use tools, retrieve knowledge, call webhooks, update session state, and hand off to other agents. The core focus is realtime voice and video agents.
No. You author an agent definition in the dashboard or through Talqing Copilot. Talqing compiles that definition into a LiveKit AgentSession and runs it through the platform runtime.
Talqing handles the agent runtime, published versions, session dispatch, transcripts, tool execution, webhooks, knowledge retrieval, usage collection, and cost breakdowns. You focus on the agent behavior and connected business systems.
Yes. You can run browser voice, text, and video test sessions, then inspect the transcript, tool calls, userdata, usage, and cost for each session before publishing a version.
Tools are built as operation trees. You can configure HTTP requests, conditional branches, code operations, generated replies, frontend RPC, MCP/provider operations, handoffs, end-call actions, and webhook-triggered flows from the UI.
Yes. Talqing can crawl and build knowledge bases, let you review the extracted pages and structure, and attach those knowledge bases to agents so runtime calls can fetch grounded context.
Yes for bring-your-own Plivo and Exotel. Connect a carrier account under Phone Numbers, import DIDs, assign a published voice agent for inbound, and place outbound test calls from the dashboard. PSTN billing stays with your carrier; Talqing runs the agent. Twilio/Telnyx, transfers, DTMF, and batch dialers are planned next.