Salesforce, without opening Salesforce.
Ask the pipeline a question, then log the call or move the opportunity without leaving the thread.
- Free to start
- No card
- Nothing irreversible without your yes
- 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 Salesforce details, and Ray takes it from there.
@Ray which opportunities are closing this month, and what did we last hear?
@Ray log that call on the Acme opportunity and move it to negotiation.
@Ray create a lead for the person who just emailed us about pricing.
@Ray run the pipeline report and post the number in here every Monday.
What Ray can and cannot do in Salesforce
Reading is free, because reading changes nothing. Everyday changes Ray just makes, and anything that can't be taken back waits for your yes. The rest is not on Ray’s list.
27 reads wired, 13 actions Ray does at once, and 5 actions that wait for your yes.
Runs on its own
What Ray reads in Salesforce
- Accounts, contacts, leads, and opportunities
- Notes, tasks, campaigns, and the reports and dashboards your team already built
- Custom objects and the fields on them
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Just does it
Ray does these at once
- Add a contact, lead, or opportunity
- Update an account, contact, lead, or opportunity
- Add or update a note
- Link a contact to an account
- Create or update a task, or log a call against a record
Anything Ray can put back comes with an Undo button on its reply. In a schedule, a watch or a chase that has read outside content with nobody present, these wait for a yes too.
Asks first, every time
Always waits for your yes
- Add an account
- Complete a task
- Log an email against a record
- Send an email from Salesforce
- Apply the lead assignment rules to a lead
Ray posts a card showing exactly what it is about to do. Nothing happens until someone approves, 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.
- Delete an account, contact, lead, opportunity, or note
- Create custom objects or fields
- Run bulk ingest or query jobs
- Mass-transfer record ownership
Exactly what Ray will ask you to approve.
Not a category of permission. These are the Salesforce actions that stop in the thread with the real content before they happen.
- Apply the lead assignment rules to Salesforce lead
- Complete Salesforce task
- Add an account to Salesforce
- Log an email in Salesforce
- Send an email from Salesforce
Ray does these at once
- Link Salesforce contact
- Add a contact to Salesforce
- Add a lead to Salesforce
- Add a note in Salesforce
- Create a Salesforce opportunity
- Create a Salesforce task
- Log a call in Salesforce
- Update Salesforce account
- Update Salesforce contact
- Update Salesforce lead
Everyday work. Anything Ray can put back comes with an Undo button on its reply.
Apply the lead assignment rules to Salesforce lead
Showing Lead id, each carrying the exact content that will land.
How Ray works with Salesforce
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect Salesforce
One click, right where you asked. Ray posts a connect card, you authorise Salesforce 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.
Megan
@Ray the checkout bug is back. Take a look in Salesforce, and tell Dana it is being looked at.
Link Salesforce contact
- Done
- just now
Ray uses Salesforce together with the rest of your tools.
One ask can read Salesforce, 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 Salesforce to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect Salesforce and it can do the Salesforce part of a request without anyone leaving the conversation: read what it needs and make the change, asking first before anything that can’t be taken back.
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 Salesforce account, so Ray can only reach what that person can already reach, and the history in Salesforce shows who actually asked.
Security and permissions
- You authorise Salesforce on its own login screen. Your password never passes through Ray.
- What waits for a yes is decided in the execution path, not by a prompt. No setting lets an irreversible action through without one.
- Each workspace is isolated at the database level, and that isolation is tested by trying to break it.
- Disconnect Salesforce in a message, or uninstall Ray and every connection it held is revoked.
Salesforce and Ray, answered
The questions teams ask before they connect Salesforce. 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 Salesforce.
Free to start, no credit card, and nothing irreversible happens without your yes.
By adding Ray, you accept the Terms and Privacy Policy.