---
title: "Interaction counting"
url: "/reference/interaction-counting"
description: "How KlicForge counts interactions against your monthly plan allowance, with worked examples."
productArea: reference
audience: ["business-user", "admin"]
tags: ["usage", "billing", "plans"]
lastReviewed: 2026-08-26
---

# Interaction counting (/reference/interaction-counting)





Every KlicForge plan includes a monthly allowance of **interactions**. This page explains
exactly what counts as one, so you can predict your usage.

## What counts as one interaction [#what-counts-as-one-interaction]

An interaction is charged **per user turn**, not per message exchanged. One turn covers
everything the agent does in response: reading its knowledge, calling tools, thinking, and
writing its reply.

The rule is:

```text
interactions for a turn = 1
                        + 1 for each attachment the user sends
                        + 1 for each file the agent sends back
```

### What does not count [#what-does-not-count]

None of the following add to your interaction count:

* **Tool calls.** An agent that calls six tools to answer one question still costs one
  interaction.
* **Retries and internal steps.** Intent detection, image analysis, transcription and
  conversation summaries are all part of running the platform, not separate interactions.
* **Turns that never reach the model.** If a request fails before the agent responds, it is
  not charged.
* **Agent replies on their own.** Only user turns start the count.

<Callout type="info">
  Attachments are counted individually because each one is processed separately — an image is
  analysed, a document is read, a voice note is transcribed.
</Callout>

## Worked examples [#worked-examples]

| What happened                                                                        | Interactions |
| ------------------------------------------------------------------------------------ | ------------ |
| A visitor asks a question, the agent answers                                         | 1            |
| A visitor asks a question that makes the agent search knowledge and call three tools | 1            |
| A visitor sends a message with two photos attached                                   | 3            |
| A visitor sends a voice note                                                         | 2            |
| A visitor asks for a document and the agent sends one file back                      | 2            |
| A conversation with ten back-and-forth user messages, no attachments                 | 10           |
| Scanning a website to see how many pages it has                                      | 0            |
| Importing 25 pages from a website                                                    | 25           |

## Scheduled tasks, evaluations, website imports and demo links [#scheduled-tasks-evaluations-website-imports-and-demo-links]

**Scheduled tasks** that send a message through an agent are charged the same way as a user
turn. A scheduled or [audience message](/scheduled-tasks/audience-messages) that carries an
[image attachment](/scheduled-tasks#attaching-an-image) costs 2 interactions instead of 1 — the
same "+1 per attachment" rule as a chat turn — charged per recipient.

A self-service [memory or business intelligence rebuild](/memory#rebuilding-a-contacts-memory)
costs **1 interaction per conversation re-read**. Rebuilding both memory and intelligence
together costs the same as rebuilding either one alone, since they share a single pass over each
conversation. The dashboard shows the exact cost before you confirm, and blocks the rebuild
rather than running it if it would exceed your remaining allowance.

**Website imports** are charged **one interaction per page imported**. Scanning a site to see
how many pages it has — and what importing them would cost — is free, so you always see the
price before you commit. You choose the page limit before the import starts, and that limit is
the most you can be charged. Pages the site fails to return are not charged, and turning the
generated documents into knowledge costs nothing further.

**Evaluations** are charged per simulated user turn, plus one interaction for each test case
that uses the AI judge. A single-turn test case scored by the judge therefore costs 2
interactions. Test cases using only deterministic checks cost no judge interaction. The
estimate shown before you start an evaluation run uses these same rules.

**[Demo links](/channels/demo-links)** create real conversations, charged exactly like a
conversation through your live widget.

## Monthly allowances [#monthly-allowances]

| Plan       | Interactions per month |
| ---------- | ---------------------- |
| Starter    | 50                     |
| Startup    | 500                    |
| Growth     | 2,000                  |
| Business   | 10,000                 |
| Enterprise | Unlimited              |

Allowances reset at the start of each calendar month.

## Where to check your usage [#where-to-check-your-usage]

Open **Settings → Usage** in the dashboard at
[app.klicforge.ai](https://app.klicforge.ai) to see interactions consumed this month, your
remaining allowance, and a breakdown by agent. Owners and admins only.

## Related pages [#related-pages]

* [Documentation home](/)