What is ReQuest DESK?

ReQuest DESK is an AI-first service management platform. You describe what your organisation does — or point it at a document — and it builds your service catalog, classifies every incoming request across email, chat, WhatsApp and voice, and routes each one to the right owner with a committed resolution time.

How is it different from a traditional service desk or an AI chatbot?

Traditional platforms make you configure the catalog by hand over months. AI-augmented tools bolt a chatbot onto an existing ticket form. ReQuest is AI-first: the catalog generates itself from your own documentation, and AI classification is the core of the request flow — not an optional add-on.

How long does it take to go live?

Days, not months. The AI Builder session, catalog review and portal configuration can typically be completed in a single working day, and the platform delivers value from the first day of operation.

Do I need an IT team or technical specialists?

No. ReQuest removes the specialist configuration burden entirely — the AI does the work that consultants and administrators have always had to do by hand.

Which channels does it support?

Web portal, embedded chat widget, WhatsApp and other messaging apps, and voice (transcribed). Every channel produces text, which the same AI classifier processes identically.

How does it avoid wrong answers or hallucination?

Every request is matched against your own service catalog and knowledge base and confirmed with a confidence score, so answers come from what you actually offer. The platform routes anything outside known patterns to a human with context.

What is the AI allowed to do on its own?

Only what you grant. Autonomy is set per request type and per resolution step — the AI can own a step, hand it to a human, or wait behind an approval gate. High-stakes actions like refunds, policy exceptions or clinical questions are typically gated: the AI prepares everything, a human approves. Full autonomy is a switch, never a default.

Does it integrate with the systems we already use?

Yes — through connectors and skills. Connectors let the desk act inside your existing tools (calendars, CRMs, billing, ticketing) so your systems stay the source of truth. Skills package how to operate one of your systems or procedures — teach it once, and every request type that needs it can use it.

Can it handle bookings and scheduling?

Bookings are built in. Appointments, resources and time slots are first-class: the desk offers times, books them, and absorbs reschedules.

No. It works for salons, clinics, facilities teams, professional services, trades and local government just as well as IT — any organisation that delivers defined services.

Does it work for MSPs managing multiple clients?

Yes. A single deployment supports multiple scoped catalogs through the service registry — one platform, N clients, each with its own branded portal.

Priced for access, not for enterprises — no six-figure license and no implementation tax. Start with a pilot and go live in days, then scale as your service layer grows.

Blog

Notes from the front desk.

Practical writing on request handling, AI you can govern, and the service layer most businesses never had time to build.

AI & trust13 July 2026 · 4 min read

Can you trust AI to talk to your customers? The case for gates and approvals

Handing customer conversations to an AI feels like a leap of faith, and most business owners are right to hesitate. The honest answer to “can you trust it?” is: only with governance. Trust is not a promise a vendor makes — it is an architecture you can inspect.

Read the article

Cost of chaos9 July 2026 · 4 min read

The real cost of a missed customer request

A missed enquiry never shows up on a report. Nobody logs the email that sat unanswered or the voicemail nobody returned — which is precisely why the cost is so easy to underestimate. It is rarely one lost sale; it is everything that sale would have led to.

Read the article

MSP4 July 2026 · 4 min read

How MSPs onboard a new client's service desk in a day

For an MSP, onboarding is where margin is decided. Every week between contract signature and a working service desk is a week of delivering ad hoc, and every hour of catalog workshops is senior time you cannot bill. The bottleneck is not tooling — it is how catalogs get built.

Read the article

Operations28 June 2026 · 4 min read

The after-hours problem: who answers when your business sleeps?

Your customers do not keep your office hours. The booking enquiry arrives at 9pm from someone’s sofa; the leak gets reported at midnight; the urgent question lands on a Sunday. Whatever answers in those hours — or fails to — is speaking for your business.

Read the article

AI & trust25 June 2026 · 4 min read

AI receptionist vs AI service desk: what's the difference?

An AI receptionist answers the phone nicely. An AI service desk makes sure the thing the caller asked for actually happens. The two get lumped together constantly, and confusing them costs real money.

Read the article

Operations19 June 2026 · 3 min read

How to stop answering the same question 20 times a week

If you answer the same question twenty times a week, that isn't an annoyance — it's data. Repeated questions are the most automatable work in your business, and most owners handle them the most expensive way possible: personally, one at a time.

Read the article

Channels15 June 2026 · 3 min read

WhatsApp is where your customers are. Is your business actually there?

Your customers stopped ringing and started messaging years ago. Most businesses answer WhatsApp the way they'd answer a mate — from one phone, personally, whenever someone happens to see it. That gap is where requests go to die.

Read the article

ITIL8 June 2026 · 4 min read

What is a service catalog — and why your business already has one

Every business already has a service catalog. It lives in the owner's head, the senior technician's memory and a few hundred email threads. The catalog isn't the problem — the fact that it's unwritten is.

Read the article

ITIL3 June 2026 · 4 min read

ITIL for small business: what actually matters (and what to skip)

ITIL has a reputation problem in small businesses: it sounds like binders, committees and a consultant on retainer. That is a shame, because underneath the ceremony sits the best thinking anyone has done about handling requests reliably. You can steal the useful parts and leave the rest.

Read the article

Reputation28 May 2026 · 3 min read

Your front desk is your brand: consistency as a reputation strategy

Customers never see your craftsmanship queue, your supplier negotiations or your margins. They see how fast you answer, what tone you take and whether you say the same thing twice. To them, the front desk is not a department of the business. It is the business.

Read the article

Operations24 May 2026 · 4 min read

From inbox chaos to audit trail: why every request needs an owner and a deadline

The shared inbox is where accountability goes to dilute. Five people can see a request, which means each of them can reasonably assume someone else has it. 'Someone will handle it' is not a workflow — it is the exact mechanism by which things get lost.

Read the article

Strategy19 May 2026 · 4 min read

Your small business doesn't need a help desk team. It needs a service layer.

When requests start slipping, the instinctive fix is a person: an admin, a coordinator, eventually a help desk team. Sometimes that is right. But often the missing thing is not hands — it is structure, and hiring more people into a structureless process just gives the chaos a bigger audience.

Read the article