Chatbot Use Cases: Examples by Industry and Function

Created by

Do not index

Created time

Sep 27, 2023 11:13 PM

Chatbot use cases are the specific jobs a chatbot does for a business, and the most common ones are answering customer questions, capturing and qualifying leads, booking appointments, tracking orders, screening job candidates, and answering employee questions from internal documents.

TL;DR

Almost every chatbot use case falls into six business functions: customer service, sales and marketing, ecommerce, scheduling, HR and recruiting, and IT or internal knowledge.

Industries reuse the same six jobs. A bank, a clinic, and a store all need question answering first. What changes is the content and the systems behind it.

Use cases sit on four levels: answer questions, capture and route, look up records, and take actions. Each level needs more integration and more safeguards.

Start with one high-volume question type the bot can resolve every time. In a 2026 Gartner survey, only 27% of customers would try a chatbot again after a bad experience.

Write each use case down before you build: user, trigger, goal, content needed, handoff rule, and one success metric.

Key takeaways

Business function	Top chatbot use cases	What the chatbot needs	Use-case level
Customer service	FAQs, policy questions, troubleshooting, handoff to a person	Help center and policy pages	1-2
Sales and marketing	Pre-sales answers, lead capture, demo booking	Product and pricing pages, a lead form	1-2
Ecommerce	Product questions, shipping and returns, order status	Product catalog, store integration for orders	1-3
Scheduling and bookings	Pre-booking questions, appointment and table booking	Service pages, a scheduling tool	1-3
HR and recruiting	Candidate questions, screening, employee policy answers	Careers pages, handbook, an applicant tracking system	1-3
IT and internal knowledge	How-to answers, ticket routing, access requests	Internal docs, a service desk	1-4

Summary graphic of chatbot use cases in six business functions: customer service, sales and marketing, ecommerce, scheduling and bookings, HR and recruiting, and IT and internal knowledge

What is a chatbot use case?

A chatbot use case is one defined job a chatbot does for one type of user, such as "answer return policy questions for shoppers" or "book a property tour for renters". A good use case names the user, the request, the outcome, and the point where a person takes over.

Use cases matter more than features. A chatbot with every feature still fails if it launches with jobs it cannot finish.

Gartner surveyed 3,566 B2B and B2C customers in February and March 2026. 49% said they would have used a chatbot if the company had offered one. Only 7% used a chatbot or digital assistant in their most recent service interaction. Gartner's advice was to start with issue types that have a proven high rate of successful resolution.

What are the 3 main use cases of a chatbot?

The 3 main use cases of a chatbot are answering questions, capturing leads, and handling simple transactions such as bookings or order lookups. Question answering is the most common starting point because it needs only content the business already has.

Answering questions: FAQs, policies, product details, and how-to steps.

Capturing leads: qualifying visitors, collecting contact details, and booking demos or calls.

Handling simple transactions: booking appointments, checking order status, or starting a return.

The four levels of chatbot use cases

Chatbot use cases fall into four levels, and each level needs more integration and more safeguards than the one before. The level decides which tool you need and how long setup takes.

Level	Example use cases	What it connects to	Main risk
1. Answer questions	Opening hours, return policy, pricing questions, product specs, how-to steps	Website, help center, documents	Out-of-date content gives wrong answers
2. Capture and route	Lead forms, demo requests, quote requests, handoff to a person	A form, email or chat inbox, CRM	Asking for details too early
3. Look up records	Order status, account balance, appointment details, claim status	Store, CRM, booking system, core system	Showing data to the wrong person
4. Take actions	Refunds, payments, cancellations, password resets	Systems that change money or accounts	An unapproved change that costs money

Most teams launch at level 1 or 2 and add level 3 once the answers are reliable. Level 4 needs identity checks, fixed rules, and a person for exceptions.

Chatbot use cases by business function

Chatbot use cases by business function describe the job the bot does, whatever the industry. The six functions below cover most deployments.

