Every tool. One teammate.

Ray works in the tools your team already has and adds the ones teams ask for. It just does what it can undo, and asks before anything it can’t.

Add to Slack for free Browse every integration

By adding Ray, you accept the Terms and Privacy Policy.

Find the tool your team lives in.

Open any of them to see what Ray reads, what it does at once, what waits for your approval, and what it will not touch. The ones Ray does not connect to yet are here too, and asking for one takes a click.

Not seeing the one your team lives in? We add the tools teams ask for.

Connect it once. Then just ask.

There is no workflow to build and nothing to maintain when the work changes.

01
Connect it once
One click, right where you asked. Ray posts a connect card, you authorise with your own account, and the work you asked for picks up where it left off.
02
Ask in plain words
In the conversation you were already having. Nothing to build, no trigger to map, no tab to open.
03
It lands, with an Undo
Reading runs on its own. Everyday changes land at once with an Undo, and anything that sends, spends or can't be taken back waits for your yes with the exact content in front of you.

and the rest

Megan

@Ray the checkout bug is back. File it, and tell Dana it is being looked at.

Create Linear issue

Title: Checkout fails on saved cards
Priority: Urgent

Undo

Control

Nothing gets sent, spent or deleted for good until you say so.

Reading changes nothing, so Ray gets on with it. It can put back a new ticket or an updated record, so it does those too, with an Undo on its reply that anyone on the team can press until the end of the next working day.

The moment it wants to send, spend or do anything it can’t put back, it stops in the thread and shows you the exact thing it is about to do. Say yes and it happens. Decline and nothing did.

No setting turns that off. And the things nobody should be able to do by accident, like wiping your data or moving money out, were left off Ray’s list when we built it, so they were never its call to make.

How Ray handles your data

What Ray posts before it sends

I will email Dana the summary you asked for.

Send email

To: dana@northwind.co
Subject: Checkout bug, where it stands

Hi Dana, the saved-card failure is filed as FLD-212 and Dan is on it. I will let you know when it ships.

SendDecline

The real card, with the real body. You approve the words that go out, not a description of them.

Who Ray acts as

Ray acts as the person asking, never as a shared login.

Most tools connect once, as whoever set them up. Everything after that is filed by a service account carrying that person’s permissions, and it keeps working long after they have gone.

Everyone connects their own account instead. Reads, and the changes Ray can undo, run as the person who asked. A write that waits for a yes runs as the person who approved it.

Reach: Ray sees what you can see in a tool, and nothing you cannot.
History: Your tools record the people involved, so the trail is still worth reading a month later.
Leaving: Access goes when the person does. There is no shared key left behind for someone to remember to turn off.

FLD-212 Saved cards fail at checkoutFiled by Dan Kowalski

Dan Kowalski asked in #payments2:11pm
Ray read the error trail as Dan2:12pm
Dan Kowalski created this issue2:12pm
Jess Moreno asked Ray to start it2:14pm
Jess Moreno moved it to In Progress2:14pm

The trail your tracker writes on its own. Two real people, and a teammate that acted as each of them in turn.

One ask can cross four tools.

Ray is one teammate with one memory, not a folder of separate connectors. So a single sentence can end in several places.

Megan

@Ray the checkout bug is back. File it, tell Dana it is being looked at, and put it on Thursday’s agenda.

LinearIssue filed, urgent
GmailReply drafted to Dana
Google CalendarAdded to Thursday
SentryError trail read for the description

What Ray takes off your plate.

The same teammate, pointed at whatever your week is actually made of.

Engineering

Bugs get filed properly, and statuses stop needing a chase.

Turns a thread into a written issue with real acceptance criteria
Reads the error trail before it writes the description
Answers where a ticket stands without anyone opening the tracker

Marketing and growth

The numbers come to you, and the drafts are waiting.

Posts the weekly campaign numbers into the channel that cares
Drafts the email and the ad copy, and never sends either alone
Builds a campaign brief from what actually performed

Operations and finance

The reconciling reads happen without a CSV export.

Reads invoices, payments and the ledger to answer a question
Chases the document nobody has signed yet
Posts the morning digest before anyone asks for it

Founders

One place to ask, across everything the company runs on.

Answers across tools, from what it did and what it can read
Remembers the decision your team made three weeks ago
Keeps the standup and the weekly recap running on their own

Every integration, A to Z

Put Ray to work in the tools you already have.

Free to start, no card, and nothing it can’t undo happens without your yes. Connect the first tool in about a minute.

Add to Slack for free