Agencies and studios

You bill for delivery, so you have to prove it

Multiple clients, each convinced they are the only one. Certainty HelpDesk gives every client their own view of their own records, so status conversations stop being a memory test.

How work reaches you today

The three things that go missing

01 / THE STATUS CALL

Half of every client call is spent reconstructing what happened since the last one.

02 / SCOPE, UNARGUABLE

The extra work was agreed in a voice note, so it was never billed.

03 / KEY-PERSON RISK

One account manager holds the history. They go on leave and the account goes quiet.

Client workspaces

One workspace per client, isolated by role

Each client organisation sees its own records and nothing else. There is no shared tracker to accidentally expose, and no internal priority a client can read as a promise.

  • A client view scoped to one organisation's records
  • Internal tasks, priorities and unassigned work stay internal
  • Access set per role, per module, enforced on the server
REQ-041In progress

Export button does nothing on Safari

Raised by the client2 Aug · 09:41
Sorted into an issue · ISS-1042 Aug · 11:02
Picked up by Abdullah3 Aug · 08:15
ResolvedPending
Change requests

Scope creep becomes a change request, not an argument

When an ask grows, it becomes a change request linked back to the original request. The moment scope diverged has a timestamp and an author, so the invoice conversation is about a record rather than a recollection.

  • Change requests keep a link to the request that spawned them
  • Target date and owner on every change, so nothing drifts silently
  • The original wording is preserved, not summarised
CR-018 raised from REQ-039Linked to the original ask
14 resolved this monthAcross 3 client workspaces
Workload

Workload across every client on one screen

Your delivery team works one list, not one list per client. Overdue work is grouped as overdue, which is the only grouping anyone acts on when a week goes sideways.

  • My work view across every project you touch
  • Overdue grouped as overdue, not buried in creation order
  • Calendar view for anything carrying a due date
In progress2

Set up Postgres backup cron

HighAug 6

Make QR generator a systemd service

LowAug 24
What you would use

The parts that carry this kind of work

Every tracker, list and calendar reads the same record, so the ticket you close is the task that disappears.

Issues, features, changes, requests

Four work item types

Each type carries its own triage rules, sorting, assignment, statuses and closing reasons. Nobody has to pretend a change request is a bug to get it tracked.

  • issues
  • feature requests
  • change requests
  • client requests

AI sorts the obvious, people decide the rest

Triage workflow

Where AI triage is enabled, every client request is read on arrival and given a type. When that reading matches what the client already said it was, it is filed straight away and stamped as sorted by AI. When it does not, or when it needs a person for any other reason, it is held with the reasoning attached, so whoever picks it up starts from an argument rather than a blank form. Pre-triage commenting means the conversation starts the moment it lands. The feature is enabled per deployment, on request.

  • auto-filed on agreement
  • held with reasoning
  • sorted-by-AI provenance
  • enabled on request

Meetings in the browser, with a page each

Video, captions and summaries

A room with a lobby, guests, screen share and live captions, opened from a link with nothing to install. Every meeting leaves a page carrying who was there and for how long, the transcript, the recording the host's browser made, the write up, and the work items it was linked to. A recurring series keeps one link and one record per occurrence.

  • lobby and guests
  • live captions
  • written summaries
  • linked to the work

The weekly sync on one board

Project tracking and the secrets register

Every client, internal and volunteer project with its stage, RAG, lead and man-days, and one structured update a week, with a push to the lead when it is missing. Sheets of your own sit beside the board, the week exports as an Excel workbook, and a secrets register warns the owner and the project's managers before a credential expires.

  • weekly updates
  • custom sheets
  • Excel export
  • expiry warnings

Every edit is versioned

Revision history

Content revision history on work items. If the scope quietly changed on Tuesday, the record says who changed it, what it said before, and when.

Per-item visibility

Privacy controls

Sensitive records stay hidden from anyone without rights to them. That holds in search, in counts, in dashboards and in notification fan out, not only in the list view.

Next step

Walk your own pipeline with us

Bring one messy client project. We will set it up live on the call and you can see whether the shape fits how you actually work.

partnerships@dhcertainty.com