Add Ray, then give it something real.something real.something real.

Adding Ray takes one click from the install page. Slack asks you to pick a workspace and shows you the permissions Ray asks for. Approve it and Ray is in.

Nobody creates an account. There is no password to set and no seats to assign. Ray works with whoever talks to it.

Ray only sees channels it has been invited to. Type /invite @Ray in the channel where your team already works, or add it from the channel’s integrations menu.

When Ray joins, it reads what it missed and picks up any request that was aimed at it and is still worth doing. Old chatter stays old. It will not answer a question your team resolved last week.

You can also DM Ray. A DM is a normal working surface, not a settings panel.

Ask the way you would ask a teammate. Ray reads the channels it’s in and answers when something is meant for it, so you do not have to mention it every time.

Dan

@Ray can you file a bug for the checkout error Megan hit? Refunds are unaffected.

Ray

Filed ENG-231 in Linear.

Undo

Ray does the research first. It reads the thread, pulls in what it already knows about your team, and writes the ticket the way a good engineer would: a real problem statement, what was expected, what happened, and acceptance criteria you can check. Where it does not know something, it writes that down instead of guessing.

You do not set integrations up in advance. The first time a task needs a tool Ray has not been connected to, it posts a Connect button. One click, the tool’s own OAuth screen, and the request you already made finishes on its own.

• Ray asks for the narrowest access that lets it do the work you requested.
• Each person connects their own account. Tools with no per-person login connect once for the whole workspace.
• Disconnecting a tool in your provider's settings takes effect immediately, and Ray says so honestly the next time it needs that tool.

The current list lives on the home page. Every integration is on every plan, including the free one. Tools Ray does not connect to can still report to it: automation alerts covers Zapier, Make and n8n.

Ray just does what it can undo, and asks before anything it can’t. Creating or updating a ticket, adding a contact, making a page: Ray does it at once, and its reply carries an Undo. Anyone on the team can press it until the end of the next working day. It puts back what Ray did and leaves alone anything a teammate changed since. Undo can’t recall a notification or an email the tool already sent.

Drafts stay drafts and send nothing. Small team-only touches, like an internal comment, a tag or a label, have no Undo button, so remove those in the tool itself.

Anything that sends to people, moves money, deletes with no restore or can’t be put back stops and waits for you. Ray shows what it is about to do, in plain language, with the actual content included: the recipient and full body of an email, the amount of a refund, the exact fields of an update. The card’s button names the action, like Send or Refund, or says Approve, beside Decline.

Ray

I’ll email Dana the revised timeline and copy Dan.

Send email

To dana@acme.com

Subject Revised timeline for the March pilot

SendDecline

Reading is free. Ray browses your tracker, reads a thread or searches the web without asking. Decline and nothing happens, and Ray tells you plainly that nothing was sent.

When a schedule, a watch or a chase runs with nobody present and Ray has read outside content, like an email, a web page or a file, every change in your connected tools except a draft waits for a person’s yes, even one Ray could undo. What an email asks for is never treated as an instruction.

There is no setting that turns this off, for anyone, on any plan. Asking Ray to skip it does not work either. More on how that is built.

Ray keeps what your team tells it, so you stop repeating yourself. Preferences, who owns what, which tracker a project lives in.

• Said in a public channel, kept for the workspace. Said in a DM or a private channel, kept only there, unless an admin asks Ray to keep it for the whole team.
• Ask what do you remember about the pilot? and Ray shows you, with where each fact came from.
• Say forget that and it is retired. Corrections supersede the old version rather than piling up beside it.
• An admin can switch durable memory off entirely, or purge everything. Purge is permanent and asks for confirmation in the channel.

Memory holds knowledge, never instructions. Something Ray remembered last month cannot redirect a task you gave it today.

Ask for recurring work in plain language and Ray sets it up. It uses the timezone of the person the schedule is for, so “9am Zach’s time” means what it says.

Jess

@Ray post a standup digest here every weekday at 9

Ray

Done. Weekdays at 9:00 in this channel. Say the word if you want it moved or stopped.

“Remind me in two hours” works the same way. Ask what is scheduled and Ray lists it. Ask it to stop and it stops. To change one, cancel it and set it again.

The free plan runs 1 scheduled digest. Paid plans have no limit on schedules.

A task is one request Ray delivered. Ask a question and get an answer, that is a task. File a ticket, chase four people for status, post a digest, each is one task no matter how many steps it took underneath.

• Every new workspace gets 50 free tasks that never expire, on top of 25 a month on the free plan.
• Work that fails, loops or gets declined never counts. You are not billed for Ray getting it wrong.
• A message Ray decides not to answer is not a task either.
• A change you undo still counts, since Ray did the work.
• When you run out, Ray tells you in the channel and offers the upgrade. Pricing is flat by team size and never metered. See the plans.

Worth knowing before you rely on it. Ray tells you these things itself when they come up, but here they are in one place.

• It cannot see channels it has not been invited to, and it will say so rather than guess at what is in them.
• It runs in Slack today.
• It will not claim a job is done when it is not. If something is beyond its tools, it says that instead of improvising.
• It never asks for your password. Most tools connect through their own OAuth screen, and the rest take one workspace key, typed on Ray's own page rather than in Slack.