Plain, without opening Plain.
The thread answered from chat, with the customer's history attached.
- Free to start
- No card
- Every write waits for you
- One key for the workspace
Ask in your own words.
Nothing to configure and no builder to open. Copy one of these into a thread, swap in your own Plain details, and Ray takes it from there.
@Ray what is the oldest unanswered thread in Plain?
@Ray reply to Dana's thread saying the fix ships Thursday.
@Ray which tier is Northwind on?
@Ray open a thread for the bug Sam reported.
What Ray can and cannot do in Plain
Reading is free, because reading changes nothing. Everything that writes waits for you. The rest is not on Ray’s list.
11 reads wired, 5 actions that wait for a human.
Runs on its own
What Ray reads in Plain
- Threads by status or priority, and one thread in full with its customer and labels
- Customers by id or email, the companies behind them, and the tier each one sits on
- The issue-tracker links already attached to a customer's threads
- Customer groups, and who on your team a thread is assigned to
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What waits for your approval
- Sending a message to the customer in a thread
- Opening a thread, renaming one, and assigning it as it is created
- Creating or updating a customer, and creating or updating a company
Ray posts a card showing exactly what it is about to do. Nothing happens until someone clicks approve, and no setting turns that off.
Not on the list
Things Ray is never handed
These are left out during curation, so they are not something Ray could do and decides against. They are not in front of it at all.
- Run an arbitrary GraphQL mutation, which would reach every refusal on this list
- Delete a customer or a team member
- Add or remove a customer from a group, because groups carry access
Exactly what Ray will ask you to approve.
Not a category of permission. These are the Plain actions Ray can take, each one stopping in the thread with the real content before it happens.
- Send a message to the customer in Plain
- Open a Plain thread
- Rename a Plain thread
- Create or update a Plain customer
- Create or update a Plain company
Send a message to the customer in Plain
Showing Thread id and Text content, each carrying the exact content that will land.
How Ray works with Plain
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect Plain
Plain has no per-person login, so it takes one workspace key. Ray posts a connect card, you paste the key on Ray's own page rather than in Slack, and it covers the whole team from then on.
- 02
Ask in plain words
In the conversation you were already having. Nothing to build, no trigger to map, no tab to open.
- 03
Approve, and it lands
Reading runs on its own. Anything that creates, sends or spends stops first and shows you the exact content.
Priya
@Ray the checkout bug is back. Take a look in Plain, and tell Dana it is being looked at.
Send a message to the customer in Plain
- Waiting on
- your approval
Ray uses Plain together with the rest of your tools.
One ask can read Plain, cross-reference what is in these, and land the finished result back in the thread. Not four connectors taking turns, one teammate with one memory.
What does connecting Plain to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect Plain and it can do the Plain part of a request without anyone leaving the conversation: read what it needs, draft the change, and post it for approval before anything is written.
It is not a workflow builder. There is no trigger to configure and no automation to repair when your process shifts. You describe the outcome in the thread and Ray picks the actions, including actions in your other connected tools when the request spans more than one.
Plain has no per-person login, so it connects once with a single workspace key and covers the whole team. Ray reaches whatever that key reaches, which is worth scoping the way you want everyone to see Plain. Every write still stops for approval first.
Security and permissions
- You paste the Plain key on Ray’s own page, never in Slack. It goes straight to the connection and never reaches the model.
- Writes are gated in the execution path, not by a prompt. There is no setting that grants blanket approval.
- Each workspace is isolated at the database level, and that isolation is tested by trying to break it.
- An admin, or whoever connected it, can disconnect Plain in a message. Uninstall Ray and every connection it held is revoked.
Plain and Ray, answered
The questions teams ask before they connect Plain. Every answer is how this integration is built rather than a promise about it.
More support & helpdesk integrations
Ray uses them together in a single run when a request spans more than one.
Put Ray to work in Plain.
Free to start, no credit card, and it asks before it acts.