Freshdesk
Freshdesk serves a large number of mid-market support teams, and the assistant case is the same as any ticketing system: status, deflection and better intake.
Freshdesk serves a large number of mid-market support teams, and the assistant case is the same as any ticketing system: status, deflection and better intake.
What Freshdesk holds, and why that matters here
Freshdesk holds tickets, contacts and a knowledge base, aimed at teams that need capable support tooling without enterprise complexity. The organisations running it typically have small support teams handling disproportionate volume.
That makes deflection more valuable than in a large enterprise. Every ticket avoided is a meaningful share of a small team's capacity, and the questions being deflected are almost always ones the knowledge base already answers.
- Tickets — status, priority, history and assignment.
- Contacts — who the customer is and what they have raised before.
- Solutions — the knowledge base articles that prevent tickets.
- SLAs — response and resolution targets against a ticket.
- Automations — the rules your team already relies on.
Questions Elbi can answer from Freshdesk
Where is my ticket?
Status and last update without an agent replying to say so.
How do I fix this?
Answered from your solutions articles rather than by raising a ticket.
When will this be resolved?
SLA target against the ticket, which sets expectations honestly.
Raise a ticket
Created from the conversation with details already gathered.
Have I asked before?
Contact history, so customers are not asked to repeat themselves.
Is this urgent enough?
Priority guidance from your own policy rather than guesswork.
How Elbi reads from Freshdesk
- An API key that belongs to one agentFreshdesk's API authenticates with an agent's API key, and every request runs with that agent's permissions. The connection therefore starts with a choice of agent — usually one set up for the purpose — rather than with a key borrowed from an administrator.
- Role and ticket scope set the ceilingThat agent's role decides what it may do, and its ticket scope — global, group, or restricted to assigned tickets — decides which tickets it can see at all. Group access limited to the groups the questions concern is usually enough.
- Customers are matched to their own ticketsA customer asking about a ticket is matched to their contact record through the sign-in or verified email you rely on, and answered only from tickets they raised, or from their company's tickets where that contact is allowed to see them.
- Due-by times answer "when"Freshdesk stamps each ticket with first-response and resolution due-by times from your SLA policies. "When will this be resolved?" is answered from those — an honest target, stated as a target — rather than from a guess.
- Private notes stay privateA Freshdesk conversation mixes replies, public notes and private notes. Customer answers use status, due-by times and public updates; private notes are excluded, and read for staff only where you allow it.
- Solution articles, and tickets that arrive completeSolution articles are read from the folders you choose, respecting each folder's visibility. Where a conversation needs a person, a ticket can be created with the transcript, contact and category already set, so your automations route it like any other.
Freshdesk roles, ticket scope and control
| Direction of access | Read by default. Creating a ticket or adding a private note is enabled per action and can wait for a person to confirm. Status, priority and assignment stay with your agents. |
|---|---|
| Role and ticket scope | Set on the agent whose API key the connection uses: the role limits actions, and the ticket scope — global, group or restricted — limits which tickets exist for it. |
| Contacts and companies | Contacts are answered about their own tickets, and about their company's only where Freshdesk allows that contact to view them. Staff are answered within their own ticket scope. |
| Credentials | The API key belongs to an agent in your account. It can be reset from that agent's profile, or the agent deactivated, at any time and without involving us. |
| Where data goes | What is read from a ticket is used for the reply and not copied into another store. Chat content is destroyed within 24 hours, most often the moment the conversation ends, and no external AI service receives it. |
| Audit | Every lookup can be logged against the question that prompted it. Tickets created or annotated by the connection show in that ticket's own activity history in Freshdesk. |
| If it is unavailable | If Freshdesk cannot be reached or your plan's API rate limit is reached, the assistant says it could not check and offers to pass the customer to your team. |
What this replaces
Small support teams are the clearest beneficiaries of deflection. A team of four handling several hundred tickets a week cannot absorb growth, and the questions driving that volume are overwhelmingly repetitive and already documented.
The second effect is on first response. A ticket created from a conversation arrives with the context gathered, which removes the exchange that starts most support interactions and shortens time to resolution measurably.
The third is out of hours. Mid-market teams rarely staff overnight, so the alternative to an assistant is a queue that starts the next morning already behind.
Which Freshdesk teams feel it most
SaaS and software
Deflection through solutions articles.
E-commerce
Order and returns tickets with better intake.
Services
Client request status.
Small support teams
Absorbing volume growth without headcount.
Getting value from Freshdesk quickly
For a small support team, the first connection worth making is the solutions knowledge base. The articles already exist, the questions they answer arrive every day, and each one answered is one fewer ticket for a team that cannot easily absorb growth.
Ticket status comes next, and Freshdesk makes it more useful than most: because every ticket carries a resolution due-by time, "when will this be fixed?" gets a real target rather than "soon". Start with status and due-by, not with the conversation history.
Creating tickets is the third step. A ticket that arrives with the contact matched, the category set and the question in the customer's own words removes the first exchange from most tickets — which matters more when there are only a few agents to have it.
Connecting Freshdesk, step by step
- Choose the questions and the solution foldersAgree which ticket questions the assistant answers and which solution categories and folders it may draw on. Folders visible to agents only stay out of customer answers.
- Set up the connecting agentCreate or choose the agent whose API key the connection will use, with the narrowest role your plan allows and a ticket scope limited to the relevant groups.
- Hand over the API keyThe key is copied from that agent's profile into the connection. It remains yours: resetting it, or deactivating the agent, ends the connection's access.
- Map fields, statuses and groupsCustom ticket fields, custom statuses, ticket types, groups and the automations that route new tickets are mapped, with Arabic wording agreed for any status name a customer will hear.
- Test the awkward casesA contact with two email addresses, a merged ticket, a ticket waiting on the customer, an SLA already breached, an article that exists only in English, and Freshdesk unavailable.
- Launch on articles and status, then add ticketsGo live on solution articles and ticket status, read a month of real conversations, then enable ticket creation. Each step is a role or scope change you control.
Freshdesk tickets, contacts and the PDPL
The personal-data question specific to Freshdesk is company visibility. Where a contact may view all of their company's tickets, a colleague's complaint — with whatever that colleague wrote in it — becomes visible to them too. Under the Saudi Personal Data Protection Law that is a disclosure worth deciding on deliberately, rather than inheriting it from a portal setting chosen years ago.
The rest is scope. The connecting agent's ticket scope bounds what can be read at all, and answers to customers draw on status and due-by times, not on the free text where people paste order numbers, addresses and ID numbers. On Elbi's side, conversation content does not survive beyond 24 hours and is usually destroyed when the conversation ends; Freshdesk remains the record, and deletion requests are handled there as they are now.
Tell customers at the start, in the language they write in, that their ticket may be checked, and that a ticket may be opened with the conversation if they need a person.
What organisations typically see
Freddy AI, Freshchat and where Elbi fits
Freshworks has its own AI layer. Freddy AI powers self-service bots that answer from your solution articles and features that help agents draft and summarise, and Freshchat carries messaging with bot flows. For a team that wants one vendor for helpdesk, chat and bot, that is a coherent choice.
Saudi buyers should test the same things whichever route they take: the Arabic on real messages, dialect included; where AI processing happens for their account, since Freshworks accounts sit in a data-centre region chosen at sign-up; and whether customers' questions need sources beyond Freshdesk, such as order status from an ERP, in the same conversation.
Elbi's position is the same for every system: Arabic and English as first languages, conversation processing inside the Kingdom on infrastructure you control, no external AI service. Freshdesk stays where your agents work; Elbi answers from it and hands over into it. If Freshchat already runs your messaging, give each channel one assistant, not two.
The mistake to avoid is connecting with an administrator's API key because it is the one to hand. Every request then runs with administrator rights, which undoes everything the ticket scope settings were meant to achieve.
Common questions
Yes — usually the highest-value connection here.
Where you enable it, with context gathered.
It can report against them, which sets expectations honestly.
Those of the agent it belongs to. That is why the connection uses an agent with a narrow role and group-level ticket scope, never an administrator's key.
No. Customer answers use status, due-by times and public updates, and private notes are excluded. Staff asking internally can see the notes their own ticket scope already allows.
Where you maintain Arabic versions of your solution articles, those are used for Arabic questions. For anything customers will rely on, such as refund or replacement terms, a reviewed Arabic article is worth adding where only an English one exists.
Connect Elbi to your Freshdesk
A working assistant on your own tickets and solution articles, in Arabic and English.