The tools you have, connected once.

Rivilo does not replace your mailbox or your chat. It reads the one you connect, and puts the work where your team already talks.

Google Workspace

Gmail requests become cards, replies are drafted and sent through your own Gmail, Calendar and Sheets read-only. The most complete setup today.

Microsoft 365 Beta

Work-account sign-in, Outlook mailbox read, and a message in your Teams channel per card. Outlook and Teams are in beta.

Slack

Mention @Rivilo in a channel: it reads the thread, answers from your boards, creates or updates the card and drafts the reply for approval.

Fireflies

Every recorded client call lands on the right project: summary, decisions and a few proposed cards you approve.

Coming soon

Proton

Connect Proton Mail and Proton Calendar, so client requests become cards the same way they do from Gmail.

Coming soon

Canva

Use your Canva designs in the documents and decks Rivilo writes.

A briefing in Slack or Teams, shaped the way you want it.

Every automation that posts to a channel shows you the message first. Say what should change and the preview changes with it. Click a suggestion, or switch to Teams.

Notification preview

Ticket briefing in #support

Rivilo APP 09:52

Site down after the DNS change

Site down after the DNS change · Studio Mara: Annemarie de Vries

Annemarie reports the shop has been unreachable since 09:40, after yesterday's DNS change at the hosting party. She mentions lost orders.

"we changed the DNS at the hosting party yesterday, since this morning nothing loads"

Urgency: high. Live site down, client mentions lost orders.

Recommendation: pick this up now. Check the DNS records against the hosting party's, then confirm to Annemarie within the hour.

Draft reply:

Hi Annemarie,
We see it and are on it. First check is the DNS records at the hosting party; you will hear from us within the hour.
Robbin

Automation · Ticket briefing in #support

Preview based on the card "Site down after the DNS change". Fictional client, real briefing structure.

Rivilo
I post a briefing in #support for every new ticket in New: summary, urgency, recommendation and a draft reply. What should change?
What should change about this notification?

Our values

  1. Privacy by design

    Your work is stored in the EU and never used to train anyone's model. Everything Rivilo remembers about a client is visible, editable and deletable, by you.

  2. Value human work

    The judgement, the taste and the relationship with the client are the job. Those stay with the people who were hired to do them.

  3. Keep the user in control

    Every reply, document and invoice stays a draft until a person approves it. Nothing goes to a client on its own.

  4. Automate the distractions

    Sorting, chasing, formatting, remembering: the groundwork that has to happen and that nobody was hired for. That is what we automate, so the rest of the day is free for what actually matters.

Connect one mailbox. Get instant clarity.

Try Rivilo