Revvly
Docs
Guide

Get notified: the bell, push and Slack.

See what produces a notification, choose what reaches you, install the app for push, and connect Slack or ClickUp Chat so OKR check-ins find people where they work. Personal settings are open to everyone; connecting Slack and reading the delivery log are for admins and owners. The OKR messages themselves are described in the OKR guide.

01Four places Revvly can reach you

The bell at the top of the dashboard is in-app and is on for every workspace. Push notifications reach a phone or desktop when the app is closed. Slack, or ClickUp Chat in its place, carries the OKR messages that ask you to answer something. The delivery log is an admin view of what was sent through those chat channels. Each is set up in a different place, and each is described below.

02The bell

The bell lists what needs your attention, newest first, with an unread count that refreshes about once a minute. Select an item to open the thing it is about. Mark all read clears the count. The panel loads twenty items and fetches older ones as you scroll to the bottom. Items are kept for 90 days and then removed, so the bell is not an archive. If your workspace has Support, ticket notifications appear in the same list.

Where
  1. Bell icon in the header

03What puts something in the bell

Form submissions go to the people the form notifies, or to its creator when no step names anyone; a form whose steps fail goes to its creator. OKRs tell an owner when an objective or Key Result is assigned to them, when someone else changes the target of a Key Result they own, and when scoring opens. A reply from a client to an email you sent in the last 30 days reaches the mailbox owner, and an email that could not be sent reaches the sender. A Calendly booking reaches the host when their address belongs to a teammate, otherwise the workspace admins and owners. An invoice that passes its due date unpaid reaches the workspace admins and owners. You are never notified of your own actions, and only active members are notified, so someone whose invitation is still pending gets nothing until they have signed in. OKR items are written only for workspaces that have turned OKRs on.

From event to bell item
  1. Something happens
    A form is submitted, an objective assigned, an invoice goes overdue.
  2. Your own actions dropped
    The person who acted is never notified.
  3. Active members only
    Pending invitations get nothing yet.
  4. Muted kinds skipped
    Nothing is written for a kind someone turned off.
  5. Item appears in the bell
    Kept for 90 days.
Your own actions, inactive members and muted kinds never produce an item.

04Choose which kinds you see

Each person decides for themselves. Under Notification bell there is one switch per kind, grouped by source: new form submission, form steps failed, objective assigned to you, Key Result assigned to you, target changed, scoring opened, new email from a client, email could not be sent, daily inbox digest, meeting booked, invoice overdue, check-ins paused, check-in report not posted, Drive client folders paused, invoice import ready for review, and reminder due. A switch only shows when it can fire for you: the inbox digest needs the Work Inbox, and Drive client folders paused is for admins of a workspace with client folders. Each switch saves as you flip it. A muted kind is not written for you at all, so it does not sit unread. Everything starts on. Several unread emails from one client fold into one row, such as 4 new emails from Acme, and count as one unread. Invoice overdue, the two check-in alerts and Drive client folders paused are only ever sent to admins. An invoice import ready for review goes to the person who started it, or to admins for an import from client folders.

Where
  1. My Account Settings
  2. Notification bell

My Account Settings is in the menu on your name at the bottom of the sidebar.

05Install Revvly and turn on push

Push is set per device. On a phone, Revvly offers to add itself to your home screen, once a day until it is installed. On Android the install button is one tap; on iPhone it shows the Share then Add to Home Screen steps. On iPhone push only works from the installed app, so install it first. Then switch on Enable push notifications on this device and allow the browser prompt. If the browser has blocked notifications for the site, the card says so and you re-enable them in the browser settings. If the card says push is not enabled on the server, your Revvly deployment has not been set up for it and an administrator needs to act.

Where
  1. My Account Settings
  2. Push notifications

On a phone, Add Revvly to your home screen on the same card opens the install steps at any time.

06What push tells you

The billing and usage alerts go to every device in the workspace that has push turned on, not only to admins: subscription renewed, customer churned, invoice paid, invoice overdue, unverified metered usage (a period that closed with no reported quantity from an API source), and a subscription that signed but has not gone live past its activation window. Tapping one opens the subscription, invoice or the task list. A shared document opened is different: it goes only to the person who sent the link, for the first few people who open it, and a mail scanner visiting the link does not count. There is no per-event switch for these pushes today; the only control is the device switch.

07Email opens and document views

When an email you sent is opened, that shows on the email itself with the time of each open, and when someone opens a library document you sent as a link it shows as Document viewed. A browser push for the document being opened is the only alert of this kind. Email opens on their own do not produce a bell item or a push. Sending a document as a link is described in the Document library guide.

