What is the difference between LiveAgent's AI Chatbot and an AI Agent?

The AI Chatbot sits on your website or in a chat widget, answering questions as a customer types them in real time. An AI Agent works from inside your ticket queue: a dispatch rule assigns it to one or more departments, and it picks up unassigned tickets there the same way a human agent would, without a customer needing to start a live chat.

Do I need to set up an AI Chatbot before I can use an AI Agent?

No. The two features are independent. You can run an AI Agent on your ticket queue without ever enabling the AI Chatbot widget, and the reverse is also true. Most teams that use both set them up separately, since they solve different problems: the chatbot handles live conversations, the AI Agent handles queued tickets.

How much does it cost to run an AI customer service agent in LiveAgent?

Usage is billed against the AI budget you assign to the dispatch rule, not a flat monthly fee on top of your plan. You set the budget size when creating the rule, and usage from that department's AI-handled tickets draws from it, so cost stays predictable and capped.

Can I limit an AI agent to only reply once per customer?

Yes. The dispatch mode setting on the rule controls this. 'Once per ticket' replies to a ticket a single time, then hands any follow-up from that customer to a human agent. 'Each time the ticket is queued' re-runs the agent whenever the ticket re-enters the queue, for example after a customer reply, which suits simpler, repetitive request types better than complex ones.

What happens if I don't set up a dispatch rule for a department?

Nothing changes. A department with no dispatch rule keeps working exactly as it did before: unassigned tickets wait for a human agent or your existing automation rules, unaffected by AI Agent features running elsewhere in the account. You can add a rule to that department later without touching any of the rules already running on other departments.

Can one AI agent cover more than one department at once?

Yes. A single dispatch rule can target several departments together, and you can also create separate rules pointing the same AI agent at different departments if you want different budgets or dispatch modes per department. Most teams start with one rule covering their highest-volume department, then split rules apart once each department needs its own budget or dispatch mode.

How do I know if the AI agent is actually working?

Check the department's ticket list for tickets marked as handled by the AI agent, and watch the AI budget's usage against the amount you allocated. A rule that never shows AI-handled tickets after a day of normal ticket volume usually means the department has no unassigned tickets reaching it, not that the rule itself is broken.

Setting Up an AI Customer Service Agent in LiveAgent: Full Tutorial

LiveAgent’s AI Agent feature doesn’t sit inside one ticket at a time. It works whole departments, picking up unassigned tickets under a budget and dispatch mode you set. This tutorial covers the setup in the order that actually avoids the two mistakes that break it.

Published on Sep 21, 2026 by Adam Khaled.

AI Tutorial Automation Customer Support

Start your free trial Schedule a demo

Setting up an AI customer service agent in LiveAgent means creating a rule in **Configuration > AI > AI Dispatch Rules** that connects one or more departments to an AI agent, then setting an AI budget and a dispatch mode before saving it. The agent then automatically picks up unassigned tickets in those departments, working within the budget and dispatch mode you set, with no code required.

In this tutorial:

What Counts as an AI Customer Service Agent in LiveAgent?
Before You Start
Step 1: Open AI Dispatch Rules and Start a New Rule
Step 2: Pick the Departments
Step 3: Choose the AI Agent and Set the Budget
Step 4: Set the Dispatch Mode
Step 5: Save, Watch, and Adjust

Adoption of AI agents in customer service jumped from 39% of organizations in 2025 to 66% in 2026, according to Salesforce’s State of Service: AI Agents Edition , a survey of 3,075 service professionals published in May 2026. Most of that growth is happening inside the ticket queue, not the chat widget, which is where an AI agent for customer service like LiveAgent’s actually operates.

This guide covers that specific setup: connecting an AI agent to a department through a dispatch rule. It’s one of several AI tools for customer service built into LiveAgent, alongside the separate AI Chatbot, so this is a first-party walkthrough rather than an independent comparison.

What Counts as an AI Customer Service Agent in LiveAgent?

An AI customer service agent in LiveAgent works from the ticket queue, not the chat window. It’s a distinct feature from the AI Chatbot, and mixing the two up is the most common reason someone can’t find the setting they’re looking for.

The AI Chatbot sits on your website or in a chat widget. It answers a customer’s questions live, as they type, before a ticket even exists.

The AI Agent works after a ticket already exists. A dispatch rule assigns it to one or more departments, and it automatically picks up unassigned tickets there, the same way a human agent would pick up a ticket from the queue. No live chat session is involved.

This tutorial covers the AI Agent and its dispatch rules. If you’re looking to set up the chat-widget experience instead, LiveAgent’s AI Chatbot is the separate feature for that.

Before You Start

Have three things ready before creating a dispatch rule:

At least one department already set up in your account, with tickets actually flowing into it. A dispatch rule attached to an empty department won’t have anything to pick up.
An AI agent available in your account to assign. Create and name it first under Configuration > AI > AI Agents, where you also pick its provider and set which tools it’s allowed to call — it needs to exist there before it shows up as an option in the dispatch rule setup.
An AI budget you’re willing to allocate. Decide on a starting number before you begin. A modest budget you can raise later is easier to reason about than an open-ended one you have to rein in.

Step 1: Open AI Dispatch Rules and Start a New Rule

Go to Configuration > AI > AI Dispatch Rules, a dedicated screen separate from the general “AI Agents” and “AI Budgets” screens, and start a new rule from there.

A dispatch rule is the object that actually connects a department to an AI agent: one form covering the department, the AI agent, the AI budget, and the dispatch mode together. Nothing runs until this rule exists and is saved, so this is the step that turns “we have an AI agent available” into “an AI agent is actually working tickets.”

