Everything that needs a decision, in one list your team can empty
/inbox gathers all of it into one list, leads each card with a suggested ending, and empties as your team works through it.- Trigger
- Inbox
- Lands in
- Dashboard, with anything you file landing in Slack
- Setup
- 1 min
- Needs
- Nothing else
Sent from the inbox: the pricing page has failed 14 probes
Shared for a second opinion, still waiting on a decision
- Down
- 38 minutes
- First failure
- 02:14
- Other pages
- Answering
A shared card stays in the queue until someone gives it an ending.
What lands in the inbox
Viably reads each queue from a power your workspace already runs, so the inbox fills as soon as those are connected. You never add items by hand.
Every card proposes one ending
The list groups cards by kind. Each card shows the first ending for its kind as a button, with the rest behind the chevron beside it.
Someone got in touch and no one has replied or claimed them. Replying takes them off this list. Endings, best first: Reply, Move it on, Hand over, Set a date, Move to another stream, Make it a task, Send to Slack, Pin to the board.
A follow-up your team accepted and then missed. Reply now, or move it to a new date. Endings, best first: Reply, Set a date, Move it on, Hand over, Move to another stream, Make it a task, Send to Slack, Pin to the board.
Deals someone is working where nothing has happened for a month: no message, no note, no stage move. Close them, or leave a note on where they stand and they come back only if another month goes by. Endings, best first: Still working it, Mark won, Mark lost, Reply, Send to Slack. This kind cannot be dismissed.
Tasks your team took on that are now past their due date. Move the date, finish them or drop them. Each choice updates the task itself. Endings, best first: Move the date, Mark it done, Hand it to someone, Drop it, Send to Slack. This kind cannot be dismissed.
Viably can no longer read an account, usually because its permission expired or was replaced. Viably collects nothing until someone reconnects it, and the platforms don't backfill the missing days. Endings, best first: Make it a task, Send to Slack, Pin to the board. This kind cannot be dismissed.
Something you run answers wrong: a dead link, a redirect chain, markup Google rejects, an endpoint that is down. If Viably is authorized on the GitHub repository, it can create a pull request to fix the issue automatically. Endings, best first: Draft a fix, File as issue, Make it a task, Pin to the board, Send to Slack.
Pages earning less than they should, searches where your result isn't getting clicks, and accounts that have stopped publishing. Each one calls for writing or building something new. Endings, best first: Make it a task, Pin to the board, File as issue, Send to Slack.
Company domains that several of your contacts write from and that are not accounts yet. Creating the account links the domain, and everyone who writes from it, now or later, joins that company. Endings, best first: Create account, Send to Slack.
Updates that need no action. Share them with the team or dismiss them. Endings, best first: Pin to the board, Make it a task, Send to Slack, File as issue.
Two axes: which queue, and what state
The rail narrows the list on a single axis: everything, what is yours, one system, or one department. Viably remembers your pick, so a bare link to /inbox opens on the list you work.
Mine means the properties, contacts and tasks you own, plus everything no one has claimed yet. The figure beside each entry counts the rows you would get if you clicked it, within the state you are already in. The second axis is the state of a decision:
Dismiss, snooze and undo
Viably saves every decision with the reason given, and you can undo any of them from the archive.
The reasons offered depend on what you are declining. A broken page can be intentional, someone else's, or not worth the work. A contact can be handled elsewhere or not a fit, in your own stream's word for a relationship that ended. A search phrase can bring the wrong traffic.
Snoozing stores a threshold instead of a date. The item stays hidden until the clicks, the money or the wait behind it grows by 50%.
Dismissing a defect as fixed hides it for 14 days, then Viably checks what the crawl still reports. If the fix never shipped or fixed the wrong thing, the item comes back.
Dismissed items keep their reason and you can restore them at any time. Where things went lists everything that became an issue, a task, a pin or a pull request, with a link to where it landed.
Only your decisions. Viably builds the cards on every read from the crawl, the contacts queues, the task board, the social accounts and the uptime probes. It stores only whether you dismissed, snoozed or filed something, and where it went.
There are two reasons. A snoozed item returns once the number behind it grows by half. And if you dismissed a defect as already fixed, Viably checks the crawl two weeks later and brings the item back if the crawl still reports it.
Yes. Cards that share an explanation are grouped as a run under one heading, and you can decide on the whole run at once. The decision also covers cards that join the run later.
Its items stop appearing. The buttons on a card also depend on the powers your workspace has: a card only offers to open a pull request in a repository Viably can reach.
Yes. The inbox belongs to the workspace, and every decision records who took it and when. The queue you pick is personal and remembered per browser.
You decide in the dashboard and the results land in Slack. You can post any card into a channel with a note when someone else should look at it, and the tasks, issues, pins and pull requests that come out of triage arrive in the channels those powers already post to.
Open /inbox to see what your workspace has already collected. The inbox is on the free plan and needs no setup.