ServiceNow
ServiceNow is the service management backbone of most large organisations, and the single largest source of "where is my ticket" contact in any enterprise that runs it.
ServiceNow is the service management backbone of most large organisations, and the single largest source of "where is my ticket" contact in any enterprise that runs it.
What ServiceNow holds, and why that matters here
ServiceNow holds incidents, requests, changes and the catalogue of services an organisation offers internally. It is powerful, comprehensive, and — for most employees — an interface they use reluctantly and infrequently.
That gap between capability and usability is exactly where an assistant helps. Employees know what they need; they do not know which catalogue item corresponds to it, or where their existing request has reached. Both are answerable in a sentence.
- Incidents — what is broken, its state and who is working on it.
- Requests — what was asked for and where it has reached.
- Catalogue — the services available and what each requires.
- Changes — planned work and its approval state.
- Knowledge — the articles that answer the question without a ticket at all.
Questions Elbi can answer from ServiceNow
Where is my ticket?
State, owner and last update — the highest-volume internal question in any ServiceNow organisation.
How do I request this?
The right catalogue item and what it needs, rather than a search through a catalogue nobody navigates well.
Is this a known issue?
Matching a symptom against open incidents, which prevents duplicate tickets.
What is the approval status?
Where a request is sitting and who it is waiting on.
Raise this for me
Creating a correctly categorised ticket from a conversation, where you enable it.
Is there planned work?
Change schedule, which answers a large share of "is something wrong" contact.
How Elbi works with a ServiceNow instance
- An integration user with only the roles it needsYour ServiceNow administrator creates a dedicated integration user in your instance and gives it roles that reach the incident, request, change, catalogue and knowledge tables agreed for the deployment, and nothing broader. ServiceNow's own access controls then apply to that user exactly as they would to a member of staff.
- OAuth or credentials you registerThe connection talks to ServiceNow's REST interface, authenticating either through an OAuth client registered in your instance or with the integration user's own credentials. In both cases your team creates the secret and can rotate or revoke it from the instance.
- The asker is matched to their ServiceNow userAn employee signs in through your own identity provider and Elbi matches them to their user record. Status questions are answered from tickets where they are the caller or the "requested for" person, so nobody is shown a colleague's incident.
- Reference numbers are optionalSomeone can quote an INC or RITM number, or simply ask about "my laptop request". Elbi finds the record and reads its state, assignment group and latest customer-visible comment, and leaves internal work notes where they are.
- States become sentences"On Hold – Awaiting Caller" becomes "the service desk is waiting for your reply", in Arabic or English depending on how the question was asked. A pending approval is described by whose desk it is sitting on, not by the approval record's code.
- Write-back only where you switch it onWhere enabled, Elbi opens an incident or submits a catalogue request with the conversation attached, so the agent who picks it up does not ask the same questions again. Closing, reassigning and approving stay with people.
ServiceNow roles, access controls and what stays yours
| Direction of access | Read on the tables agreed at deployment. Creating an incident, submitting a catalogue item and adding a comment to an open ticket are separate permissions, each enabled on its own and each able to wait for a person's confirmation. |
|---|---|
| Who can see what | Two limits apply together. The roles and access controls on the integration user set the ceiling, and the identity of the person asking narrows every answer to what they could open in ServiceNow themselves. |
| Credentials | The integration user and any OAuth client live in your instance. Deactivating the user or revoking the client ends the connection at once, with no call to us. |
| Where data goes | Tickets stay in ServiceNow and are read at the moment of the question rather than copied. Message content from the conversation is destroyed within 24 hours, usually when the conversation ends, and no external AI service sees it. |
| Audit | Elbi records each lookup: the question, what was retrieved, the agent and the conversation. Anything it creates in ServiceNow carries the integration user as its author, so the ticket's own history shows what arrived through the assistant. |
| If it is unavailable | During an upgrade window or an outage, Elbi says it cannot reach ServiceNow and offers a person. It will not report a ticket state it was unable to read. |
What this replaces
The most valuable thing an assistant does with ServiceNow is prevent tickets rather than track them. A significant share of incidents are questions the knowledge base already answers, raised as tickets because searching the knowledge base is harder than asking.
The second is correct categorisation. Mis-categorised tickets are routed wrongly, sit in the wrong queue and resolve slowly, and the cause is almost always that the person raising it did not know which category applied. An assistant that gathers the details conversationally and creates a correctly categorised ticket removes that entire failure mode.
The third is status. "Where is my ticket" is the most common follow-up contact in enterprise IT and contributes nothing when answered by a person.
How different sectors use a ServiceNow connection
Enterprise IT
Ticket status and catalogue navigation at scale.
HR shared services
Where ServiceNow is used for HR cases as well as IT.
Facilities
Request status for maintenance and workplace services.
Large government
Internal service delivery across departments.
Getting value from ServiceNow
ServiceNow already knows why people contact the desk: every incident has a category, every request has a catalogue item, and every chase shows up as another comment. Report on a recent month of those before choosing anything, and the first flows tend to choose themselves.
In most instances the order is the same. First, the status of the asker's own open incidents and requested items, because that is where follow-up volume sits. Second, knowledge articles offered before a ticket is raised, since an incident avoided is worth more than one tracked. Third, the catalogue finder: matching "I need access to the finance share" to the right item and collecting its variables in conversation instead of on a form.
Write-back comes after that. Raising an incident with the transcript attached, or adding a comment when someone answers a ticket that is waiting on them, are the useful ones. Approvals, reassignment and closure are better left inside ServiceNow, where the people accountable for them already work.
What connecting ServiceNow involves
- Rank the questions from your own ticketsIncident categories, request volumes and the chasers logged as comments show what people actually ask. That ranked list, not the list of available tables, sets the scope.
- Agree tables and fields in writingYour ServiceNow owner signs off which tables and fields Elbi may read, usually incident, requested item, change, catalogue and knowledge, and which stay out, such as HR cases or security incidents. That sign-off is what an auditor will ask to see.
- Create the integration user and its secretYour administrator creates the user, assigns the agreed roles and registers the OAuth client or password. The secret stays with your team, who can rotate or revoke it on their own schedule.
- Map your instance, not the default oneCustom states, renamed categories, assignment groups, extra catalogue variables and any scoped applications are mapped during deployment, together with the Arabic wording each state should be described in.
- Rehearse on sub-production firstWhere you have a development or test instance, the awkward cases are tried there: an unknown INC number, a ticket that belongs to someone else, a catalogue item with mandatory variables, the instance halfway through an upgrade.
- Go live on status, then widenStart with ticket status and knowledge, read a month of real questions, then enable ticket creation. Widening in that order keeps every step easy to reverse.
Personal data inside ServiceNow tickets
Incident descriptions are free text, and people put anything in them: mobile numbers, identity numbers pasted in to prove who they are, the medical reason behind an absence. Under the Saudi Personal Data Protection Law that makes every ticket lookup a processing activity, with the usual questions about purpose, access and how long anything is kept.
Two decisions keep it defensible. Leave HR cases and other sensitive tables out of scope unless there is a specific reason to include them; in ServiceNow they normally sit behind their own, narrower roles anyway. And have Elbi return only the fields an answer needs, such as state, assignment group and the last public comment, rather than the full description. What it reads serves the answer in front of it, and the conversation holding that answer is destroyed within 24 hours.
Where contractors or customers use the portal as well as employees, tell them plainly, in Arabic and English, that their tickets will be read in order to answer them.
What organisations typically see
ServiceNow's own assistants, and where Elbi fits
ServiceNow has its own conversational options: Virtual Agent, which runs guided conversations in the platform's portals and messaging channels, and Now Assist, its family of generative AI features. For an organisation whose service desk lives entirely in ServiceNow, and whose licences already include them, they are a sensible first thing to evaluate.
Elbi is the alternative when one assistant has to answer from ServiceNow and from systems outside it, such as HR, finance or a customer-facing portal, in Arabic and English, under one set of governance and one audit trail. ServiceNow stays the system of record; Elbi is one front door to it.
Whichever route you take, the same mistakes recur. Pointing an assistant at the whole CMDB produces answers nobody asked for. Letting it close or reassign tickets without a person removes the accountability ServiceNow was bought to provide. And an assistant that cannot say "ServiceNow is unavailable right now" will sooner or later report a stale state as fact.
Common questions
Where you enable it, and correctly categorised — which is often more valuable than the time saved, because mis-categorised tickets resolve slowly.
Yes, and preventing the ticket is usually worth more than tracking it.
Yes. Answers are bounded by the permissions of the person asking.
No. Elbi connects as an integration user that your administrator creates, with the roles you choose, and your team can deactivate that user or revoke its OAuth client at any time without going through us.
Most instances are. Custom tables, renamed states, bespoke catalogue items and scoped applications are normal, and they are mapped during deployment instead of assuming the out-of-the-box data model.
Elbi can create incidents, submit requests and add comments where you enable each one, and any of those can wait for a person to confirm. Closing, reassigning and approving are better done in ServiceNow by the people responsible for them.
Connect Elbi to your ServiceNow instance
Ticket status, knowledge and catalogue answers from your own instance, in Arabic and English.