Product case study

FoxDesk: the client-support system we built for our own work.

At AENZE, customer requests, implementation notes and billable time needed one reliable record. FoxDesk grew from that workflow: receive the request, assign responsibility, record the work and send the client a clear report.

The screenshots use fictional data from an isolated demonstration workspace.

Before FoxDesk

The help desk and the work record told different stories.

A request might begin in email, move into a ticket, continue in implementation notes, and finish in a separate timesheet. The team could solve the problem, but reconstructing who did what, for which client, and how long it took created avoidable work at reporting time.

FoxDesk ticket detail with fictional customer conversation, assigned owner, and recorded time
One ticket keeps the request, responsibility, work, and result together.

The workflow

Four connected steps, with the ticket as the shared context.

  1. ReceiveEmail and portal requests become tickets with the original context intact.
  2. OwnEach request gets a responsible person, priority, state, and next step.
  3. RecordTimers and exact manual entries remain connected to the work that produced them.
  4. ReportThe client sees completed work and its duration in one understandable report.
FoxDesk team dashboard with fictional clients, agents, and 30-day work activity
The team sees current workload and recorded work across several clients.
FoxDesk public client report with fictional work entries and exact durations
The client report explains the work behind the total before invoicing.

Two operating choices

Open source stays public. Cloud removes the operational work.

FoxDesk Open Source

The public AGPL-3.0 application is for teams that want to run FoxDesk on infrastructure they control and manage their own updates, backups, email, and availability.

View the public repository

FoxDesk Cloud

The hosted service is for teams that want the same request-to-report workflow without installing or operating a server. Its tenancy, billing, and platform administration remain private SaaS modules.

Explore the public beta