
Beyond FAQ answers, an enterprise chatbot can look up a live record for the person asking. It can change a record inside rules you set. It can also run a multi-step workflow across your systems, such as granting access, onboarding a new hire or posting a daily alert to the team that owns a number. Each step up needs deeper access to your systems and tighter limits on what the chatbot may do. So the use case you choose shapes the build more than the model does.
Companies are moving past the FAQ bot, and Gartner expects many of those projects to fail. In June 2025 Gartner predicted that by the end of 2027, over 40% of agentic AI projects will be canceled. It blamed escalating costs, unclear business value or inadequate risk controls. In the same release, Gartner said many vendors were rebranding AI assistants, RPA tools and chatbots as agents, even when the products had no substantial agentic capabilities. It estimated that only about 130 of the thousands of agentic AI vendors are real. Sort your use cases by what each one needs from your systems. The ones you can ship today then stand apart from the ones that would stall.
Enterprise chatbot use cases fall on four levels. Each level includes the ones below it, and each adds a requirement your systems and your team have to meet.
| Level | What it does | Example | What it needs |
|---|---|---|---|
| Answer | Replies from approved documents and cites the source | "How many days of parental leave do I get?" | A current knowledge base with a named owner |
| Look up | Reads one live record for the person asking | "Where is order 4471?" | Read access to your CRM, ERP or HR system, filtered by role |
| Act | Changes a record inside your rules | "Request access to the finance dashboard" | Scoped write permission, limits and an approval rule |
| Orchestrate | Runs several steps across systems, sometimes unprompted | Setting up a new hire from a signed offer | A workflow engine, error handling, a log and someone to run it |
FAQ bots stop on the first row. The second row needs an integration with the system that holds the record. The third needs permissions you are willing to grant and a rule for when a person approves. The fourth needs an engineer on call after launch, because a workflow that runs every night will eventually meet a record nobody planned for.
Most departments have use cases on more than one level.
Pick a use case to see which level it needs, what the chatbot reads and writes, and which decision stays with a person.
A chatbot that changes records needs four controls that an FAQ bot never needed. First, it has to know who is asking, so the sign-in from Slack, Teams or your intranet maps to a role. Second, it reads only the records that role may see. Third, every change is checked before it runs, against limits you set and, where your policy says so, a person's approval. Fourth, every action is logged with the records read and the approver, so anyone can see later what happened.
Two production systems show how far these controls go in practice. On Pinkcube's after-hours chat agent, the agent that talks to customers has no permission to create tickets at all. A separate triage agent reads each finished chat and creates the ticket the chat agent promised. As a result, every ticket the customer was told about exists. The Pinkcube case shows the full setup.
A Dutch Odoo implementation partner was building a system for a dental care group. Ovidius moved the group's appointment scheduling out of the ERP and into a layer built on n8n. Every night, five sync workflows feed a matching step. An AI agent then picks the best slot for about 1,500 appointments a week across 200 practitioners. Each appointment it cannot place produces a report saying why. The AI pilot page describes how that build was proven on the partner's own data first.
The fourth level includes chatbots that speak up without being asked. IES Limited is a travel insurance group with four brands. It emailed a 25-page MI pack to around 50 people every working day, and a collapse in its quote funnel once took 20 days to notice. The system Ovidius built reads the pack when it lands at 11:30. By 12:00, it posts alert cards in Microsoft Teams to six audiences, and each audience sees the metrics it owns.
The design rule that makes this safe for a finance team works for any chatbot that reports numbers. The database calculates every figure, and the language model only writes the sentence around the figures it was handed. A verification step names any number the model was not given. Once, the model put two figures into a brief that were not in its input. The brief said so at the top and asked for verification before it went out. The IES daily MI alerting case has the detection logic and the results.
A chatbot project stalls when its use case sits a level above what the organization can support. The pilot answered questions from a sample of documents. Production then needed live data, permissions nobody had agreed or an owner for the knowledge base. Three gaps cause that mismatch.
The controls that stop an agent before it acts on a bad answer are covered in our article on AI guardrails.
The AI use case canvas gives you a one-page format for steps 2 to 4. If you first need someone to find and rank use cases across departments, the AI Audit ends in a ranked 90-day roadmap. To compare the off-the-shelf options before a custom build, read our guide to the best enterprise AI chatbot for your use case.
An FAQ chatbot answers from a fixed set of questions or help articles. An AI agent can also call your systems. It can look up a record, change it inside the permissions you grant, and run several steps in one conversation. Gartner has warned that many products sold as agents are rebranded chatbots, so ask any vendor which systems the product writes to.
The most common are customer service lookups such as order status, and IT service desk requests such as password resets and access requests. HR policy answers, finance status checks, scheduling and answers from internal knowledge bases are common too. Proactive alerts, where the chatbot posts to a team without being asked, form another group.
Yes, through the system's API, with credentials limited to the actions you approve. Every change should pass a check against your limits first. It should be logged with the records the chatbot read and anyone who approved it.
Give it the narrowest permissions that work, and check every proposed change against your rules before it runs. Send anything above a limit to a person for approval. On Pinkcube's build, the customer-facing agent has no ticket permissions at all, and a separate agent creates every ticket.
A guarded chat agent like Pinkcube's goes from kickoff to live in 5 to 7 weeks. For a new use case on your own systems, an AI pilot builds a working prototype on your staging data in 2 to 6 weeks. The pilot ends in a go or no-go report.
If your first use case needs live data or actions, see how we build an enterprise AI chatbot on your own systems. You can also book a discovery call and bring the request you most want off your team's plate.