Whether you're managing three servers or three hundred, Dibs won't restrict the number of queues you have running.

Let your whole organization use Dibs without worrying about surprise billing.

Ten queues in one Slack channel, or a hundred queues in a hundred channels, it's all good.

For those times when someone has gone on holiday or is unavailable, bump someone from the queue and let the next person have their go.

If you know you'll only need to hold onto something for a set amount of time, Dibs automatic timers allows you to specify the amount of time that you're claiming the thing for, eg:

/dibs on server1 for 45 min

No more spelling errors, eg: this will work:

/dibs on staging

but this won't work:

/dibs on stageing

Help other team members understand more, by stating a short description.

Useful also for attaching bug/issue numbers to things.

If typing out commands into Slack is getting a bit boring, this enhancement adds in-app Slack buttons with a dropdown menu to allow you to quickly use Dibs.

This makes certain queues have a bit more noise, so that as new members are added to a queue, notifications are sent to the queue leader.

Better than drawing names from a hat, use a random queue to decide who's next. Useful for sharing the load with office chores.

Originally written to allow semi-anonymous queues, this feature allows you to keep the guest list a secret.

Run commands faster by avoiding typing out the whole queue name, eg:

/dibs on sta

(if the conch/queue name was "staging")

Fire off interesting web requests when the queue moves.

This feature allows you to register web requests that should occur when new people are added to the queue or when the queue changes leaders.

There's even a special Webhook Builder to help you get going.

Allow multiple people to hold the conch at the same time.

This can be useful for allowing groups of people to claim a resource simultaneously, whilst others are queued in line.

Eg help your customer support team coordinate lunch break groups without leaving the phones un-manned /dibs on lunch

Use Dibs directly in your automation and CI/CD pipelines by setting up per-queue API authentication tokens.

This lets you manipulate conches/queues directly via API calls.

Keep separate collections of queues in separate Slack/Discord channels.

Eg: one channel for deploys, one channel for testing/QA.

Great for roster duty or taking turns with after hours support or any other turn taking event that repeats day after day.

People will get automatically placed onto the end of the queue over and over.

Make it mandatory to use timers on particular queues.

This prevents people forgetting to release the queue and forces people to consider how long they'll want to claim the thing.

Jump to the head of the queue. It's here if you need it, just in case.

Rename a queue without losing all the queue members that are waiting their turn.

For silencing the queue messages that Dibs sends to the Slack or Discord channel.

Can be applied to individual queues or all queues.

Dedicated (real human) support to instantly assist. Plus access to all the newest features and additions.