---
title: 13 AI Chatbot Examples for SaaS and Online Stores
canonical: "https://www.thrivedesk.com/blog/ai-chatbot-examples/"
author: ThriveDesk
description: "See 13 AI chatbot examples for SaaS teams and online stores: real support jobs with sample chats, what each bot needs, and what to measure."
categories: [blog, customer-support]
---

# 13 AI Chatbot Examples for SaaS and Online Stores, With Sample Chats

See 13 AI chatbot examples for SaaS teams and online stores: real support jobs with sample chats, what each bot needs, and what to measure.

 [Parvez Akther](https://www.thrivedesk.com/author/parvez/) 15 min read Updated November 18, 2026

![Line drawing of a speech bubble with one part enlarged in a magnifying circle](https://www.thrivedesk.com/_astro/ai-chatbot-examples.DiJIS_KN_BfLQ3.webp)

TL;DR

-   An AI chatbot answers customer questions in chat from your own help content, orders and rules.
-   The best AI chatbot examples are narrow support jobs: password reset, failed payment, order status, returns, sizing and after-hours lead capture.
-   Each example needs up to four inputs: a help article or page, short Q&A answers, a lookup action when the answer depends on customer data, and a handoff rule.
-   A scripted button bot follows menus. An AI agent reads free text and answers from your content. Pick the one that handles what your customers really type.
-   Check a chatbot product for a start date, a dated changelog, live integrations and a handoff that attaches the chat.
-   In ThriveDesk, you build every example here with sources, guidance, actions and handoff rules, then test in Preview & Simulations before you go live.

A chatbot is only as good as the page behind each answer. Fix the article first, then blame the bot.  Parvez Akther ThriveDesk

An AI chatbot is software that reads a customer’s message and answers in plain words, using your [help articles](https://www.thrivedesk.com/features/help-center/), policies and customer data. This post shows 13 AI chatbot examples, and each one is a real support job. The chats are written samples, not logs from a live store.

Five examples suit [software teams](https://www.thrivedesk.com/industry/saas/), five suit [online stores](https://www.thrivedesk.com/industry/ecommerce/), and three suit both. Each has a sample chat, the inputs the bot needs and one thing to measure. The bot takes the repeat questions, such as password resets, order status, return rules and sizing. Your team keeps refunds, bugs and upset customers.

## What an AI chatbot is, and what it is not

A chatbot is a program that talks with customers in a chat window. Two kinds exist.

A scripted bot offers buttons and keywords on a fixed path. It works well for one narrow job that never changes, such as sending a tracking link. It fails when the customer types something the script does not hold.

An AI chatbot reads free text. It finds the article or policy that holds the answer and writes a reply from it. If you also let it act, for example look up an order, it is an AI agent. Most examples below need that step.

A chatbot is not the same as [live chat](https://www.thrivedesk.com/live-chat-support/). Live chat is the channel, the chat window, and a person, a scripted bot or an AI agent can answer inside it. For the longer comparison, read [chatbots vs live chat](https://www.thrivedesk.com/chatbots-vs-livechat/).

![Hand-drawn line that starts as stiff steps and turns into a smooth curve ending in a speech bubble](https://www.thrivedesk.com/_astro/script-vs-conversation.CdFV3G6w_2uSLQ9.webp)

## AI chatbot examples for SaaS and software teams

Software teams get the same few questions all day: login, billing, how-to and bugs. These five examples cover most of them.

### 1. Password reset and account lockout

A customer who reset a password and still can’t log in is the most common software chat. The bot needs a help article on login and lockouts, and a guidance rule to never ask for a password. A handoff rule sends single sign-on and admin lockouts to a person, because someone must check those. Watch the chats resolved without a person, and the chats that reopen within a day.

### 2. Failed payment or plan change

A failed card is a billing question with a quick answer. The bot needs a connection to the app that holds your purchases, such as Stripe, Paddle or Freemius, and an action that looks up a purchase. Guidance says a teammate confirms refunds and plan changes. Watch for answers that name the wrong plan or price, and read a sample each week.

Example 1

Acme support

Today 9:41 AM

Customer: I reset my password but I still can't log in.

AI agent: I can help. Is the account under this email address?

Customer: Yes.

AI agent: Too many failed tries lock the account for 30 minutes. Wait, then use the newest reset link.

AI agent: If it still fails, I will pass this to a teammate.

Example 2

Acme support

Today 11:05 AM

Customer: My card failed. Did I lose access?

AI agent: Your account is still active. The last payment did not go through.

AI agent: You can update the card in Billing. The next retry runs in a few days.

Customer: Can I get a refund for last month?

AI agent: A teammate will confirm that. I passed them this chat.

### 3. Onboarding how-to

New users ask how to do the first tasks, and a short answer with the right article keeps them going. The bot needs one help center article for each setup step. Training on your [knowledge base](https://www.thrivedesk.com/blog/ai-knowledge-base/) is the base of every example in this post. Watch the questions the bot could not answer in a new user’s first week, because each one is a missing article.

Example 3

Acme support

Today 10:02 AM

Customer: How do I invite my team?

AI agent: Open Settings, then Team, and select Invite. Type each email address and pick a role.

AI agent: Here is the article with screenshots: Invite your team.

### 4. Bug report triage with handoff

A bug chat needs details before a person can act, so the bot collects them first. Guidance tells it to ask for browser, steps and account email. A handoff rule assigns the chat to a teammate, adds a tag and sets a priority, and the chat becomes a [ticket](https://www.thrivedesk.com/trouble-ticket-software/) with everything attached. The bot never promises a fix date. Watch the time to the first human reply on bug chats.

Example 4

Acme support

Today 3:20 PM

Customer: The export button does nothing.

AI agent: Sorry about that. Which browser are you using?

Customer: Chrome.

AI agent: What did you click, and did an error show?

Customer: Export, then nothing. No error.

AI agent: Thanks. I sent the details to the team. A person will reply here.

### 5. Cancellation and save

When a customer writes “I want to cancel my plan”, the bot asks why, offers the options you list and passes the final step to a person. Guidance lists those options, such as a cheaper plan, and a handoff rule on the word “cancel” lets a teammate finish the request. The cancel path stays one message away. For more on this job, see [churn prevention software](https://www.thrivedesk.com/best-churn-prevention-software/). Watch your own save rate: count the chats that ended with a plan change and compare it month to month.

Example 5

Acme support

Today 4:12 PM

Customer: I want to cancel my plan.

AI agent: I can pass that on. May I ask why you are leaving?

Customer: Too expensive for how often I use it.

AI agent: We have a cheaper plan with fewer seats. Want details, or should I hand you to a teammate to cancel?

## AI chatbot examples for ecommerce and retail

Stores get order, delivery and return questions, and the volume jumps during a sale. A retail chatbot takes the repeat ones. For more tactics, see these [ecommerce customer service best practices](https://www.thrivedesk.com/ecommerce-customer-service-best-practices/).

### 6. Order status and delivery

“Where is my order?” is the top question in most stores. The bot needs a [Shopify](https://www.thrivedesk.com/integrations/shopify/) or [WooCommerce](https://www.thrivedesk.com/integrations/woocommerce/) connection and an action that looks up an order, plus a handoff rule for lost parcels. Watch how often the order lookup fails to find the order number.

### 7. Returns and exchanges

A shopper who asks how to return boots wants the steps and a quick choice between a refund and another size. The bot needs your returns policy as an article or page. Guidance says never to promise a refund date, and a handoff rule sends refund and exchange requests to a person. Watch the handoffs by reason: a spike on one reason points to a gap in the policy page.

Example 6

Boot Co. support

Today 2:14 AM

Customer: Where is my order?

AI agent: I can check. What is your order number?

Customer: #10482

AI agent: It shipped yesterday and is with the carrier. Here is the tracking link.

AI agent: If the tracking stops moving for several days, write back and a teammate will look.

Example 7

Boot Co. support

Today 10:30 AM

Customer: How do I return these boots?

AI agent: You can return unworn items within the return window on our returns page.

AI agent: I can send the steps. Do you want a refund or a different size?

Customer: Different size.

AI agent: A teammate will set up the exchange. I passed them this chat.

### 8. Product and sizing questions

Shoppers ask “Do these run small?” before they buy. The bot reads your product pages as a Website source, and a size guide as a file or an article. It answers from what the page says. If the page is silent, it says so and offers a person. Watch the questions it could not answer. Add each answer to the product page, and every shopper benefits.

Example 8

Boot Co. support

Today 7:50 PM

Customer: Do these run small?

AI agent: The size guide says this boot fits true to size. Half sizes are not made.

Customer: I'm a 9.5. What should I order?

AI agent: The guide suggests size 10 for a half size. I can't see how it fits your foot, so a teammate can help if you want a second opinion.

### 9. Stock and back-in-stock

A bot that reads pages cannot see live stock, so it must say that and not guess a date. The bot needs a policy article on restocks and preorders. A handoff rule on restock questions passes the chat to a teammate, who can take the email address and follow up. Watch how often shoppers ask about the same product, because that list tells you what to restock.

### 10. Shipping cost and delivery time

Shipping questions peak before a holiday. The bot needs a shipping page, or one Q&A item for each country, with exact numbers and no long policy text. Watch the chats in the days before a sale, because they show where your shipping page is unclear.

Example 9

Boot Co. support

Today 1:20 PM

Customer: When will the black pair be back?

AI agent: I can't see live stock, and I don't want to guess a date.

AI agent: Leave your email and a teammate will follow up.

Customer: ana@example.com

AI agent: Thanks. I passed it to the team.

Example 10

Boot Co. support

Today 1:26 PM

Customer: How much is shipping to Canada, and how long does it take?

AI agent: Standard shipping to Canada takes 7 to 12 business days. The cost shows at checkout.

AI agent: Orders over the free shipping limit ship free. The shipping page has the exact amount.

## AI chatbot examples that work for both

Three jobs suit any business. Each one touches the sale or a handoff, so the guidance must be exact: say when to suggest a plan, what to promise after hours and when a person takes over.

### 11. Pre-sale questions and upsell

“Which plan fits a team of four?” and “Is this jacket warm enough for winter?” are the same job. The bot needs plan or product pages, and guidance that says when to suggest a better fit, for example “If the customer’s team is larger than the plan allows, name the next plan.” It answers the question first, then names the better fit. Track pre-sale chats that end in a purchase from your own store or billing data.

Example 11

Acme support

Today 12:15 PM

Customer: Which plan fits a team of four?

AI agent: The Team plan has five seats. The Starter plan has two.

AI agent: Want me to link the plans page, or pass you to a teammate for a custom quote?

### 12. After-hours lead capture

A question at 3 a.m. gets an honest answer: the team is offline, and here is how to reach it. The bot needs the setting that asks for an email and opens a ticket when no one is online, plus your business hours. Watch how many after-hours chats become tickets, and how fast the team replies the next morning.

Example 12

Acme support

Today 3:02 AM

Customer: Do you offer a plan for agencies?

AI agent: We do not have that detail in my notes, and nobody is online now.

AI agent: Leave your email and a teammate will reply in the morning.

Customer: sam@example.com

AI agent: Thanks. I opened a ticket for the team.

### 13. Hand off to a person

Every bot needs this one. A customer who has asked three times wants a person, and the bot must pass the chat without a fight. Set handoff rules for a request for a person, for keywords such as refund, for low confidence and for upset customers. The person in your [help desk](https://www.thrivedesk.com/blog/help-desk-software/) sees the full chat. Watch the handoffs by reason, and how long customers wait after a handoff.

Example 13

Acme support

Today 1:48 PM

Customer: This is the third time I am asking. I want a person.

AI agent: I am sorry about that. I am passing this chat to a teammate now.

AI agent: They can see everything we said, so you do not need to repeat it.

## Which inputs each example needs

![Hand-drawn square hub joined by four lines to four dots](https://www.thrivedesk.com/_astro/four-inputs.BBkqmI3__Z1fTnAp.webp)

Every example uses the same four building blocks. This table shows which ones each job needs, so you can plan your content before you set anything up.

| Example | Help article or page | Q&A | Lookup action | Handoff rule |
| --- | --- | --- | --- | --- |
| 1\. Password reset | Login article | Yes | No | SSO and admin lockouts |
| 2\. Failed payment | Billing article | Yes | Purchase lookup | Refunds and plan changes |
| 3\. Onboarding how-to | One article per step | Yes | No | Low confidence |
| 4\. Bug triage | Known issues article | No | No | Every bug report |
| 5\. Cancellation | Plan options | Yes | Purchase lookup | The word cancel |
| 6\. Order status | Delivery article | Yes | Order lookup | Lost parcels |
| 7\. Returns | Returns policy | Yes | Order lookup | Refunds and exchanges |
| 8\. Sizing | Product pages, size guide | Yes | No | Unanswered questions |
| 9\. Stock | Restock policy | Yes | No | Restock dates |
| 10\. Shipping cost | Shipping page | Yes | No | Unusual destinations |
| 11\. Pre-sale and upsell | Plan or product pages | Yes | No | Large or custom deals |
| 12\. After-hours capture | Business hours | No | No | No one online |
| 13\. Handoff | None | No | No | Asks for a person, upset |

Start with the examples that have no lookup action, because they need only content. Add order or purchase lookups once the first ones work.

## What to measure across all examples

Each example has its own metric. Four numbers work for the whole bot.

1.  First reply time: the minutes from the first message to the first answer.
2.  Resolved without a person: chats where the bot answered and the customer did not write again or reach your team.
3.  Handoff rate: the share of chats passed to a person. Log the reason for each one.
4.  Top topics: the questions customers ask most. Feed that list back into your help center.

Review them every week for the first month, then every month. Sales and releases change the questions, so review after each one.

## What separates a good AI chatbot from a bad one

Take one question, “Where is my order?”, and give it to two bots.

Scripted button bot

Boot Co. bot

Today 2:14 PM

Customer: Where is my order?

Bot: Choose an option: 1. Orders 2. Returns 3. Other

Customer: Orders

Bot: Choose an option: 1. New order 2. Existing order 3. Other

Customer: Existing order

Bot: I did not understand. Please contact support.

AI agent

Boot Co. support

Today 2:14 PM

Customer: Where is my order?

AI agent: I can check. What is your order number?

Customer: #10482

AI agent: It shipped yesterday and is with the carrier. Here is the tracking link.

AI agent: Want me to pass this to a teammate?

The first bot loops through menus and ends in a dead end. The second one reads the question, looks up the order and offers a person. A button bot still does one fixed job well, such as sending a tracking link or a reset link, but the problem starts when it must handle free text. Check any bot against these five points:

-   It answers from your own content only.
-   It says so when it is not sure.
-   It can look up the customer’s data when the question needs it.
-   It hands off with the chat attached.
-   You can test it before customers see it.

If you want to compare products, see the [best AI chatbots for customer service](https://www.thrivedesk.com/blog/best-ai-chatbots-for-customer-service/) and how [AI chatbots are changing help desks](https://www.thrivedesk.com/how-ai-chatbots-are-redefining-help-desks/).

## How to choose an AI chatbot product in the agentic AI era

![Hand-drawn balance scale with a speech bubble on one pan and a checklist on the other](https://www.thrivedesk.com/_astro/weigh-the-product.B0lV95N-_Z1htrou.webp)

Agentic AI means software that does tasks, not only answers. Salesforce says service teams estimate that AI handles 30% of cases today. Gartner projects how much agentic AI will resolve by 2029. The 30% is a service teams’ estimate. The 50% and the 80% are projections. The 64% is a customer survey.

Share of service cases handled by AI: today and projected for 2027

Share of service cases handled by AI: today and projected for 2027
| Item | Share of cases |
| --- | --- |
| Handled by AI today (estimate) | 30% |
| Handled by AI in 2027 (projection) | 50% |

Source: Salesforce, State of Service report announcement, November 2025 (service teams' estimate and projection)

64%

of customers would prefer that companies did not use AI for customer service (survey)

Gartner customer survey, July 2024

80%

of common service issues resolved by agentic AI without a person by 2029, with 30% lower operational cost (prediction)

Gartner press release, March 2025

Customers are wary of AI service, and Gartner expects agentic AI to resolve most common issues by 2029. A product must prove it works before you rely on it.

Vibe-coded software is an app built fast with AI coding tools and shipped with little engineering, testing or security review. It can look fine in a demo. Test how it behaves on your busiest day, where it stores chat data and whether you can keep your history if you leave.

Check these signs before you buy:

-   A start date you can verify, and a dated changelog.
-   A public status page with past incidents.
-   Integrations that work, such as Shopify, WooCommerce and Stripe.
-   A handoff that attaches the full chat.
-   A way to test before launch.
-   A support team that answers.

ThriveDesk is not vibe-coded. You can check the facts. It has run for more than five years, and the dated changelog goes back to 2021. Its Shopify, WooCommerce, Stripe, Paddle and Freemius integrations are live in the App Store. For large support loads, the shared inbox has assignment, tags and priorities, and a handoff passes the full chat to a teammate. See the [pricing page](https://www.thrivedesk.com/pricing/), or read how [AI training](https://www.thrivedesk.com/ai/training/) and [escalation to people](https://www.thrivedesk.com/ai/escalation/) work.

## How to build these AI chatbot examples with ThriveDesk

This tutorial builds the examples above in ThriveDesk. You need an account and a few help articles. The AI agent is called Neo, and the app labels use that name. For background, read [conversational customer service](https://www.thrivedesk.com/blog/conversational-customer-service/).

### Step 1: create the inbox and the chat widget

1.  Open **Settings**, then **Inboxes**. Skip to item 4 if you already have an inbox.
2.  Select **New inbox**.
3.  Type an **Inbox name**, such as “Support”.
4.  Open **Neo** in the left rail.
5.  Under **Deploy**, select the **+** next to **Chat widget**.
6.  Type an **Assistant name**.
7.  Select your inbox in **Select Inbox**.

![The Neo menu in ThriveDesk with Train, Guidance, Actions and Handoff & Escalation, and Chat widget with a plus button under Deploy](https://www.thrivedesk.com/_astro/neo-chat-widget.Id_KLMpD_Z26y5I8.webp)

### Step 2: connect your store or billing app

1.  Open **App Store** in the left sidebar.
2.  For a store, install [Shopify](https://www.thrivedesk.com/integrations/shopify/) or [WooCommerce](https://www.thrivedesk.com/integrations/woocommerce/). WooCommerce also needs the ThriveDesk plugin.
3.  For a software company, install the app that holds your purchases, such as Stripe, Paddle or Freemius.
4.  Select the inboxes for the app.

This serves examples 2, 5, 6 and 7.

![The ThriveDesk App Store searched for Shopify, showing the Shopify card with a Set up button](https://www.thrivedesk.com/_astro/connect-store.B5CWn-dd_Z1GggPP.webp)

### Step 3: add the sources

1.  Open **Neo** in the left rail.
2.  Open **Doc**. Your help center docs are listed under **Sources**.
3.  Select **Create doc** if an article is missing, and type the article.
4.  Open **Website**.
5.  Select **Add website**.
6.  Type your domain, such as “example.com”.
7.  Select the product, shipping and plan pages to add.
8.  Open **File**.
9.  Select **Upload Files**.
10.  Pick a size guide or a policy file. The upload takes PDF, Word, Excel and text files, up to 10 files and 50 MB at a time.
11.  Open **Q&A**.
12.  Select **Add Q&A**.
13.  Type one top question and its answer. Repeat for your top ten, the way you write [saved replies](https://www.thrivedesk.com/canned-reply-guide/).

Test: open **Preview & Simulations** and type “How do I reset my password?”. The reply should name the right article. If it does not, fix the source.

![The Neo Q&A page with a question and answer filled in and an Add button](https://www.thrivedesk.com/_astro/add-qna.C_C9_ETU_ZNJcQC.webp)

### Step 4: write the guidance

1.  Open **Guidance**.
2.  In **Voice and tone**, select a **Tone**, such as **Friendly** or **Professional**.
3.  In **Answer length**, select **Concise** for chat.
4.  Select the **Brand summary** box.
5.  Type this rule on its own line: “Never promise a refund date.”
6.  Type this rule: “Never ask for a card number or a password.”
7.  Type this rule: “For refund and plan change questions, say a teammate will confirm.”
8.  Type this rule: “For bug reports, ask for browser, steps and account email.”
9.  Select **Save**.

Test: type “When will I get my refund?” in **Preview & Simulations**. The reply should give no date and say a teammate will confirm. If it gives a date, make the rule more direct.

![The Neo Guidance page with the brand summary, the voice and tone options and a Save button](https://www.thrivedesk.com/_astro/guidance.CL902tNP_OsIcH.webp)

### Step 5: turn on actions

1.  Open **Actions**.
2.  Select **Add action**.
3.  Select the app you connected in step 2.
4.  Select the action that looks up an order or a purchase.
5.  Leave other actions off until you trust the agent.

Test: type “Where is my order?” in **Preview & Simulations**. The agent should ask for an order number and look it up. If it does not, check the app connection.

![The Neo Actions page listing order lookup, refund and other actions, each with an on and off switch](https://www.thrivedesk.com/_astro/actions._3am3mn6_Z2gWdzs.webp)

### Step 6: set handoff rules and business hours

1.  Open **Handoff & Escalation**.
2.  Type the **Handoff message**.
3.  Turn on **When no one is online, ask for an email and open a ticket**.
4.  Select **Add rule**.
5.  Type a **Name**, such as “Refunds”.
6.  In **Trigger**, select **A message mentions keywords**.
7.  In **Keywords**, type “refund, chargeback, cancel subscription”.
8.  In **Assign to**, select a teammate.
9.  Select **Save**.
10.  Select **Add rule** again.
11.  In **Trigger**, select **The customer asks for a person**.
12.  In **Assign to**, select a teammate, then **Save**.
13.  Open **Settings**, then **Business Hours**.
14.  Select **Add business hours** and set the schedule.

Test: send a message with “refund” in **Preview & Simulations**. Check that the handoff rule applies. If not, check the keywords. For example 9, add a rule with the keywords “back in stock, restock”.

![The Handoff & Escalation page with the handoff message, the switch to ask for an email when no one is online, and a list of handoff rules](https://www.thrivedesk.com/_astro/handoff.C7LsBQdS_SG84M.webp)

### Step 7: test, then go live

1.  Open **Preview & Simulations**.
2.  Type the customer lines from the examples above.
3.  Select **Improve Answer** on a wrong reply.
4.  Edit the source article, or add a Q&A item for that question.
5.  Under **Deploy**, open **Chat widget**.
6.  Open your widget.
7.  Select the **NEO** tab.
8.  Turn on **Enable NEO**.

Place the widget on product, cart and order pages for a store. For a software product, use the pricing page and the app. After one week, open **Agent Activity** and add an article for every gap.

![The Preview & Simulations page with a Live Chat tab, the instructions editor and a Message Neo box](https://www.thrivedesk.com/_astro/preview-simulations.CkgYWU8U_Z1xlDdo.webp)

![The NEO tab of the chat widget settings with the Enable NEO switch](https://www.thrivedesk.com/_astro/enable-neo.DvzjjGhN_ZnaLwA.webp)

## Frequently asked questions

### What are some AI chatbot examples for customer support?

Common examples are password reset, failed payment help, onboarding how-to answers, bug report triage, order status, returns and exchanges, sizing questions, shipping costs, pre-sale questions, after-hours lead capture and handoff to a person. This post shows 13 of them, each with a sample chat, what the bot needs and what to measure.

### What is the difference between a chatbot and an AI chatbot?

A basic chatbot follows a script of buttons and keywords. It fails when the customer types something the script does not cover. An AI chatbot reads free text and answers from your own content, such as help articles and policies. An AI agent can also act, for example look up an order, and hand off to a person.

### Can an AI chatbot work for both a SaaS company and an online store?

Yes. The engine is the same. The content and the actions differ. A SaaS team trains it on help articles and connects a billing app so it can check a plan. A store trains it on shipping and returns pages and connects Shopify or WooCommerce so it can check an order. Both need a handoff rule.

### What do I need before I add an AI chatbot to my website?

You need four things. First, clear help center articles and policy pages. Second, short Q&A answers for your top ten questions. Third, a connection to your store or billing app if the bot should look up data. Fourth, handoff rules and a test run. Write the content first, because the bot can only be as clear as your pages.

### How do I stop an AI chatbot from giving a wrong answer?

Limit it to your own content, add guidance rules such as never promise a refund date, and test it with real customer messages before launch. When a reply is wrong, fix the article or Q&A it came from. Add a handoff rule for low confidence and for words like refund or cancel, so a person takes those chats.

### How much does an AI chatbot cost for a small team?

Prices vary by product. ThriveDesk plans start at $29 a month for 2 teammates, or $19 a month on annual billing. Standard is $69 for 5 teammates and Unlimited is $129. The AI agent and live chat come with every plan. The built-in help center starts on Standard. There is a 7-day free trial with no credit card.

### Should an AI chatbot hand off to a person?

Yes. A bot cannot settle refunds, complaints or angry customers, and a customer who cannot reach a person leaves. Show a way to a person in the first message. Hand off with the full chat attached when the customer asks or the bot is unsure, so nobody repeats the story.

![Parvez Akther](https://www.thrivedesk.com/_astro/parvez.D6nO2bZR_R4Rks.webp)

Written by

[Parvez Akther](https://www.thrivedesk.com/author/parvez/) ThriveDesk

Parvez is the co-founder and CEO of ThriveDesk, and cares about customer experience and support. Parvez is an open source enthusiast and a father of three.
