Core concepts

Essentially, Enok can be described as a platform for developing conversational chat and voice agents based on your enterprise knowledge, extending their capabilities with tools and integrations and distributing them through different channels like chat widgets and phone numbers. Any solution created on the basis of Enok is built using a small set of basic components which work in harmony. Getting acquainted with these basic components will simplify the understanding of the solution architecture and configuration processes.

Agents

An agent is the conversational assistant your users interact with. It is created from a template that sets an initial personality, then shaped through a name, a first message, a base prompt. Voice behaviour is controlled separately through a Voice Playbook. An agent begins in a draft state and becomes active only after it is deployed.

Learn more in AI Agents.

Knowledge bases

A knowledge base is your own content, structured into collections and articles. A collection is a container, a logical grouping of source material. Articles are the individual pieces of content inside it: PDFs or web pages that Enok reads, indexes, and makes available for semantic retrieval.

When a collection is attached to an agent, the agent searches it by meaning rather than keyword. This means the agent can find the most relevant passage in response to a question even when the user's wording does not match your source text verbatim. All content is private to your workspace. Attach a collection to an agent in its General settings.

Learn more in Knowledge.

Tools & Webhooks

A tool is a distinct capability allocated to an agent. The description of the tool, its usage cases, and timing is written by you for the agent, who will then decide independently if he needs to use the tool in the dialogue. Webhook is an actual API connection underpinning a tool, it contains the request method, endpoint, headers, params, and secrets. The separation means a webhook can be built once and shared across multiple tools.

Learn more in Tools and Webhooks.

Phone numbers

A phone number in Enok is a live telephone line, imported from a provider such as Twilio or connected via a custom SIP endpoint, that is assigned to a voice agent. When an inbound call arrives on that line, Enok routes it into a live session with the assigned agent. A number routes to one agent at a time.

Learn more in Phone numbers.

Deployments

Deploying an agent provisions the runtime that makes it accessible. There are two deployment surfaces:

• Chat widget - an embeddable component you drop onto a web page. Configurable for theme, size, position, interaction mode (text, audio, or both), and optional feedback and terms prompts.

• Phone - an assigned telephone number that turns inbound calls into voice sessions with the agent.

Learn more in Deploy an agent.

Conversations & history

Every interaction, whether a chat session or a phone call, produces a conversation record with a full transcript and a status. These records feed the per-agent dashboard metrics, surface the most common user intents, and populate a fallback report of questions the agent failed to answer. Individual transcripts can be read or downloaded from the History tab.

Learn more in Dashboard & history.