Helpdesk Chatbot Without a Ticketing System

A helpdesk chatbot answers customer questions on your website, takes the requests it cannot answer and forwards them to you, which is probably the job you wanted help desk software to do. Most pages on this term are written for IT departments and support teams with ticket queues. This guide is for you if you answer customers yourself, or with one or two colleagues.

What is a helpdesk chatbot?

A helpdesk chatbot answers visitor questions from your own website and files, captures the ones it cannot handle, and forwards them to your team with the full conversation: the job of a help desk, without ticketing software. The same term also covers bots that help a company's own staff with password resets and IT requests. This guide is about the other kind, the one your customers talk to on your website.

Ultimo Bots is the AI agent platform where you describe in plain words what your agent should do and Mo, the builder in the AI Studio, builds it: skills on public APIs and MCP servers that do real work in your own systems. Answering from your content, taking requests and handing over to you is where it starts. The same agent answers on your website, WhatsApp, Messenger and Instagram.

The examples below use Larkhollow Fiber, a fictional local internet provider. Its owner, Tess, answers customers herself, with one technician who helps when she is out on a job.

Do you actually need a ticketing system?

If one to three people answer all your customer questions, you probably do not. A ticketing system exists to divide work between many people: queues, assignment rules, service-level timers, reports per agent. Ask yourself who you would assign a ticket to. If the answer is you, every time, those features manage a line that does not exist.

The price model follows the same logic. As of November 9, 2026, Zendesk calls its pricing "primarily seat-based (per agent, per month)", and Freshdesk lists each plan per agent. An AI help desk can bill differently: with Ultimo Bots you pay for answers in AI credits, and your colleague costs nothing extra.

What you need is smaller: repeat questions answered, nothing lost, and a person who can step in. Here are those jobs in three setups.

What a helpdesk chatbot does instead of tickets

It answers what it can from your content, forwards the rest as a request with the whole conversation, and lets you step into the chat.

• Answers from what you already wrote. Your website pages, PDF and Word files, Q&A pairs, Google Drive, OneDrive and Notion all feed the same knowledge base. The agent answers from your content, not from guesses about your business.
• Requests that land under Leads. Each forwarded request sits in Leads with the whole conversation and counts as unread until you open it. The new-lead alert reaches you at once by email and in the portal, and in Slack or Telegram if you switch those on.
• The full history when you step in. In the live chat you see the full history. From the portal Inbox you can even reply to a website chat that has ended: the visitor sees your reply if they come back to your site.
• The same help on other channels. On WhatsApp, Messenger and Instagram the same agent answers, and you can pause the AI for one conversation and reply from the portal Inbox.

A fictional visitor types "How do I restart my router?", and the agent answers from Tess's support page: "I'm Larkhollow Fiber's AI assistant. Unplug the router, wait 30 seconds and plug it back in. The light should turn solid green within two minutes."

Already keep tickets in a system of your own? Where it has a public API with an API key or bearer token, Mo can build a skill that opens one from the chat, as our 24/7 support guide shows.

How do you set up a helpdesk chatbot?

You give the agent what you already wrote, test it with your real questions and put it on your site.

1. 1

   Give it what you already wrote

   Add your website as the first source, upload your support PDFs and add Q&A pairs for what your site leaves out. The agent reads the text on your pages and images only by their alt text, so post troubleshooting steps as text.

2. 2

   Ask your real questions in the Test tab

   Open the AI Studio and ask what customers actually ask. Test chats use AI credits, and a request you forward there creates a real lead and a real email, so you see exactly what will arrive.

3. 3

   Decide who hears about requests

   On the Notifications page, check the event New lead generated and add your colleague's address to the email recipients.

4. 4

   Put it on your site

   On Wix, install from the App Market without code. On WordPress, install the plugin. On Webflow, install from the Marketplace. On most other sites, paste a three-line snippet before the closing body tag.

5. 5

   Switch yourself online when you can help

   While at least one teammate is online in the live chat, visitors see a "Talk to a human" button. Your status stays as you set it until you change it.

The website chat shows "You are chatting with an AI assistant" above the first message, on every plan. The sample chats here also use one behavior, saved word for word under Behaviors > Add Behaviors in the AI Studio's "Your agent" panel: "If none of your replies so far has said you are an AI assistant, say so briefly in this reply. The welcome message at the start does not count, since the visitor may not have seen it. If asked whether you are human, say plainly you are an AI."

