Fathom, without opening Fathom.
What the meeting decided, without watching it again.
- Free to start
- No card
- Reads only, nothing to approve
- Your own account, not a shared login
Ask in your own words.
Nothing to configure and no builder to open. Copy one of these into a thread, swap in your own Fathom details, and Ray takes it from there.
@Ray what did we agree in the Acme call?
@Ray what meetings did the team have with Northwind this month?
@Ray send me the summary from this morning's standup.
@Ray did anyone mention the renewal date on that call?
What Ray can and cannot do in Fathom
Reading is free, because reading changes nothing. Everything that writes waits for you. The rest is not on Ray’s list.
5 reads wired, and nothing that writes.
Runs on its own
What Ray reads in Fathom
- Meetings and who was on them
- Recording summaries and transcripts
Reading changes nothing, so Ray never stops to ask whether it may look something up.
No send, no spend
What Ray answers with
Ray reads Fathom and answers from it in the thread. Writing to Fathom is not switched on yet, so there is nothing here to approve.
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.
- Write anything back to Fathom
How Ray works with Fathom
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect Fathom
One click, right where you asked. Ray posts a connect card, you authorise Fathom 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
Ray answers where you asked
Ray only reads Fathom, so there is nothing here to approve. It looks up what it needs and replies in the thread.
Priya
@Ray the checkout bug is back. Take a look in Fathom, and tell Dana it is being looked at.
Ray
Checked Fathom. The spec was last edited on Tuesday and the open question about refunds is still unanswered.
Ray uses Fathom together with the rest of your tools.
One ask can read Fathom, 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 Fathom to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect Fathom and it can do the Fathom 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.
Every person on the team connects their own Fathom account, so Ray can only reach what that person can already reach, and the history in Fathom shows who actually asked.
Security and permissions
- You authorise Fathom on its own login screen. Your password never passes through Ray.
- 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.
- Disconnect Fathom in a message, or uninstall Ray and every connection it held is revoked.
Fathom and Ray, answered
The questions teams ask before they connect Fathom. Every answer is how this integration is built rather than a promise about it.
More calendars & scheduling integrations
Ray uses them together in a single run when a request spans more than one.
Put Ray to work in Fathom.
Free to start, no credit card, and it asks before it acts.