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.

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.

The requests moved. The tracking didn't.

Customers reach for the channel with the least friction, and for most people that's the messaging app already open on their phone. A WhatsApp message is easier to send than an email and less committal than a call, so more and more genuine requests — bookings, complaints, quote enquiries — arrive that way.

But while email at least sits in a shared inbox, WhatsApp typically lives on one personal handset. The business is present on the channel without being organised on it — and the customer can't tell the difference until something slips.

This isn't a niche problem for youth-oriented brands. Landlords hear from tenants on WhatsApp. Clinics get rebooking requests on it. MSPs get "the printer's down again" on it. The channel arrived; the process never did.

What's wrong with answering from the owner's phone?

Everything works until it doesn't. One person answering personally feels warm and quick — right up to the week they're on holiday, off sick, or simply busy. Then the channel goes dark and nobody else can even see what was promised.

The structural problems stack up:

Untracked — no record beyond one person's chat history
Unowned — a message seen is not a request assigned
Unsearchable — try finding "that quote from March" across a year of chats
Working-hours only — messages sent at 9pm wait until someone wakes up
A single point of failure — the channel is one handset and one memory

What changes when WhatsApp is a first-class request channel?

Treat WhatsApp as a service channel and every message becomes a case. In ReQuest DESK, WhatsApp feeds the same classifier as email, web, chat and transcribed voice — one pipeline for every channel — so a booking request gets identified, logged with an owner and timestamps, and answered from your published knowledge base whether it arrived by message or by phone.

That also means the 9pm message gets a real, grounded answer at 9pm, not an apology at 9am. We've covered why that matters in who answers after hours — the short version is that the customer messaging at night is often the one comparing three businesses at once.

And because every request gets an owner, the promise made in a chat bubble carries the same committed resolution time as one made in writing. The customer notices no ceremony. Your operation gains all of it.

A channel is a setting, not a project

Historically, "adding WhatsApp" meant an integration project: vendors, scoping calls, a quarter of someone's time. That framing is out of date. When the service layer already exists — catalog, classifier, resolution chain — a new channel is just another door into the same building.

Switching one on should take a decision, not a roadmap. The hard question isn't technical any more; it's whether you're willing to treat a WhatsApp message with the same seriousness as a signed letter. Your customers already do.

The service layer you never had time to build — live in days.

Describe what you do — ReQuest builds the catalog, answers the routine, and routes the exceptions to your team.

Join the waitlist Request a demo

← All articles