Dialpad, without opening Dialpad.
Read what a call decided without listening to it again.
In your channel
Ask Ray for something in Dialpad and it posts this card in the thread. One click, and the task you asked for carries on where it left off.
What Ray can and cannot do in Dialpad
Reading is free, because reading changes nothing. Everything that writes waits for you. The rest is not on Ray’s list.
Runs on its own
What Ray reads in Dialpad
- Fetch call by id
- Fetch call transcript by id
- Fetch user details by id
- Get call center status by id
- Get call labels
- Get phone number details
- List offices endpoint
- List users
- Retrieve callcenter operators by id
- Retrieve call centers information
- Retrieve call center by id
- Retrieve call information
- Retrieve company data
- Retrieve contact by id
- Retrieve contact list
- Retrieve department by id
- Retrieve list of departments
- Retrieve numbers via api v2
- Retrieve office by id
- Retrieve operator duty status
- Retrieve sms opt out by company id
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What waits for your approval
- Send SMS via Dialpad
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.
- Delete access control policy by id
- Transfer call to destination
- Patch websocket signature secret
- Delete agent status by id
- Post websocket connection secret
How Ray works with Dialpad
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect Dialpad
One click, right where you asked. Ray posts a connect card, you authorise Dialpad 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
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 Dialpad, and tell Dana it is being looked at.
Send SMS via Dialpad
- Waiting on
- your approval
What does connecting Dialpad to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect Dialpad and it can do the Dialpad 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 Dialpad account, so Ray can only reach what that person can already reach, and the history in Dialpad shows who actually asked.
Security and permissions
- You authorise Dialpad 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 Dialpad in a message, or uninstall Ray and every connection it held is revoked.
More email & comms integrations
Ray uses them together in a single run when a request spans more than one.
Put Ray to work in Dialpad.
Free to start, no credit card, and it asks before it acts.