Why a support desk should read like a ledger
We chose tabular numerals, monospace metadata, and a single editorial typeface for a reason.
The first time we sketched what the Reqdesk dashboard should look like, we drew a column. Not a kanban board, not a timeline — a column. Date, ID, subject, status, owner, age. Tabular, scannable, predictable.
That sketch became the brand.
Tabular by default
Numbers in a queue mean something. Two tickets opened 17 minutes apart should look 17 minutes apart on screen. Old support desks ran on grey, proportional digits where “1:23” and “12:03” were visually almost identical. Reqdesk uses tabular numerals everywhere a comparison is implied — column widths align, eyes land on differences first.
Editorial, not corporate
We chose Instrument Serif (italic, displayed) for headlines because almost no SaaS uses a true display serif. We chose Cedar (a deep teal) instead of the standard purple gradient because purple gradients have become a tell — “this is a generic SaaS landing page, please buy”. A support desk for a real team should look the way a daybook looks: ink, paper, restraint.
Mono for metadata
Filenames, IDs, timestamps, status keys, machine outputs — anything that came out of a system rather than a human’s keyboard — gets Geist Mono. The reader can tell at a glance whether they are looking at a sentence or at structured data.
Why bother
Because if the dashboard reads like a tax form, the team treats it like one. A desk that respects its own data shapes a team that does too.