Ticket Detail

Everything about one job, on one screen.

The email that started it, every reply since, who owns it, what it is waiting on, and the decision you need to make, without opening a second tab to find any of it.

Start free View pricing
The record

One timeline, not four places to look

Every ticket keeps a single history: inbound email, replies your team sent, internal notes, status changes, assignments and the steps the workflow took. Every entry carries its own date and time, and it reads top to bottom, so picking up someone else's ticket takes a scroll rather than an explanation.

Emails render in place: long messages collapse, so a forwarded chain doesn't bury the note underneath it
Automated steps are on the same timeline as human ones, so you can see exactly where a person took over
It closes visibly: resolved, escalated or cancelled lands as the last entry, not as a status you have to go looking for
WO-1042 · Leak in unit 4B

Email received

dana@brightside.co

Leak in unit 4B, water coming through the ceiling.

Assigned

Workflow

Routed to Work Orders · assigned to Marcus

Note

Marcus (internal)

@priya can you confirm the vendor is covered for this building?

Reply sent

You → dana@brightside.co

A plumber is booked for Thursday 9am. We’ll confirm once onsite.

Replies

Talk to the customer, or talk to your team

One composer, two modes. A public reply sends a real email from your connected mailbox, threaded to the original, with the people already CC'd kept in the loop. An internal note never leaves the building.

Public replies thread properly, so the customer sees a conversation instead of a stack of unrelated messages
Internal notes are unmistakably internal: a different colour, a different tab, and no send-to-customer path
Replying never moves the workflow. Answering a question is not the same as advancing a process, so RouteWrk refuses to guess. The flow moves when the step it is waiting on completes
Reply
Public replyInternal note

To: dana@brightside.co · cc: super@brightside.co

Thursday 9am is confirmed. I’ll send photos once the work is done.

Send replyThreads to the original · CC everyone
INV-8871 · waiting on you

Approval needed: $4,180 over threshold

Northside Plumbing · Invoice #8871 · matched to WO-1042

ApproveReject

Decide here. The workflow picks up from your answer

Decisions

The decision happens where the work is

When a workflow reaches a step that needs a person, the ticket parks and the question appears on its detail page, with the context needed to answer it. Approve or reject, tick off a checklist, review a drafted email before it sends, pick the photos that go to the customer.

The ticket waits, it doesn't fail: parked work is visible, not lost in a queue nobody checks
A strip at the top shows the route: the steps already done, the one it sits at now, and what comes next
Routed by mistake? Send an email ticket back to the inbox in one click and start it again properly

The rest of what's on the page

The details that decide whether a handoff is clean or costs a phone call.

One owner, no ambiguity

Assign the ticket to anyone with access to the workspace, or grab it yourself. The change lands on the timeline, so "who picked this up" is answered on the record instead of in a chat thread.

Everyone involved, with roles

A ticket carries its people (requester, vendor, onsite contact, CCs), each with a role rather than a loose email address. Open one and you know who to talk to before you read a word.

Fields that fit your work

Status, priority and category come as standard; the rest are yours. Define the fields a workspace needs and they render on every ticket in it. No schema change, no developer.

Attachments stay with the ticket

Photos and documents from inbound email, or dropped in by hand, live on the ticket in private storage, not in someone’s downloads folder.

@mention a teammate

Type @ in an internal note to pull someone in. They get a notification with a link straight to the ticket, and the mention stays on the record.

Optional SLA clocks

Turn on SLA policies and every ticket shows a live chip: time to first response, time to resolve, and how long it has been parked at a gate. Tracking and display only: a breach never silently changes what your workflow does.

More of the platform

Give every job one home.

Create a workspace, connect your mailbox, and work your first ticket end to end.