08Connect Slack

Slack is connected once for the whole workspace by an admin or owner, through Slack’s own install screen. Slack may ask a Slack administrator to approve the install. The page shows the state in words: Connected, Degraded, Needs reconnecting (Slack no longer accepts the token, so nothing is delivered until you reconnect), App removed (reinstalling restores delivery and keeps the people links) or Not connected. A setup list tracks the three steps that must all be done before anyone is prompted: workspace connected, people linked to Slack accounts, announcement channel chosen. A Slack workspace can be connected to only one Revvly account at a time.

Where
  1. Org Settings
  2. Integrations
  3. Slack
  4. Connect Slack

Admins and owners. Re-check refreshes the state. Disconnect asks you to confirm.

09Link people to their Slack accounts

A person who is not linked receives nothing in Slack. Manage people lists suggested links matched on email address, and nothing is linked until you choose Confirm. Anyone left over can be linked by hand from a picker, and a link can be removed. A person who is in Slack but has no Revvly account is listed separately and can be invited. Key Results whose owner is not linked to Slack carry an unreachable badge in the OKR screens, so you can see who will not be asked.

Where
  1. Org Settings
  2. Integrations
  3. Slack
  4. Manage people

10Invite people from Slack

Invite from Slack lists people in the Slack workspace who have no Revvly account and sends each a direct message with a single-use join link. Bots, deactivated accounts and accounts from other Slack workspaces are left out, and so are guests unless you tick Include guests; a line under the list says how many were left out. Before sending you see the most the invitations could cost if everyone accepts, because a seat is taken only when someone accepts. Only an owner can send; an admin chooses Request approval and the owners are told, then an owner approves from Pending invites. If the workspace has no owner, admins can send directly. A link lasts 14 days. Resend gives a fresh link and invalidates the old one, and a reminder goes out once, a week in.

Where
  1. Org Settings
  2. Integrations
  3. Slack
  4. Invite from Slack

Admins and owners can open it. Pending invites shows invitations and approval requests.

11OKR check-ins over Slack

With OKRs on, a linked person gets a weekly direct message listing the Key Results owed a check-in, with a Start check-in button, and replies in the chat with a value and a confidence. The same channel carries the weekly digest, scoring prompts, assignment and target-change messages and the cycle announcements to the channel you pick. Pick the announcement channel in the Slack card; the bot can join a public channel itself. You can also type /revvly checkin, /revvly score, /revvly conclude (record the verdict on a hypothesis test you own), /revvly status followed by a Key Result, and /revvly mine in Slack, and /revvly with anything else shows the help. A hypothesis test that ends in two days, or has run past its end, sends its owner one message with a Conclude here button that records the verdict in the chat. Objectives and Key Results are created in Revvly, not in Slack. The cadence, reminders and scoring flow are in the OKR guide. A separate Check-ins page appears in Settings for workspaces that have it, but it only stores definitions today and sends nothing.

Where
  1. Org Settings
  2. Integrations
  3. Slack
  4. Announcement channel

12ClickUp Chat instead of Slack

If your team works in ClickUp, an admin can send the OKR messages through ClickUp Chat. It is one channel for the whole workspace: while Use ClickUp Chat for OKR messages is on, every OKR message goes to ClickUp instead of Slack, and Slack stays connected and is used again when you switch it off. People are linked to their ClickUp accounts first, and someone with no link gets nothing through ClickUp. Replies are read about once a minute, so an answer can take a moment to register. Messages are sent as the ClickUp user who connected, unless you reconnect with a dedicated ClickUp user.

Where
  1. Org Settings
  2. Integrations
  3. ClickUp
  4. Check-ins in ClickUp Chat

Appears once ClickUp is connected.

13Check that messages are arriving

Notifications shows the last seven days: people reached, messages sent, nobody linked, silenced, held back by a rule, and failed. Zero people reached is the first sign of a broken connection or missing links. The same page sets the workspace check-in day and hour, whether team leads are copied on the weekly digest, and whether each concluded hypothesis test is posted to the announcement channel with its outcome and learning (off by default); each person can set their own day and time and choose which categories to silence on My Account Settings, and those apply in their own timezone. Delivery log lists every message the product tried to send through its chat channels, including the ones it deliberately skipped, with an outcome of Delivered, Waiting for its digest, Failed, Nobody linked, Silenced, Held back or Folded into a digest. Filter by outcome to find a missed prompt. The summary, changing the workspace defaults and the log are for admins and owners.

Where
  1. Org Settings
  2. Delivery log

Notifications is the tab beside it. See the OKR guide for what each OKR message does.