Team Inbox

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.

Start free See what empties it

Free plan forever with no credit card, and unlimited seats on every plan.

Viably

viably.app/inbox

Inbox5 waiting

Bob Vance is waiting on a first replyAct now2 days waiting

“Do you do annual billing if we take twelve seats?”Vance Refrigeration, arrived through the pricing form

ReplyMove it onSnoozeDismiss

Send Michael the twelve-seat quoteAct now3 days late

Jim has held this since Tuesday.

Move the dateMark it doneSnoozeDismiss

Product snippets: Missing field “aggregateRating”Act now1.2k clicks at stake

Reported as an error on the template every product page renders.The 12 pages

Draft a fixFile as issueSnoozeDismiss

athlead.com/pricing failed 14 probes in a rowAct now38 min down

First failure at 02:14. Every other page on the host answers.

File as issueMake it a taskSnoozeDismiss

Instagram has published nothing for 23 daysWorth a look23 days quiet

The three posts before the gap averaged 4,100 views each.

Make it a taskPin to the boardSnoozeDismiss

Bob Vance is waiting on a first replyAct now2 days waiting

“Do you do annual billing if we take twelve seats?”Vance Refrigeration, arrived through the pricing form

ReplyMove it onSnoozeDismiss

Send Michael the twelve-seat quoteAct now3 days late

Jim has held this since Tuesday.

Move the dateMark it doneSnoozeDismiss

Product snippets: Missing field “aggregateRating”Act now1.2k clicks at stake

Reported as an error on the template every product page renders.The 12 pages

Draft a fixFile as issueSnoozeDismiss

athlead.com/pricing failed 14 probes in a rowAct now38 min down

First failure at 02:14. Every other page on the host answers.

File as issueMake it a taskSnoozeDismiss

Instagram has published nothing for 23 daysWorth a look23 days quiet

The three posts before the gap averaged 4,100 views each.

Make it a taskPin to the boardSnoozeDismiss

Every ending here writes to the board, the record or the repository.

One list

Six 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 still waiting on a reply, and follow-ups somebody promised and missed. Each card links to the contact and what they're worth.
Deals
Deals untouched for a month, and companies your contacts write from that you could add as accounts.
Work
Overdue tasks and who's holding them. Work due later in the week stays off the list until it's actually late.
SEO
A weekly crawl checked against Search Console: broken markup, pages that dropped out of the index, and queries that rank without clicks.
Social
Accounts that have gone quiet, and recent posts that did well enough to be worth building on.
Uptime
Endpoints that stopped answering, and the integrations that quietly stopped collecting last Tuesday.

6

Systems swept into one list

18

Endings a card can be given

Seats, so the whole team triages

Endings

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.

Michael Scott asked about the migration windowAct now1 day waiting

“Could you take us across in the first week of May?”Dunder Mifflin, Scranton, lifetime value $4,320

ReplyMove it onHand overSnoozeDismiss

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.

One card proposes one endingThe rest sit behind the chevron

Taking the ending is what empties the list. Filing an issue puts it on the board and mirrors it to GitHub, handing a person over gives them an owner in the CRM, and moving a date re-arms the Slack nudge that chases it. Nothing here writes a second copy of a decision your other tools already hold.

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, plus the unclaimed
Your own properties, contacts and tasks, plus anything still unclaimed, which keeps unowned work visible to everyone.
Your department, remembered
Sales sees sales and hiring sees hiring. Viably remembers your pick for each workspace and opens the inbox on that list.
Counts that match the list
The number beside each queue is exactly how many items you'll see when you click it, in the status you're already viewing.

Everything14

Mine5

People4

Work2

SEO6

Social1

Uptime1

Status

Needs a decision14

Good to know4

Sleeping3

Dismissed28

Where things went41

Holding the line

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 saved with the item. Dismissed items keep their own view, and you can restore any of them later.
Snooze until the number moves
A snoozed item comes back when the traffic, revenue or wait behind it grows by half. Until then, it stays out of your queue.
Fixes get verified
Marking a defect fixed holds it for two weeks, then checks it against the next crawl. If the defect is still there, it returns to the inbox.
Where things went
Every item that became an issue, task, pin or pull request links to where it ended up, giving you a record of what each week of triage 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.

Add Viably to Slack See what Via does

#ops — Slack

Today

ViaApp10:42 AM

📥athlead.com/pricing failed 14 probes in a row

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

File as issueOpen the inbox

OM

Oscar10:42 AM

That's the cache rule I changed last night. Taking it.

ViaApp10:42 AM

🐛Issue #241 created

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.app

14 days

Viably+ trial.

Seats on every plan

$7

per day, billed annually

3,000

Events each month

FAQ

Questions about the Team Inbox

What is the Team Inbox?

One queue for everything your workspace has found that needs a decision from a person. Viably sweeps your site, your contacts, your task board, your social accounts and your uptime probes, then puts what it found in a single list with the ending each card is actually asking for. Taking that ending moves the item out of the inbox and into the surface that owns it.

Where do the items come from?

From systems you have already connected. Search Console and the weekly crawl produce the site findings, the contacts queues produce the people waiting on a reply, the task board produces the work that ran past its date, and the social and uptime powers produce the accounts and endpoints that stopped working. Switch a power off and its items stop appearing, because nothing is copied anywhere.

Is this another database my team has to maintain?

No. The inbox holds no items of its own. Every card is derived on read from data the workspace already has, and the only rows Viably writes are your decisions: dismissed, snoozed, or filed somewhere with a link to where it went. That is why a dismissal survives the set of pages or people behind it changing.

What happens when I dismiss something?

It leaves the queue and keeps its reason, and you can put it back at any time from the Dismissed view. One reason behaves differently: saying a defect is fixed is a claim about the next crawl rather than a decision to live with something, so Viably holds it for fourteen days and brings it back if the crawl still reports it.

What does snoozing do?

It sets a threshold rather than a date. The item sleeps until the number behind it grows by half, however long that takes, so a search phrase worth eighty clicks comes back at a hundred and twenty and never on a Tuesday for no reason.

Can two people work the same inbox?

Yes, and most teams do. Pick a queue once and Viably remembers it, so your designer opens on the site findings and your sales lead opens on the people waiting. Mine narrows to what you own plus everything unclaimed, and every queue carries its own count so nobody has to guess where the work is.

Do I need Slack for this?

No. The inbox, the endings and the archive all run in the browser. Teams already in Slack get two extra things: any card can be posted into a channel with a note, and the tasks, issues and pull requests that come out of triage land in the channels those powers already write to.

Can Viably fix things itself?

For the findings where it can name the file and the change, yes. It writes the change, opens a pull request, and shows it to you for approval in Slack before anything reaches your repository. The card stays in the inbox until the pull request merges, because a draft is a request rather than a fix.

How much does it cost?

The Free plan is always available and carries the full feature set. Viably+ is seven dollars a day billed annually with unlimited seats, and it opens with a fourteen-day trial that bills nothing until the fortnight is up.