Customer service chatbot use cases

Customer service chatbot use cases are about answering and resolving customer questions without a wait. They are the most common reason businesses add a chatbot.

Answer FAQs and policy questions from the help center

Walk customers through troubleshooting steps

Collect details before a handoff, so the agent does not ask again

Hand the conversation to a person with the full transcript

Answer in the customer's language

Customer service has its own detailed breakdown of AI use cases, including triage, agent assist, and quality review, in customer service AI use cases. Real deployments are collected in support chatbot examples.

Sales and marketing chatbot use cases

Sales and marketing chatbot use cases turn website visitors into qualified leads. The bot answers the questions that come before a purchase, then asks for contact details once the visitor shows interest.

Answer pricing, feature, and comparison questions

Qualify leads by company size, budget, or use case

Show a lead form or booking link for a demo

Recommend the right plan or product

Re-engage returning visitors on high-intent pages

The playbook for sales chatbots, including the metrics to track, is in chatbots for sales and marketing. B2B patterns from companies such as Salesforce and Docker are in B2B chatbot examples.

Ecommerce chatbot use cases

Ecommerce chatbot use cases help shoppers choose a product and get answers after they buy. Product and policy questions need only content. Order lookups need a store integration.

Recommend products and compare variants

Answer sizing, shipping, and returns questions

Look up order status and tracking (needs a store integration)

Start a return or exchange (needs a store integration and rules)

Answer questions in the shopper's language

Store examples are in ecommerce chatbot examples, and the tool shortlist is in ecommerce chatbot solutions.

Scheduling and booking chatbot use cases

Scheduling chatbot use cases get a visitor from a question to a booked slot. The chatbot answers what people ask before they book, and a scheduling tool handles the calendar.

Answer service, price, and preparation questions

Share the booking link at the right moment

Collect contact details from visitors who do not book yet

Send urgent cases to a person

The step-by-step setup is in how to build an appointment booking chatbot.

HR and recruiting chatbot use cases

HR chatbot use cases answer the same questions candidates and employees ask every week. Recruiting bots answer job questions and screen applicants. Internal HR bots answer policy and benefits questions from the handbook.

Answer candidate questions about roles, pay bands, and the hiring process

Pre-screen candidates with a short form

Answer leave, benefits, and expense policy questions

Guide new hires through onboarding documents

A recruiting build is covered in how to build a recruitment chatbot. Hiring decisions stay with people and with the applicant tracking system.

IT and internal knowledge chatbot use cases

IT and internal knowledge chatbot use cases answer employee questions from internal documentation, often inside Slack or Microsoft Teams. They cut repeat questions to the IT and operations teams.

Answer how-to questions from internal docs and wikis

Route requests to the right queue in the service desk

Handle password resets and access requests (needs a service desk integration)

Answer developer questions from product documentation

The tool comparison is in IT support chatbots, and the Slack setup is in chatbot for Slack support.

Chatbot use cases by industry

Chatbot use cases by industry combine the six functions above with each sector's own content, systems, and rules. The table shows the common jobs and the main constraint in each industry.

Industry	Common chatbot use cases	Main constraint
Ecommerce and retail	Product questions, shipping and returns, order status, recommendations	Order data needs a store integration
Healthcare	Service and insurance questions, appointment booking, visit preparation, clinic hours	Patient data rules (HIPAA in the US)
Banking and finance	Product questions, fee and rate questions, account lookups, card controls	Identity checks and consumer protection rules
Insurance	Coverage questions, quote requests, claim status, document checklists	Coverage answers must match the policy wording
Education	Admissions, financial aid, course registration, campus services	Student data rules (GDPR in the EU, FERPA in the US)
Travel and hospitality	Booking questions, check-in details, itinerary changes, local information	Changes need the booking system
Real estate	Listing questions, tour booking, lead qualification	Fair housing rules in the US
SaaS and software	Product how-to, documentation answers, trial onboarding, pricing questions	Docs change with every release
Government and public sector	Program eligibility, form guidance, office locations, status checks	Plain language and accessibility
Restaurants and local services	Menu and allergen questions, reservations, opening hours	Menus and hours change often

