← All projectsReact / Operations Console

SignalDesk

Put exceptions from separate workflows into one place with an owner and a next action.

Concept illustration of SignalDesk workflow; no live customer data
Project
SignalDesk
Audience
Growing companies with payment, commerce, integration and client-operation exceptions
Type
Independent working prototype
Evidence
Repository, documentation and tests

Where work gets stuck

Operational problems may surface in different tools, making it hard to know which issue is urgent, who owns it and what should happen next.

This project is for growing companies with payment, commerce, integration and client-operation exceptions. The aim is to make the next decision visible to the people doing the work.

What a team might do

A payout mismatch, a retried order update and a client waiting for information appear in the same queue. A team lead filters urgent cases, assigns an owner, records the next step and reviews the history instead of rebuilding the story from chat messages.

What the prototype does

  • Priority queue, filters, saved views and ownership
  • Review drawer, next actions, activity trail and bulk updates
  • CSV export and fictional alert generation

What I built and tested

I designed and implemented this independent prototype to explore the business workflow and its technical constraints. React, TypeScript, typed state transitions, local persistence, accessibility work and tests. The repository explains how to run its real implementation and tests.

Explore the demo and the code

Open the interactive browser demo to understand the workflow. Read the source and README for installation, local testing and implementation details. Your demo changes remain in your browser's local storage.

What this version does not claim

The Pages frontend is interactive with fictional data stored in the visitor's browser. It has no server, login or live payment and commerce integrations. No customer outcomes have been measured for this independent demonstration.

Could this fit your team?

Bring three recurring exception types to a guided walkthrough using fictional records. Test whether the queue makes ownership and handoffs clearer. There is no fee or obligation to adopt a product. Any work involving real data or a production deployment would need a separate scope and appropriate safeguards.

Tools and skills

ReactTypeScriptOperationsFrontend

Which operational issue gets noticed too late in your team?

Tell me how your workflow currently works. We can explore a small guided pilot or discuss a software system tailored to your organization.

← Engineering portfolioExplore the Business Systems Lab →