Even the best AI chatbot sometimes meets a question it can't answer — or a visitor who simply wants to talk to a real person. With Chatbotty, those moments don't end in a dead end. Your chatbot offers to create a support ticket, collects the visitor's email, and hands the request over to you with a short, ready-made summary. In this guide, you'll see the whole journey: how the chatbot creates a ticket during a live conversation, where tickets land in your dashboard, and how to work with them using statuses and internal notes. ## When your chatbot offers to create a ticket Once support tickets are enabled, your chatbot keeps an eye on every conversation and steps in when a human touch is needed. Typical situations include: - A question is relevant to your business, but the answer isn't in your knowledge base yet - The visitor asks to be contacted by someone from your company - A business inquiry or partnership proposal comes in - The visitor reports a problem, complains, or asks for a refund - The visitor signals urgency and needs a real person In all of these cases, the chatbot politely offers to create a support ticket. And here's the important part: it never creates one behind the visitor's back. It always asks for permission first and collects a valid email address, so you have a way to follow up. ## How a ticket is born — a real conversation Here's an example from a bike shop chatbot. A sales representative named Antony opens the chat widget and proposes a business partnership. That's not something the chatbot can decide on its own — so it offers to pass the request to the team: The whole flow takes four short steps: 1. **The chatbot offers a ticket.** It recognizes the message as something the team should handle and asks if the visitor would like a support ticket created. 2. **The visitor shares their email.** This is how you'll get back to them later. 3. **The chatbot asks for consent.** A clear confirmation that the visitor agrees to be contacted. 4. **The ticket is created.** The chatbot replies with the ticket number — for example TKT-000001 — so the visitor has a reference for the future. Behind the scenes, the AI also writes a one-paragraph summary of the request. You don't need to read the whole transcript to know what the ticket is about. ## Turn on support tickets in your chatbot settings Enabling the feature takes one click. Open your chatbot in the dashboard, switch to the **AI & Behavior** tab, and turn on **Automatic Support Tickets**: Support tickets are available on the Elite plan and above. The free 14-day Evaluation trial includes them too, so you can try the full flow before subscribing. ## Where tickets arrive in your dashboard Every new ticket lands in the **Support Tickets** section of your Chatbotty dashboard. The list shows the ticket number, the visitor's email, the AI summary, the current status, which chatbot created it, and the date: Ticket numbers are yours alone — every account starts at TKT-000001 and counts up. If you run more than one chatbot for your website, the filters at the top let you narrow the list down to a single bot or a single status in seconds. ## Inside a ticket Click any ticket to open its detail page. Everything you need to act is on one screen: - **Contact information** — the visitor's email is a live link. Click it and your mail app opens with the ticket number already in the subject line and the summary in the body. - **Summary** — the AI-written description of what the visitor needs. - **Linked conversation** — one click takes you to the full chat transcript, so you always have the complete context. The link works both ways. When you browse a conversation that produced a ticket, you'll see a small ticket card right next to it: ## Keep track with statuses Every ticket moves through a simple lifecycle. Changing the status takes one click in the **Update Status** card: - **Open** — a fresh ticket nobody has touched yet. Every new ticket starts here. - **In Progress** — you've picked it up and you're working on it. - **Resolved** — the request has been handled. - **Closed** — the ticket is finished and archived for good. A quick glance at the ticket list tells you exactly what still needs attention — open tickets stand out in red, resolved ones turn green. ## Internal notes — your private to-do trail The notes section is where you record what you've actually done about a ticket. Each note is timestamped, and only you can see them — the visitor never does: Notes work best as a short diary of the case. For example: - *"Contacted Antony by email — asked for their product catalog and wholesale pricing. Waiting for a reply."* - *"Spoke with Mr. Antony on the phone. We agreed on an online meeting next Tuesday at 10:00 to go through the partnership terms."* If you come back to the ticket a week later — or a colleague picks it up — the notes tell the whole story at a glance. Added a note by mistake? Hover over it and delete it. ## A simple workflow that works Putting it all together, handling a ticket looks like this: 1. A new ticket arrives as **Open**, with the visitor's email and an AI summary waiting for you. 2. You reach out — click the email link, or call the visitor — and add an internal note about it. Switch the status to **In Progress**. 3. Once the request is handled, add a final note and mark the ticket **Resolved**. 4. When no follow-up is expected, set it to **Closed**. That's the entire loop: your AI chatbot catches the requests it can't solve, and you finish them with full context — no copy-pasting, no lost emails, no sticky notes. Tip: check your Support Tickets page as part of your daily routine. The status filter set to "Open" shows you instantly whether anything new came in overnight. Ready to stop losing the questions your chatbot can't answer? Turn on support tickets and let your AI assistant hand them to you on a silver platter.