Support Inbox

How it works

What Support Inbox actually does once it is running.

A customer writes in

The message becomes a ticket with the request restated in one line, a topic, and a severity set from the impact they describe — not from how loudly they describe it.

They hear back straight away

An acknowledgement confirms you have it and repeats the problem back so they know they were understood. It promises nothing you have not verified.

The clock is watched

Each topic carries a response target. Every hour, anything past due or about to be surfaces, urgent first.

What you'll have

The point of running it — not the features, the result.

An instant first response, at the moment their patience is highest.

A queue ordered by impact rather than by who shouted.

Nothing quietly aging past the response time you promised.

What's inside

A template is a complete system, not a blank document with a nice name.

Its data, already modelled

Collections with the right fields, relations and views for the job — ready for your records the moment it installs.

Its automations, already wired

The workflows that keep it current, with their triggers configured. Turn them on and they run.

Its own agent

A specialist scoped to this Wapp that knows its data and tools, reachable from the same chat you use for everything else.

Yours to reshape

Add a field, change a rule, or restyle the app by describing the change. Templates are a starting point, not a cage.