Freshdesk, without opening Freshdesk.
Tickets, what was said on them, and the reply that closes one out.
- 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 Freshdesk details, and Ray takes it from there.
@Ray what is still unanswered in support from yesterday?
@Ray reply to that ticket with the workaround from the help article.
@Ray which tickets are about to breach their SLA?
@Ray add a note on the Acme ticket that engineering is on it.
What Ray can and cannot do in Freshdesk
Reading is free, because reading changes nothing. Everything that writes waits for you. The rest is not on Ray’s list.
81 reads wired, 61 actions that wait for a human.
Runs on its own
What Ray reads in Freshdesk
- Tickets with their conversations, fields, and time entries
- Contacts, companies, agents, groups, and skills
- Canned responses, solution articles, and discussion topics
- Satisfaction ratings and the SLA policies behind them
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What waits for your approval
- Reply to a customer, or add a note only your colleagues see
- Create or update a ticket, and update many at once with one change
- Create or update contacts, companies, and solution articles
- Forward a ticket to an address you name
- Log time against a ticket, and watch one
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.
- Read the agent profile endpoint, which returns that agent's API key
- Export your contacts to a file
- Create canned responses in bulk, which no single card could show you
- Change your helpdesk's email settings, which govern every mailbox
- Delete a ticket, contact, company, or conversation
Exactly what Ray will ask you to approve.
Not a category of permission. These are the Freshdesk actions Ray can take, each one stopping in the thread with the real content before it happens.
- Freshdesk: add note to ticket
- Freshdesk: add ticket user access
- Freshdesk: add watcher
- Freshdesk: bulk unwatch tickets
- Freshdesk: bulk update tickets
- Freshdesk: create admin
- Freshdesk: create admin group
- Freshdesk: create admin ticket field
- Freshdesk: create admin ticket field section
- Freshdesk: create agents
Freshdesk: add note to ticket
Showing Body and Ticket id, each carrying the exact content that will land.
How Ray works with Freshdesk
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect Freshdesk
Freshdesk 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 Freshdesk, and tell Dana it is being looked at.
Freshdesk: add note to ticket
- Waiting on
- your approval
Ray uses Freshdesk together with the rest of your tools.
One ask can read Freshdesk, 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 Freshdesk to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect Freshdesk and it can do the Freshdesk 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.
Freshdesk 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 Freshdesk. Every write still stops for approval first.
Security and permissions
- You paste the Freshdesk 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 Freshdesk in a message. Uninstall Ray and every connection it held is revoked.
Freshdesk and Ray, answered
The questions teams ask before they connect Freshdesk. 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 Freshdesk.
Free to start, no credit card, and it asks before it acts.
By adding Ray, you accept the Terms and Privacy Policy.