Ecommerce and retail

Ecommerce and retail chatbots answer product, shipping, and returns questions, and look up orders when connected to the store. Most of the volume in a store is the same handful of questions about delivery times, sizing, and returns. A retail case is covered in AI chatbot for retail.

Healthcare

Healthcare chatbots answer service, insurance, and preparation questions, and send patients to booking. Symptom advice and diagnosis belong with clinicians, so most practices keep the bot on administrative questions.

Patient data changes the tool choice. For SiteGPT, a HIPAA Business Associate Agreement is available on the Enterprise plan only, and chatbot training content must stay free of protected health information (SiteGPT HIPAA program). The requirements are covered in HIPAA compliant AI chatbots and on the healthcare chatbot page.

Banking and finance

Banking chatbots answer product and fee questions, and authenticated bots look up balances and transactions. The US Consumer Financial Protection Bureau reported that all of the top 10 US commercial banks use chatbots. It estimated that about 37% of the US population interacted with a bank's chatbot in 2022.

The same report warned about "doom loops", where customers cannot reach a person. Finance teams should keep a visible route to an agent. More detail is on the financial services chatbot page.

Insurance

Insurance chatbots answer coverage questions, collect quote details, and report claim status. Coverage answers should quote the policy documents directly, and claim decisions stay with adjusters.

Education

Education chatbots answer admissions, financial aid, and registration questions, often at the busiest points of the academic year. Student data rules apply, and the education chatbot page covers them.

Travel and hospitality

Travel and hospitality chatbots answer booking, check-in, and local questions in many languages. Changing a booking needs a connection to the reservation system, so many teams start with questions only.

Real estate

Real estate chatbots answer listing questions, qualify buyers and renters, and book tours. They work outside office hours, when many people browse listings.

SaaS and software

SaaS chatbots answer product how-to and documentation questions, and help trial users get started. Documentation changes with every release, so the bot needs a regular content refresh. The setup for docs is in AI chatbot for documentation.

Government and public sector

Government chatbots answer eligibility and form questions in plain language. They also point people to the right office or form. Public-sector bots need accessible widgets and answers that match the official guidance word for word.

Use cases for complex conversations with chatbots

Use cases for complex conversations are requests that take several turns, depend on conditions, or need personal records to answer. A chatbot can handle many of them when it has the right content and a clear point to hand off.

Complex use case	What makes it complex	How to handle it
Multi-step troubleshooting	Each answer depends on the last step the user tried	Train on step-by-step guides and hand off after two failed steps
Eligibility and coverage questions	The answer depends on conditions such as plan, location, or date	Ask the qualifying questions first, then quote the source document
Guided product selection	The visitor does not know which product fits	Ask 2-3 questions about needs and budget, then recommend with reasons
Changes to an existing booking or order	Needs the record and the rules for what can change	Connect the booking or order system, or hand off with the details collected
Billing disputes and complaints	Money and emotion are involved	Collect the facts and hand off to a person every time

The rule for complex conversations is to keep context across turns and never make the visitor repeat details. When the bot hands off, the agent should receive the full transcript. Grounding answers in your own content, a method called retrieval-augmented generation, keeps multi-turn answers tied to source pages.

How to write a chatbot use case

To write a chatbot use case, describe one job in seven fields: the user, the trigger, the goal, the content or system needed, the happy path, the handoff rule, and the success metric. Writing it down before you build shows whether the job is level 1 or level 3, and what content is missing.

