One ops queue instead of three inboxes and a lying spreadsheet
Work was disappearing across email aliases, Slack DMs, and a sheet that was always slightly wrong. We built one queue — owner, status, and SLA visible — so nothing depends on someone remembering to check a folder.
- Strategy
- Intake firstQueue designn8n
- Design
- Visible ownershipSLA digests
- Client
- Internal opsShipped in weeks
Outcomes
What changed after handoff
“Did anyone see this?” stopped
Requests used to sit for a day or more whenever they landed in a folder nobody was checking that week. Every item now has an owner and a visible state from the moment it arrives, so the daily Slack ritual of chasing down status — asking, waiting, following up again — went quiet because the queue already answered it.
One door for every request
Forms, email forwards, and Slack handoffs used to depend on someone remembering to check three different places; requests that fell into the wrong one could sit until the following week. All three now land in the same queue within minutes of arriving, regardless of which channel they came in through.
What shipped
The system in plain terms
- Multi-channel intake into one normalized record
- Owner and status visible on every item
- SLA timers and overdue digests
- Optional AI triage with a written rationale — never a black box
- Handoff docs so the team can extend the queue later
The build
How we got there
Background
Requests arrived everywhere: email aliases, a form nobody trusted, Slack DMs, and a spreadsheet that was always slightly wrong. The problem wasn’t “we need AI.” It was “we need one place work can’t disappear.”
We scoped a lightweight queue, not a new platform. Intake first. Judgment second. AI only where a short rationale helps a human decide faster.
Challenges
Different channels meant different shapes of request. Items sat for days because ownership wasn’t visible. Earlier tools failed when they asked the team to change how they worked overnight.
The build had to feel familiar on day one and still beat the spreadsheet by week two.
Ops would abandon the sheet only if:
- Every channel feeds one queue
- Owner and status are always visible
- Escalations don’t mean copying threads by hand
Solution
n8n normalizes intake and writes into the kind of internal tool the team already knew how to use. Status stays honest. Optional triage assists sit behind a clear rationale — never something that blocks the work.
Fixed price, short timeline, full source at handoff. The spreadsheet was a backup for a week. Then it got archived.
Next
Got a workflow that hurts this much?
Bring us the one costing your team the most time. We’ll tell you straight whether it needs a build — or a smaller fix.