(LiveAgent also has an older, separate way to trigger an AI agent — a generic automation rule in Configuration > Automation > Rules using a “Run AI agent” action. That path still works, but it splits the department, agent, and budget across more screens and has no dispatch-mode equivalent, so this tutorial uses the dedicated AI Dispatch Rules screen instead.)

Step 2: Pick the Departments

Choose one or more departments for this rule to cover. A single rule can target several departments at once, so a support team split into “General Support” and “Billing” doesn’t need two separate rules if the same AI agent and budget should cover both.

Departments with no matching rule are unaffected. If you only create a rule for “Billing,” your “Sales” department keeps running exactly as it did before, with no AI agent involvement, handled by your human agents and any existing automation rules.

Start narrow. Pick the one department with the most repetitive, lowest-stakes ticket volume for your first rule, confirm it works the way you expect, then expand to other departments once you’ve seen a week or two of real results.

Step 3: Choose the AI Agent and Set the Budget

Assign which AI agent handles the work, and which AI budget its usage draws from. Every dispatch rule needs both.

The budget isn’t a suggestion. Usage from AI-handled tickets in that department draws directly from the credit pool you assign, so a rule can’t quietly run past what you’ve allocated to it. This is what makes cost predictable: you’re setting a ceiling per rule, not turning on an open-ended service.

If you’re running more than one dispatch rule, decide whether each one gets its own separate budget or shares one pool. Separate budgets make it easier to see exactly which department is driving AI usage; a shared pool is simpler to manage if you’re not worried about one department outspending another.

Step 4: Set the Dispatch Mode

Choose between two dispatch modes before saving the rule:

Dispatch mode	What it does	Fits best for
Once per ticket	The agent acts on each ticket a single time. Any follow-up from that customer goes to a human agent instead.	Simple, one-shot requests: order status, a document request, a password reset
Each time the ticket is queued	Re-runs the agent whenever the ticket re-enters the queue, for example after a customer reply.	Repetitive back-and-forth that doesn’t need human judgment calls, like basic troubleshooting steps

“Once per ticket” is the safer default for a first rule. It limits how much of any single conversation the AI agent handles, which makes it easier to review its replies and catch a bad pattern before it repeats across many tickets. Switch a department to “each time the ticket is queued” only after you’ve reviewed a batch of its “once per ticket” replies and trust the quality.

Step 5: Save, Watch, and Adjust

Save the rule, then check back within a day. Look for two things: tickets in the target department actually marked as handled by the AI agent, and the AI budget’s usage climbing against what you allocated.

If nothing shows up as AI-handled after a normal day of ticket volume, the department likely isn’t receiving unassigned tickets the rule can pick up, rather than the rule itself being broken. Check that tickets are actually landing in that department unassigned, not auto-assigned to a human agent by an existing rule that runs first.

If the AI agent is replying but the replies miss the mark on a specific ticket type, that’s a signal to either narrow the department the rule covers or switch that department back to “once per ticket” while you review more examples. You don’t need to delete anything to make either change: open the existing rule in AI Dispatch Rules and update its departments, agent, budget, or dispatch mode directly, then save it.

Getting the Order Right

The two mistakes that break this setup are the same ones every time: creating a dispatch rule for a department with no real unassigned-ticket flow, and picking “each time the ticket is queued” before you’ve reviewed enough “once per ticket” replies to trust the pattern. Both are easy to avoid by following the five steps above in order, starting with one narrow department.

Once a rule is running the way you expect, adding a second department or a second rule is the same five steps again, just faster the second time. This is what AI customer support actually looks like day to day: not a single dramatic launch, but one narrow rule proven out before the next one gets added. Start your free trial if you want to set up your first dispatch rule directly rather than reading about it.

Share this article

Frequently asked questions

: The AI Chatbot sits on your website or in a chat widget, answering questions as a customer types them in real time. An AI Agent works from inside your ticket queue: a dispatch rule assigns it to one or more departments, and it picks up unassigned tickets there the same way a human agent would, without a customer needing to start a live chat.
: No. The two features are independent. You can run an AI Agent on your ticket queue without ever enabling the AI Chatbot widget, and the reverse is also true. Most teams that use both set them up separately, since they solve different problems: the chatbot handles live conversations, the AI Agent handles queued tickets.
: Usage is billed against the AI budget you assign to the dispatch rule, not a flat monthly fee on top of your plan. You set the budget size when creating the rule, and usage from that department's AI-handled tickets draws from it, so cost stays predictable and capped.
: Yes. The dispatch mode setting on the rule controls this. 'Once per ticket' replies to a ticket a single time, then hands any follow-up from that customer to a human agent. 'Each time the ticket is queued' re-runs the agent whenever the ticket re-enters the queue, for example after a customer reply, which suits simpler, repetitive request types better than complex ones.
: Nothing changes. A department with no dispatch rule keeps working exactly as it did before: unassigned tickets wait for a human agent or your existing automation rules, unaffected by AI Agent features running elsewhere in the account. You can add a rule to that department later without touching any of the rules already running on other departments.
: Yes. A single dispatch rule can target several departments together, and you can also create separate rules pointing the same AI agent at different departments if you want different budgets or dispatch modes per department. Most teams start with one rule covering their highest-volume department, then split rules apart once each department needs its own budget or dispatch mode.
: Check the department's ticket list for tickets marked as handled by the AI agent, and watch the AI budget's usage against the amount you allocated. A rule that never shows AI-handled tickets after a day of normal ticket volume usually means the department has no unassigned tickets reaching it, not that the rule itself is broken.