Field	What to write	Example: return policy questions for an online clothing store
User	Who asks	A shopper with a recent order
Trigger	What they type or click	"Can I return this?" or "How do returns work?"
Goal	The outcome that counts as done	The shopper knows the deadline, condition rules, and how to start a return
Content or system needed	Pages, documents, or integrations	Returns policy page, shipping FAQ, returns portal link
Happy path	The ideal conversation in 2-4 turns	Bot states the 30-day window, lists conditions, links the portal
Handoff rule	When a person takes over	Damaged item, order older than 30 days, or the shopper asks for a person
Success metric	One number to track weekly	Share of return questions resolved without a ticket

Worked example: sizing the return-questions use case

This example uses illustrative numbers for a hypothetical store. It shows how a written use case turns into a launch decision.

The store receives 1,000 service emails a month. 30% of them are return questions, which is 300 emails.

In a 20-question pre-launch test, the bot answers 17 return questions correctly. That is an 85% pass rate.

At 85%, about 255 of the 300 monthly return questions could be resolved in chat. The other 45 go to a person with the transcript.

The team fixes the three failed answers by adding a missing page on exchanges, reruns the test, and launches.

The full testing method is in chatbot best practices. Ready-made prompts and flows are in chatbot templates.

How to choose your first chatbot use case

Choose your first chatbot use case by picking the highest-volume question type the bot can resolve every time with content you already have. Widen the scope only after that use case holds up.

If you need...	Pick this use case first	Why
Fewer repeat emails and calls	FAQ and policy answers	Level 1, uses pages you already have, launches fastest
More qualified leads from the website	Pre-sales answers plus a lead form	Visitors get answers before they are asked for details
Fewer "where is my order" tickets	Order status lookup	Level 3, needs a store or helpdesk integration
More booked appointments	Pre-booking answers plus a booking link	The scheduling tool books, the chatbot removes the doubts first
Fewer internal HR or IT questions	Internal knowledge chatbot in Slack	Employees ask where they already work
Refunds or cancellations handled automatically	Start with the questions, add actions later	Level 4 needs rules, identity checks, and a person for exceptions

Decision tree for choosing a first chatbot use case: repeat questions, lost leads, order or account requests, and internal employee questions

Which tool fits which chatbot use case?

The right tool depends on the use-case level. Content-trained chatbots cover levels 1 and 2. Helpdesk, store, and service-desk platforms cover levels 3 and 4 because they hold the records.

Use case	Tool type	Examples
Answers from your website, help center, and documents	Content-trained chatbot	SiteGPT, Chatbase
Ticket handling inside a helpdesk	Helpdesk AI agent	Zendesk AI agents, Fin
Order lookups and returns in an online store	Ecommerce helpdesk with AI	Gorgias (see ecommerce chatbot solutions)
Scripted flows, quizzes, and fixed forms	Visual flow builder	Botpress, Landbot (see Landbot alternatives)
Password resets and access requests	IT service desk with AI	Moveworks, Jira Service Management (see IT support chatbots)
Candidate screening at volume	Recruiting automation	Paradox, Workable (see recruitment chatbot)

Many teams combine two layers. A content-trained chatbot answers the questions, and the helpdesk or store platform handles records and actions. A wider list of platforms is in customer service AI chatbot platforms.

Where SiteGPT fits

SiteGPT covers the level 1 and level 2 use cases: answers from your own content, lead capture, and handoff to a person. It trains on websites, sitemaps, files, Google Drive, Dropbox, OneDrive, Box, Notion, GitHub, and YouTube. It answers in 95+ languages, and human support with escalation is available on every plan.

SiteGPT has real limits. It does not look up orders or take actions in a store, has no visual flow builder, and has no Intercom or HubSpot integration today. Chat integrations such as Slack, Messenger, and Crisp start on Growth, and the Zendesk AI agent starts on Scale.

SiteGPT plan	Billed monthly	Billed yearly	Messages per month
Starter	$59 a month	$39 a month ($468 a year)	Up to 4,000 GPT-4.1-mini or 400 GPT-4.1
Growth	$129 a month	$79 a month ($948 a year)	Up to 10,000 GPT-4.1-mini or 1,000 GPT-4.1
Scale	$429 a month	$259 a month ($3,108 a year)	Up to 40,000 GPT-4.1-mini or 4,000 GPT-4.1

