---
title: "Domain packs"
url: "/agents/domain-packs"
description: "Tell KlicForge what kind of business an agent serves, so memory and business intelligence extract the right things."
productArea: agents
audience: ["business-user", "admin"]
tags: ["domain-packs", "memory", "business-intelligence"]
lastReviewed: 2026-08-25
---

# Domain packs (/agents/domain-packs)



A domain pack is configuration that tells KlicForge what kind of business an agent serves, so
the platform knows what to extract, remember, and track across conversations. Without one,
KlicForge treats every conversation generically. With one, an agent's [memory](/memory) and
business intelligence become domain-aware — they extract the right entity types, event types,
and memory keys for that specific business context.

## Why configure a domain [#why-configure-a-domain]

Before you can enable memory on an agent, you must select a business domain. This is a
deliberate gate — the extraction pipeline needs to know what to look for (orders, appointments,
student progress) to produce useful output instead of noise.

[Business intelligence](/intelligence) does not share this gate — it discovers your business's
vocabulary from your own conversations, so a domain pack is an optional head start rather than a
precondition.

Configuring a domain has no plan requirement of its own — every plan can select one. Memory
requires a plan that includes it and stays locked until a domain is configured. Business
intelligence has no plan requirement and no domain requirement — it is available on every plan
with nothing to configure first.

## The intelligence layer [#the-intelligence-layer]

On the agent's **Settings** tab, the **Intelligence Layer** section groups three settings:

1. **Business domain** — pick packs from the catalog. Configure this first if you plan to use
   memory.
2. **Memory** — persistent per-contact memory across conversations.
3. **Business intelligence** — event extraction and a self-building vocabulary of your business.
   See [Intelligence](/intelligence).

## Pack catalog [#pack-catalog]

KlicForge ships 15 domain packs across three categories.

### Core packs [#core-packs]

| Pack                      | Best for                                                             |
| ------------------------- | -------------------------------------------------------------------- |
| Generic business          | Always included automatically — baseline extraction for any business |
| Contact and CRM memory    | Remembering contacts, their preferences, and relationship history    |
| Tasks and follow-ups      | Action items, reminders, and follow-up tracking                      |
| Documents and knowledge   | Document requests, knowledge references, policy lookups              |
| Appointments and bookings | Scheduling, reservations, and booking management                     |

### Vertical packs [#vertical-packs]

| Pack                   | Best for                                         |
| ---------------------- | ------------------------------------------------ |
| Commerce and orders    | Orders, products, payments, and delivery         |
| Delivery and logistics | Dispatch, tracking, and last-mile delivery       |
| Customer support       | Support tickets, issue resolution, escalations   |
| Professional services  | Client cases, engagements, and case management   |
| Education and tutoring | Lessons, progress, and learning goals            |
| Personal assistant     | Daily tasks, personal preferences, and lifestyle |

### Sensitive packs [#sensitive-packs]

These handle personally sensitive data and display an elevated or restricted badge in the
dashboard. Select them only when the use case genuinely requires it.

| Pack                    | Best for                                                      |
| ----------------------- | ------------------------------------------------------------- |
| Legal                   | Case facts, legal references, and regulatory matters          |
| Healthcare and wellness | Health data, symptoms, care instructions                      |
| Children's education    | Child learning data, with additional privacy controls applied |
| Finance and advisory    | Financial data, goals, portfolio references                   |

## Selecting packs [#selecting-packs]

From the agent's **Settings** tab, under **Intelligence Layer → Business Domain**:

1. Choose a **primary pack** — the main domain this agent serves. This sets the primary
   extraction schema.
2. Optionally add **secondary packs** to extend coverage — for example, a catering agent might
   use Commerce and Orders as primary, with Appointments and Bookings and Delivery and
   Logistics as secondary.

**Generic Business** is always active and never needs to be selected — it applies automatically
as a baseline, so even an agent with no explicit pack configuration produces useful memory
output.

When you create an agent from a template, the wizard applies the template's recommended packs
automatically. Change them afterward from the agent's Settings.

## How packs affect extraction [#how-packs-affect-extraction]

When a conversation ends, extraction reads the applied packs and uses their entity types, event
types, and memory key hints to guide what becomes a memory atom — a commerce pack extracts
preferred items and delivery preferences, an education pack extracts lesson topics and learning
gaps. The same pass produces the [business intelligence](/intelligence) events.

A pack is a **head start, not a limit**. Its event types are offered as the preferred vocabulary,
and anything your conversations turn out to be about that no pack anticipated is still recorded —
a restaurant discussing halal certification, an agency discussing viewing times. Nothing is
discarded for not appearing in a pack.

What a pack adds beyond the names is the shape of each event: what the type means, which
[labels](/intelligence#what-each-event-records) it should be countable by, and which details to
capture. The Tasks and Follow-Ups pack is what tells extraction that a created task should record
what it is about as a label while keeping the task's own wording in the encrypted detail — so
attaching a pack that fits your business makes the resulting events far more useful to count,
even though you would get events either way.

## Common configurations [#common-configurations]

| Use case                    | Primary pack           | Secondary packs                                   |
| --------------------------- | ---------------------- | ------------------------------------------------- |
| Catering or food ordering   | Commerce and Orders    | Appointments and Bookings, Delivery and Logistics |
| Home-based business         | Commerce and Orders    | Delivery and Logistics, Customer Support          |
| Personal assistant          | Personal Assistant     | Tasks and Follow-Ups, Appointments and Bookings   |
| Financial advisor assistant | Finance and Advisory   | Contact and CRM Memory, Tasks and Follow-Ups      |
| Tutor or homework help      | Education and Tutoring | Children's Education                              |
| Customer support agent      | Customer Support       | Contact and CRM Memory                            |

## Related pages [#related-pages]

* [Agents](/agents)
* [Memory](/memory)
