Reply.io, without opening Reply.io.
Who replied, who went quiet, and who goes into the sequence next.
- 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 Reply.io details, and Ray takes it from there.
@Ray who replied to the founders sequence this week?
@Ray pause the outbound sequence, we are rewriting the pitch.
@Ray add these five contacts to the Q4 sequence.
@Ray mark Dana as replied so she stops getting emails.
What Ray can and cannot do in Reply.io
Reading is free, because reading changes nothing. Everything that writes waits for you. The rest is not on Ray’s list.
24 reads wired, 18 actions that wait for a human.
Runs on its own
What Ray reads in Reply.io
- Contacts and companies by search or filter, with the full activity trail against each
- Sequences, their steps and step variants, their stats, and two compared side by side
- The shared inbox, and the tasks assigned to whoever is asking
- Which mailboxes can send, their daily limits, and which sequences they are running
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What waits for your approval
- Putting contacts into a sequence, and starting or pausing the sequence itself
- Creating and updating a contact or a company, and changing who owns one
- Marking people replied or opted out, and blacklisting a contact or a domain
- Replying from the shared inbox, filing a thread, and creating or completing a task
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.
- Configure the product: sending schedules, triggers, custom fields or workspace settings
- Connect, disconnect or edit a mailbox, a LinkedIn account or another integration
- Touch Jason, the built-in AI SDR, or approve the messages it drafts on your behalf
Exactly what Ray will ask you to approve.
Not a category of permission. These are the Reply.io actions Ray can take, each one stopping in the thread with the real content before it happens.
- Reply add contact to sequence
- Add a contact to Reply
- Update a Reply contact
- Add a company to Reply
- Update a Reply company
- Start a Reply sequence
- Pause a Reply sequence
- Change a contact's status in a Reply sequence
- Reply mark contacts as replied
- Reply mark contacts as opted out
Add a contact to Reply
Showing Email, First name, Notes, Company, Title, Linked in url and Phone, each carrying the exact content that will land.
How Ray works with Reply.io
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect Reply.io
Reply.io 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 Reply.io, and tell Dana it is being looked at.
Reply add contact to sequence
- Waiting on
- your approval
Ray uses Reply.io together with the rest of your tools.
One ask can read Reply.io, 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 Reply.io to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect Reply.io and it can do the Reply.io 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.
Reply.io 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 Reply.io. Every write still stops for approval first.
Security and permissions
- You paste the Reply.io 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 Reply.io in a message. Uninstall Ray and every connection it held is revoked.
Reply.io and Ray, answered
The questions teams ask before they connect Reply.io. Every answer is how this integration is built rather than a promise about it.
More crm & sales integrations
Ray uses them together in a single run when a request spans more than one.
Put Ray to work in Reply.io.
Free to start, no credit card, and it asks before it acts.