Zendesk
Zendesk is where a great many customer service teams live. Connecting an assistant to it means customers can be told where their ticket has reached without an agent doing the telling.
Zendesk is where a great many customer service teams live. Connecting an assistant to it means customers can be told where their ticket has reached without an agent doing the telling.
What Zendesk holds, and why that matters here
Zendesk holds tickets, their history and the help centre content around them. It is customer-facing rather than internal, which changes the emphasis: the highest-volume question is status, and the person asking is the customer rather than an employee.
The help centre matters too. Most Zendesk deployments have a substantial knowledge base that customers do not read, because searching is harder than asking. An assistant that answers from it converts that investment into deflected contact.
- Tickets — state, history and assigned agent.
- Help centre — the articles that answer questions without a ticket.
- Users and organisations — who the customer is and their history.
- Macros and workflows — the standard responses your team already uses.
- Satisfaction — ratings and follow-up state.
Questions Elbi can answer from Zendesk
Where is my ticket?
Status and last update, answered to the customer directly.
Has this been resolved?
Resolution state, which prevents a large share of chase contact.
How do I do this?
Answered from your help centre rather than by raising a ticket.
Raise a ticket
Creating one from a conversation with the context already gathered.
Have I contacted you before?
History, so the customer is recognised rather than asked to repeat.
Who is handling this?
Assignment, where you choose to disclose it.
How Elbi works with Zendesk Support and the help centre
- An OAuth client or an API token, created by an adminThe connection authenticates either through an OAuth client registered in Admin Center, with scopes such as read access to tickets and the help centre, or through an API token used with a named user's email address. The OAuth route is usually the tighter one, because its scopes can be limited by resource.
- The connecting user's role sets the ceilingRequests run with the permissions of the user behind the token. An agent limited to tickets in their own groups limits what the connection can reach before any question is asked.
- Customers see only their own ticketsA customer asking "where is my ticket?" is matched to their requester record — through the sign-in or verified email you rely on — and answered only from tickets they requested or, if you allow it, their organisation's shared tickets.
- Public replies and internal notes are kept apartZendesk stores public replies and internal notes on the same ticket. Customer answers draw on status, the last public update and the assigned group; internal notes are excluded, and read for staff only where you allow it.
- Help centre articles, in the reader's languageArticles are read in the locale that matches the question where both Arabic and English versions exist, and articles restricted to user segments stay restricted. When no article covers the question, the assistant says so rather than stretching one that nearly does.
- New tickets arrive with the context attachedWhere enabled, a conversation that needs a person becomes a ticket with the customer as requester, the transcript as the first comment and a tag your triggers can route on. An internal note on an existing ticket, when a customer chases, is the other useful write.
Zendesk roles, scopes and control
| Direction of access | Read by default. Creating a ticket or adding an internal note is enabled per action and can wait for a person to confirm. Changing status, priority or assignee stays with your agents. |
|---|---|
| Scopes and roles | OAuth scopes limit which resources the client can use — tickets, users, the help centre — and whether it may read or write each. The role of the user behind the connection limits it again. |
| Customers and organisations | End users are answered only about tickets they requested, or their organisation's shared tickets where you have enabled that. Staff asking internally are answered within their own role and groups. |
| Credentials | The OAuth client, any API token and the user they act as all live in your Admin Center. An admin can revoke a token or delete the client at any time, without involving us. |
| Where data goes | Ticket details fetched for an answer are used for it and not copied elsewhere. Conversation content is deleted within 24 hours — generally as soon as the chat ends — and nothing is sent to an external AI service. |
| Audit | Lookups can be logged, each with the question behind it. Every ticket the connection creates or annotates carries Zendesk's own ticket audit trail, so those changes are visible on your side. |
| If it is unavailable | If Zendesk cannot be reached or a rate limit applies, the assistant tells the customer it could not check their ticket and offers another way to reach your team. |
What this replaces
The clearest win is deflection through the help centre. Organisations invest heavily in help content and see modest use, because customers would rather ask than search. An assistant that answers from that content changes the economics of the investment without requiring new content.
The second is status. Ticket-chasing is a large, entirely avoidable contact category, and answering it automatically frees agents for the tickets themselves.
The third is intake quality. A ticket raised from a conversation arrives with the details already gathered, which shortens the first response and removes the round trip that starts most support interactions.
Which support teams on Zendesk use it
SaaS and technology
Ticket status and help centre deflection at volume.
Retail and e-commerce
Order-related tickets and returns.
Services businesses
Client request status.
Any Zendesk deployment
Converting an under-used help centre into deflected contact.
Getting value from Zendesk first
Two questions carry most of the value in a Zendesk deployment. "Where is my ticket?" is answered from one record the customer already owns, and every automated answer is one fewer chase reply for an agent. "How do I…?" is answered from help centre articles your team has already written — content paid for once and read too rarely.
Start with those two, in both languages. Check which help centre articles exist in Arabic as well as English: policy wording that customers will quote back to you — refunds, warranties, deadlines — deserves a reviewed Arabic article rather than reliance on the English one.
Ticket creation comes third. Its value is intake quality: a ticket that arrives with the customer identified, the order or account number captured and the question stated removes the first round of back-and-forth that starts most tickets.
Connecting Zendesk, step by step
- Pick the questions and the help centre scopeAgree which ticket questions the assistant answers, which help centre categories or sections it may draw on, and whether customers may see organisation-shared tickets. Those three decisions set most of the scope.
- Create the OAuth client or tokenAn admin registers an OAuth client with read scopes on tickets, users and the help centre, adding write on tickets only if ticket creation is enabled — or creates an API token to be used with a dedicated user. Either way, it stays in your Admin Center.
- Set the connecting user's roleThe user behind the connection should hold the narrowest role that answers the questions — limited to the relevant groups where your plan allows custom roles — so the ceiling is set in Zendesk, not in the assistant.
- Map fields, statuses and triggersCustom ticket fields, custom statuses if you use them, brands and the triggers that route by tag are mapped, so a ticket raised from a conversation lands in the same queue a web-form ticket would.
- Test the awkward casesA customer with tickets under two email addresses, a ticket merged into another, an article that exists only in English, a solved ticket reopened by a reply, and Zendesk unreachable.
- Launch on status and articles, then add intakeGo live on ticket status and help centre answers, read a month of real conversations, then switch on ticket creation. Each step is a scope or role change your admin can reverse.
Zendesk tickets and personal data under the PDPL
Tickets hold more personal data than their fields suggest. Customers paste order numbers, addresses, ID numbers and sometimes health or financial details into the description, and attachments carry more. Under the Saudi Personal Data Protection Law, reading those through an assistant needs a purpose and a basis, and answers should reveal no more than the question needs.
Two choices keep that tight. For customers, answer from status, the last public update and the assigned group rather than from the free text of the ticket. For the help centre, draw only on public articles or on the user segments the asker belongs to. On Elbi's side, messages are destroyed within 24 hours, usually when the conversation ends; Zendesk remains the record, with your existing deletion and redaction practice.
Say at the start of the chat, in the customer's language, that their ticket may be looked up, and that a ticket may be created with the conversation if they need a person.
What organisations typically see
Zendesk's own AI agents, and where Elbi fits
Zendesk has its own automation. Its AI agents answer customers in Zendesk messaging from your help centre and hand over to human agents in the same workspace, and its agent-side AI tools suggest replies and summarise tickets. For a team that runs everything inside Zendesk, having the bot, the queue and the reporting in one place is the main attraction.
Saudi buyers usually weigh three points. Arabic quality on real customer messages, dialect included — test it rather than assume it. Where AI processing for your account takes place, which is worth confirming with Zendesk for your plan and region. And whether customers' questions need sources beyond Zendesk, such as order status in an ERP or a policy document, in the same conversation.
Elbi's position is the same across its integrations: Arabic and English as first languages, conversation processing inside the Kingdom on infrastructure you control, and no external AI service. Zendesk stays the system your agents work in; Elbi answers from it and hands over into it. If Zendesk messaging already carries your chat, decide which assistant owns which channel before running both.
The mistake to avoid on any route is reading ticket descriptions back to customers. They are written for agents, often contain internal shorthand, and sometimes contain another person's details.
Common questions
Yes, and that is usually the largest single win.
Where you enable it, with the context already gathered so first response is faster.
Always, immediately, and with the conversation attached.
No. Customer answers draw on ticket status, public updates and assignment, and internal notes are excluded. Where staff ask internally, notes can be included for roles that already see them in Zendesk.
Each brand's help centre and tickets can be scoped separately, so a customer of one brand is answered only from that brand's content and tickets.
Either works. An OAuth client lets an admin limit scopes by resource, such as read-only tickets and help centre, which makes it the tighter choice. An API token runs with the full permissions of the user whose email accompanies it.
Connect Elbi to your Zendesk
A working assistant on your own tickets and help centre, in Arabic and English.