How Kontakt works
A short mental model of Kontakt and a glossary of the words you see across the app and these docs.
Kontakt sits between your customers and your team. Customers message you on the channels they already use. Those messages land in one inbox, where an AI agent can answer, hand over to a person, or take an action in your systems. Separately, you can reach out first, with automated journeys and one-time broadcasts. Everything happens inside a workspace, and usage is paid for with credits.
The big picture
Think of Kontakt in four layers.
- Where customers reach you. Channels such as WhatsApp, Instagram, Messenger, email, SMS, and the web widget. You connect them under Settings.
- Who answers. Conversations from every channel arrive in Conversations. An AI agent replies first on the channels you bind it to, and hands over to your team when it can't help.
- What the agent knows and can do. Agents answer from your knowledge and follow skills. Skills call tools, for example to look up an order or check a wallet balance.
- How you reach out. Journeys react to events and run multi-step flows. Broadcasts send one message to an audience once. Both use your templates and respect your contact policy.
Glossary
Workspace
A workspace holds one business, brand, or team's data: people, conversations, channels, AI agents, knowledge, campaigns, API keys, and billing. Workspaces don't share data with each other. Each has its own team members and its own plan and credit balance. See Workspaces.
Firm
Your firm is the company account that owns your workspaces. When you sign up, Kontakt creates a firm and a first workspace for you. If you belong to workspaces in more than one firm, the workspace switcher groups them by firm name.
Team members and roles
People on your team who sign in to a workspace. Each member has one role in that workspace, and the role decides what they can see and change. See Team members and Roles and permissions.
Channels
The places customers talk to you: WhatsApp, Instagram DMs, Messenger, email, SMS, voice, USSD, push notifications, and the web widget or hosted chat page. Each channel is connected once per workspace under Settings. Some channels charge per message. See Channels and Channel pricing.
Conversations
A conversation is the thread between one customer and your workspace on a channel. It can be handled by an AI agent, assigned to a team member, or both in turn. You work them in Conversations. See Conversations and Routing.
People
Your customers and contacts. Each person has a profile with contact details, custom fields, tags, and their history with you. Kontakt adds people when they message you, and you can import them or create them through the API. See People.
Audiences
Saved groups of people defined by filters, such as "VIP customers in Lagos". Broadcasts and journeys target audiences. See Audiences.
Agents
An AI agent is the assistant that replies to customers. It has a name and a persona, it is bound to the channels where it should answer, and it mounts a set of skills. You manage agents under AI, in Agents. See Agents.
Skills
A skill is one thing an agent knows how to do, written as a procedure: "Track an order", "Book an appointment", "Handle a refund request". Skills are versioned, so you can see changes and roll back. See Skills.
Tools
Actions a skill is allowed to take while it handles a conversation, such as searching knowledge, handing over to a person, looking up a customer, or calling your own API. Built-in tools come with Kontakt. Shopify adds catalog tools, and custom API tools connect your systems. See Tools and Custom API tools.
Knowledge
The material your agents answer from: your website, uploaded files, pasted text, Google Drive documents, and past conversations. Kontakt compiles it into a knowledge wiki that records where each fact came from. See Knowledge.
Reviews and training
Ways to check and improve what agents say. Supervised replies wait in Reviews for someone to approve, edit, or reject them. Training imports past conversations so agents learn your voice, knowledge, and skills, and Voice keeps real reply examples that shape how agents sound. See Reviews and training.
Journeys
Automated, multi-step flows that run for each person who enters them. A journey can start from an event, a segment, or an inbound WhatsApp message. Its steps can wait, check a condition, send messages, update a profile, credit a wallet, or hand over to your team. You build them in Campaigns. See Journeys.
Broadcasts
A broadcast sends one message to an audience, once, now or at a scheduled time. Use broadcasts for announcements and promotions. See Broadcasts.
Templates and content
Reusable messages, including the WhatsApp templates Meta must approve before you can send them outside a customer's service window. You manage them in Content. See Content and templates.
Events
Records of something a customer did, such as "signed up", "placed an order", or "missed a payment". Your systems send events to Kontakt through the API or a webhook source. Events can start a journey, resume a journey that is waiting for them, and mark an AI conversation as resolved. You can browse them in Events. See Events and Ingestion.
Outcomes
How Kontakt knows something worked. On an agent, a resolution event names the event that counts as success, for example kyc_complete. When that event arrives for the customer, the agent's conversation is marked resolved. In a journey, the end step records an outcome name and can count the run as a conversion. See Agent health and Journeys.
Credits
The unit Kontakt uses to charge for usage. AI replies use credits, and so do messages on channels that charge per message. Plans include credits each period, and you can top up. Each AI reply costs $0.03. Your balance shows in the top bar. See Credits and top-ups and Plans.
How a message flows
- A customer sends a WhatsApp message.
- Kontakt finds or creates that person and opens or continues their conversation.
- If an agent is bound to that WhatsApp connection, the agent picks a skill, searches your knowledge, and may call a tool. It then replies.
- If the agent can't help, it hands over to your team. When the conversation is assigned to someone, they get a notification.
- The reply uses credits for the AI turn, and the channel may charge for the message.
- If your system later sends a matching event, the outcome is recorded, and any journey waiting for that event continues.