One inbox for everything waiting on a decision.
Your team checks five places before lunch: the address nobody owns, the Search Console tab nobody opens, the board where three tasks went past their date, the integration that stopped collecting last Tuesday. Viably sweeps all of them and puts what needs deciding into one list you can finish, with the right ending already on the button.
Free plan forever with no credit card, and unlimited seats on every plan.
ViablyEvery ending here writes to the board, the record or the repository.
Five systems sweep in. Your team works one queue.
Work spread across five queues means none of them ever reaches the bottom. Viably reads what your workspace already holds and collapses it into a single list with one finish line at the end of it.
- People
Everyone who wrote in and is still waiting, plus the follow-up somebody promised and let slip. Each card is matched to the contact record, so it already knows what the person is worth.
- Work
Tasks that ran past their date, and who is holding them. Work due later this week stays out, because that asks for the work rather than for a decision.
- SEO
Your site, crawled every week and read against Search Console. Broken markup, pages that dropped out of the index, and the phrases you rank for and nobody clicks.
- Social
Accounts that have gone quiet, and the posts that did well enough to be worth a second one.
- Uptime
Endpoints that stopped answering, and the integrations that quietly stopped collecting last Tuesday.
Every card opens with the ending it is asking for.
Most triage tools give every row the same two buttons and leave you to translate. A customer who has waited two days is not an issue or a task, and neither is an endpoint that stopped answering at 2am. Viably reads what the item is, promotes the one ending that fits, and keeps the rest a click away.
An enquiry is asking for an answer, so the button is Reply and it opens their record with the composer ready. Answering is what takes them out of the queue, so nothing files a second record of it.
Pick your queue once. Viably remembers it.
One list for the whole company is triageable and wrong for everybody whose job is not the website. The inbox narrows on a single axis: everything, what is yours, one system, or one department. The status run beside it holds the items you noted, the ones you put to sleep, the ones you said no to, and everything that has already left.
- Mine, without hiding the unclaimed
Your own properties, contacts and tasks, plus everything nobody has picked up yet. Unclaimed work stays visible to the whole team, since that is the work most likely to be dropped.
- The department you already told us
Sales sees sales, hiring sees hiring. Your pick is remembered per workspace, so a bare link to the inbox opens on the list you work rather than on everything.
- Counts that answer the question you are asking
The figure beside a queue is how many rows you get if you click it, counted in the status you are already in. No rail advertises twelve and hands back three.
Say no once, and have it stick.
A queue that re-proposes what your team already declined is one they stop opening by the second week. Every decision here is durable, reversible, and kept with the reason somebody gave for it.
- Dismiss it, and say why
The reason is kept with the item, and the decision can be taken back from the Dismissed view. Nothing is deleted, so your team can say no freely and still find it again.
- Snooze against the number, not the calendar
A snoozed item comes back when the traffic, the money or the wait behind it grows by half. If the number never grows, the item stays asleep.
- “Fixed” is a claim, so we test it
Marking a defect fixed holds it for a fortnight and then checks the next crawl. A fix that never shipped is somebody's problem again this month instead of being filed forever.
- Where things went
Every item that became an issue, a task, a pin or a pull request is listed with a link to where it landed, so you can read back what a week of triage actually produced.
Triage in the browser, decide in the channel
Send any card into Slack with a note when it needs somebody else's eyes. The item stays in your inbox until a decision is actually taken, and whatever you file lands in the channel the power already writes to. @Via keeps the thread and the record in step from there, so nobody has to report back on what happened.
Sent from the inbox by Jim. It stays in his list, because telling the channel is not deciding anything.
- Down
- 38 minutes
- First failure
- 02:14
- Other pages
- Answering
That's the cache rule I changed last night. Taking it.
Filed from the inbox, so the card has left the queue and says where it went.
- Repo
- viably/on_next
- Assignee
- @oscar
- Status
Triage is a team sport, so every seat is free.
Viably+ is billed per workspace rather than per person, so putting your designer, your support lead and your founder on the same queue costs nothing extra. The Free plan carries the whole inbox, every ending included.
Every issue, every task on the kanban, and everything that moves the needle for our team goes through Via. It organizes work in a way that is truly only possible because of all the automation hooks that it packs with it. We cannot imagine having to work without it after the third month.
Gerald BryanLead Architect, Sectors Financial AI Suitesectors.appQuestions about the Team Inbox
Give your team one list they can finish.
Start free, connect one source, and watch the first decisions leave the queue this afternoon.
- Free to start
- No credit card required
- Powers on when you need them