Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.usefini.com/llms.txt

Use this file to discover all available pages before exploring further.

Overview

Tags are labels that Fini applies to every conversation automatically, in real time. They’re organised into tag groups. Each group represents a single classification dimension, and Fini evaluates each conversation against your instructions to pick the right tag within that group. Tags serve two purposes:
  • Visibility: see patterns across your conversations: what topics customers ask about, why escalations happen, how your AI agent is performing
  • Logic: use tag values as conditions in Rulebook rules, so your AI agent behaves differently depending on how a conversation is classified
Tags page showing tag groups list with Mandatory and Default badges

How tags work

After each message exchange, Fini evaluates every active tag group against the conversation. For each group, Fini reads your AI Instructions (the decision rules you’ve written) and applies the most appropriate tag from that group. This happens automatically. You don’t trigger it and customers don’t see it. The tags accumulate on the conversation and are visible in Inbox. The quality of your AI Instructions directly determines the accuracy of your tags. A vague instruction produces inconsistent results. A specific instruction with clear decision rules, like “apply escalated if the AI agent used the phrase ‘let me connect you with our team’, apply resolved if no follow-up is pending”, produces reliable, actionable tags.

Types of tag groups

Mandatory

Mandatory tag groups are always active on every conversation across every AI agent. You cannot edit, delete, or disable them. The most important mandatory group is Conversation Status, which has three tags:
TagWhen it applies
ResolvedThe AI agent gave a complete answer and no follow-up is pending
Escalated to Human AgentThe conversation was handed off to a human
Waiting for CustomerThe AI agent asked for something and is waiting for the customer to respond
Mandatory tag groups are system-managed. You cannot add, edit, or remove their tags.

Default

Default tag groups are pre-built by Fini and available to all accounts. Unlike Mandatory groups, you choose which AI agents they apply to. They are not automatically active on every AI agent. Default groups cover common classification needs out of the box. Assign them to an AI agent when you want that classification dimension tracked without building it from scratch.
Tags list showing Default and Mandatory badges on tag group cards

Custom

Custom tag groups are ones you create from scratch for your specific needs. They are fully editable: you define the title, description, instructions, which tags belong to the group, and whether the group is available as Rulebook conditions. Two patterns cover most use cases: Classification groups: categorise what conversations are about. Use these to understand your conversation mix and surface trends. Examples:
  • Product area (billing, onboarding, technical, account access)
  • Type of query (refund request, status check, feature question)
Guardrail groups: monitor whether your AI agent behaved correctly. Use these for quality assurance and compliance auditing. Examples:
  • PII Redaction: did the AI agent reveal personal data it shouldn’t have?
  • Tone & Compliance: did the AI agent use neutral, non-accusatory language?
  • Claim Safety: did the AI agent make unsupported product claims?
Guardrail groups are especially useful in regulated industries where AI behaviour needs to be auditable. Apply them to every AI agent and review flagged conversations in Inbox regularly.

Creating a tag group

Create New Tag Group form showing all input fields
1

Click + New Group

Opens the create form inline on the page.
2

Fill in the group details

  • Group Title: a short, descriptive name for the classification dimension (e.g. “Type of Issue”, “Guardrail | PII Redaction”)
  • Group Description: human-readable context for your team about what this group classifies
  • AI Instructions: the decision rules telling Fini how to evaluate the conversation and when to apply each tag. You can add this after creating the group, but it is critical for accuracy.
3

Enable Rulebook access if needed

Toggle Tag Group available in Rulebooks on if you want this group’s tags to be usable as conditions in Rulebook rules. You can change this later.
4

Click Create Group

The group is created and you land on the group detail page, where you can add individual tags.

Adding tags to a group

Once inside a tag group, the Tags section at the bottom of the page is where you add the individual values the AI can apply.
Tag group detail page showing Tag Selection setting and the Tags section with existing tags
To add a tag:
  1. Enter the tag name: use short, machine-readable values (e.g. resolved, user_denied, billing_dispute). These are what you reference in Rulebook conditions and see in Inbox filters.
  2. Enter the description: this doubles as the decision rule for when to apply this specific tag. Be specific. Include example messages that should and shouldn’t trigger it.
  3. Click + Add.
Repeat for each tag in the group. You can edit or delete individual tags using the icons on the right of each tag row.
Write tag descriptions as if explaining the decision to a junior team member. “Apply this tag if the customer explicitly asked for a refund” is far more reliable than “Apply for refund-related conversations.” The AI follows your rules exactly as written.

Tag Selection

Each tag group has a Tag Selection setting that controls how many tags the AI can apply per conversation:
  • Exactly one tag is selected: Fini must pick exactly one tag from the group. Use this when options are mutually exclusive (e.g. Resolved vs. Escalated vs. Waiting for Customer).
  • Multiple tags can be selected: Fini can apply more than one tag from the group to the same conversation. Use this when a conversation can belong to multiple categories at once (e.g. a conversation about both billing and account access).

Assigning tag groups to AI agents

Default and Custom tag groups must be explicitly assigned to each AI agent before they become active. Mandatory groups are always active and do not need assignment.
Tags page in assignment mode with AI agent selected and checkboxes visible on each group
To assign a group to an AI agent:
  1. Click the AI agent selector dropdown in the top right of the Tags page and choose an AI agent.
  2. Checkboxes appear on each tag group card.
  3. Check the groups you want active for that AI agent.
  4. Click Save.

Connection to Rulebook

Tags and Rulebook are designed to work together. The full loop:
  1. Customer sends a message
  2. Your AI agent responds
  3. Fini evaluates every active tag group and applies the appropriate tags
  4. Rulebook reads those tag values and evaluates any rules that use them as conditions
  5. If a condition matches, the rule fires, routing the conversation, triggering a handoff, or changing reply behaviour
This means tags aren’t just analytics labels. They are live signals that drive how your AI agent behaves. To make a tag group available as a Rulebook condition, open the group’s overview and toggle on Tag Group available in Rulebooks. Once enabled, that group’s tags appear in the Rulebook Check step’s condition builder.
Tag group detail page showing the Tag Group available in Rulebooks setting

Example rules driven by tags

Escalation based on a guardrail group:
IF pii_detected → escalate to compliance team immediately
Routing based on topic:
IF Type of Issue = billing → route to billing specialist queue
Confirmation flow:
IF Action Confirmation = user_confirmed → proceed with the action
IF Action Confirmation = user_denied → send apology and offer alternatives
Mandatory tag groups (including Conversation Status) are not available as Rulebook conditions. Only Custom groups with the toggle enabled can be used.
Use tag values as your first choice for Rulebook conditions. Tags are set before a Rulebook rule runs, making them the most reliable signal for branching logic, more reliable than User Attributes or Read step extraction.

Rulebook

Use tag values as Check step conditions to route and branch conversations.

Attributes

User Attributes provide complementary context fetched automatically with every message in the conversation

Inbox

Filter and review conversations by tag value. Conversation Status drives the status badge on every conversation.

Analytics

View tag distribution across conversations over time.