Paying yearly saves $240 a year on Starter ($708 monthly versus $468), $600 on Growth, and $2,040 on Scale. Every self-serve plan starts with a 7-day free trial, and a credit card is required.

Try SiteGPT free for 7 days

Common mistakes when choosing chatbot use cases

The most common mistake is launching with too many use cases at once. Gartner found that only 27% of customers would try a chatbot again after a negative experience, so early failures are expensive.

Starting at level 4. Refunds and payments need integrations and rules. Start with the questions around them.

Hiding the route to a person. Gartner found 87% of customers say access to a human agent is essential when companies use GenAI in service.

Skipping the written use case. Without a goal and a metric, nobody can tell whether the bot works.

Letting content go stale. A bot trained on last year's pricing page gives last year's prices.

Forgetting disclosure. In the EU, Article 50 of the AI Act has applied since 2 August 2026. People must be told they are interacting with an AI system unless that is obvious.

For the difference between a chatbot and an AI agent that takes actions, see AI agent vs chatbot.

Frequently asked questions

Basics

What are the most common chatbot use cases?

The most common chatbot use cases are answering FAQs and policy questions, capturing and qualifying leads, booking appointments, tracking orders, and answering employee questions from internal documents.

What are chatbots used for in business?

Businesses use chatbots to answer customer questions at any hour, qualify website visitors, book appointments, and cut repeat questions to service, HR, and IT teams.

What is an example of a chatbot use case?

An example of a chatbot use case is an online store's bot that answers return policy questions. It states the return window, lists the conditions, links the returns portal, and hands damaged-item cases to a person.

Industries

Which industries use chatbots the most?

Ecommerce, banking, healthcare, education, travel, and software companies use chatbots widely. The CFPB reported that all of the top 10 US commercial banks use chatbots.

Can a chatbot be used in healthcare?

Yes. Healthcare chatbots usually handle administrative work such as service questions, insurance questions, and appointment booking. Patient data rules apply, and in the US a vendor that handles protected health information needs a Business Associate Agreement.

What are enterprise chatbot use cases?

Enterprise chatbot use cases include customer service at scale, internal IT and HR knowledge, sales qualification, and documentation answers for developers. Enterprises add identity checks, audit trails, and signed data agreements.

Planning and writing use cases

How do you write a use case for a chatbot?

Write a chatbot use case in seven fields: user, trigger, goal, content or system needed, happy path, handoff rule, and success metric. Keep each use case to one job.

How many use cases should a chatbot launch with?

A chatbot should launch with only the use cases it can resolve reliably, often one or two. Gartner's 2026 advice is to expand scope only after performance is reliable.

Can chatbots handle complex conversations?

Chatbots can handle many complex conversations, such as troubleshooting and eligibility questions, when they keep context across turns and answer from source documents. Billing disputes and complaints should go to a person.

Tools and cost

Do you need coding to build a chatbot for these use cases?

No coding is needed for level 1 and level 2 use cases. A content-trained chatbot learns from your website and documents. Level 3 and 4 use cases need integrations, which may need developer time.

How much does a chatbot cost?

A content-trained chatbot such as SiteGPT starts at $59 a month billed monthly, or $39 a month billed yearly. Helpdesk and enterprise platforms often price per agent or per resolution. The full breakdown is in chatbot cost.

Sources

Checked on 18 October 2026.

Gartner: Only 27% of Customers Would Try a Chatbot Again After a Negative Experience (September 2, 2026)

CFPB: Chatbots in consumer finance (June 2023)

European Commission: Transparency obligations under Article 50 of the AI Act

SiteGPT pricing

SiteGPT integrations

SiteGPT docs: Let visitors talk to your team

SiteGPT: HIPAA at SiteGPT

Chatbot Use Cases by Industry and Business Function