Where does a question go when the agent has no answer?

It gives what answer it can, offers once to forward the request to your team, and asks for contact details only after the visitor says yes. That is the built-in Lead Generation skill, on every new agent: collecting a problem and forwarding it is its job. Our fallback message guide covers what the reply should say.

Take a request Tess's pages leave open, in a fictional chat: "Can you run a line out to my detached workshop?" The agent answers: "I'm Larkhollow Fiber's AI assistant. Our pages do not cover extending service to a separate building. I can forward your request to the team so they can follow up. Shall I?" After "Yes, please." it asks for a name and email, and the visitor writes "Priya Nair, priya.nair@example.com". The agent closes: "Thanks, Priya. You'd like service extended to your detached workshop. The team has your request."

Tess finds the request under Leads with the whole conversation, and the same conversation is in the new-lead email. If she needs more to act on it, she asks Mo to add fields such as a phone number or street address to the skill.

When someone wants a person

People hate bots that trap them, rightly, so the route to a person stays short.

• Tess is online. A visitor clicks "Talk to a human", Tess clicks Join, enters her name as the display name and the visitor sees "Tess has joined the chat." The AI stops replying, she has the full history in the same window, and when she leaves the agent takes over again. Your own live chat messages use no AI credits.
• Tess is out on a job. With nobody online, the button stays hidden. The agent keeps answering and offers to take the request through the lead skill, so Tess reads it when she is back at her desk.

When a line goes down, the agent reads your status page

The agent reads the incidents you post on your status page, through a skill Mo builds from your description. For Larkhollow Fiber, one question fills the inbox whenever a line goes down: "Is the internet down in my area?"

Tess already posts every outage on her hosted status page, with each area as a component, so she posts an outage once and the chat reads it.

Mo reads the docs and asks Tess for the key in a secure field; the key is stored encrypted. Mo then builds the lookup for open incidents, runs it against the real page and reports what the agent can now do.

Mo can build on any public API that works with an API key or bearer token, and Instatus is one. Per its API docs on November 9, 2026, requests carry an API key as a bearer token, created in the account's developer settings. Its incidents endpoint returns each incident's name, status, start time, affected components and updates, and can filter by status. Better Stack documents status page endpoints with a bearer token as well.

Two fictional visitors, two outcomes:

• The area is listed. A visitor asks "Is the internet down in my area?", and the agent answers: "I'm Larkhollow Fiber's AI assistant. Which area are you in?" After "North Ridge" it replies: "Yes. Our status page lists a fiber cut affecting North Ridge. The latest update says the crew is on site."
• Nothing is listed. A visitor asks "Is your service down in Mill Creek? My connection keeps dropping." and hears: "I'm Larkhollow Fiber's AI assistant. Our status page lists no incident for Mill Creek right now. I can forward this to the team so they can look into your connection. Shall I?" After a yes, the lead skill takes over, and Tess gets the request with the whole conversation.

The lookup reads the incidents you post on your status page, the same for every visitor, so no customer account, address or record is involved. Each answer that uses it is the usual 1 AI credit on Ultimo Core. The skill takes one of your plan's skills (Smart 3, Boost 10, Ultimo 30), and building it with Mo uses more credits than a quick question. You can connect your other systems in the AI Studio too, through a public API or an MCP server, and ready-made skills cover Wix, Stripe, Cal.com, Calendly, HubSpot and Mailchimp.

What does a helpdesk chatbot cost?

As of November 9, 2026, Ultimo Bots Smart costs $29 a month or $19 billed yearly with 500 AI credits, Boost $59 or $39 with 2,000 and Ultimo $249 or $199 with 10,000. A standard answer uses 1 AI credit, every plan includes all channels and live chat, and teammates are free. If you install from Wix, billing runs through the Wix App Market, so the listing shows your price. See pricing.

How that compares with per-seat and per-resolution tools is covered in what an AI agent costs and in our price check of low-cost options.

Who answered your last 20 customer emails?

Open your inbox and count. If one to three people wrote those 20 replies, the ticketing question is settled. The same 20 questions are your test set: start the trial, add your website and ask them in the Test tab of the AI Studio.

Each answer you would not give yourself tells you which page or Q&A pair to add. Each question that a look at public data in your own system could answer, such as a status, a schedule or free slots, is the first skill to describe to Mo.

Questions and answers