- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi Everyone,
I need to give a demo of ServiceNow to a client who has little or no prior knowledge of the platform. I would like to make the demo simple and easy to understand, starting from the basics and gradually covering the key concepts.
Could you please suggest a good approach or demo flow covering the following topics?
What is ServiceNow, and why do organizations use it?
How does ServiceNow work at a high level?
Overview of the major ServiceNow modules/applications, with 4–5 lines explaining each module.
ServiceNow table structure and how tables are related.
Users, Groups, and Roles – what they are and how they are related.
What are Incident and Problem Management?
How do we create/raise an Incident (INC) from the Service Portal?
How do we create/raise a Problem (PRB) and what happens after it is created?
What happens to an Incident/Problem after submission – assignment, state changes, resolution, closure, etc.?
Any other important ServiceNow concepts that should be included in a beginner-friendly client demo.
If anyone has a sample demo flow, presentation, documentation, or recommendations for conducting such a beginner-level ServiceNow demo, I would really appreciate your guidance.
Thank you in advance!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
5 hours ago
Since the audience has little or no ServiceNow knowledge, I'd recommend telling the story from a business user's perspective rather than starting with technical concepts.
A simple flow could be:
What ServiceNow is and the business problems it solves.
High-level overview of the platform and major modules.
Explain tables as "database spreadsheets" and show how records are stored.
Introduce Users, Groups, and Roles using a support team example.
Demonstrate Incident Management:
User raises an incident from the Service Portal.
Incident gets assigned to a support group.
Show state transitions (New → In Progress → Resolved → Closed).
Demonstrate Problem Management:
Multiple incidents point to the same root cause.
Create a Problem record and explain root cause analysis.
Show how fixing the problem prevents future incidents.
Briefly show reports, dashboards, notifications, and approvals.
End with an end-to-end scenario covering the full lifecycle.
My suggestion is to keep the technical details light and focus on a real-world example (e.g., "Employee unable to access email"). Clients usually understand ServiceNow much faster when they can follow a business process from issue creation to resolution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
5 hours ago
Since the audience has little or no ServiceNow knowledge, I'd recommend telling the story from a business user's perspective rather than starting with technical concepts.
A simple flow could be:
What ServiceNow is and the business problems it solves.
High-level overview of the platform and major modules.
Explain tables as "database spreadsheets" and show how records are stored.
Introduce Users, Groups, and Roles using a support team example.
Demonstrate Incident Management:
User raises an incident from the Service Portal.
Incident gets assigned to a support group.
Show state transitions (New → In Progress → Resolved → Closed).
Demonstrate Problem Management:
Multiple incidents point to the same root cause.
Create a Problem record and explain root cause analysis.
Show how fixing the problem prevents future incidents.
Briefly show reports, dashboards, notifications, and approvals.
End with an end-to-end scenario covering the full lifecycle.
My suggestion is to keep the technical details light and focus on a real-world example (e.g., "Employee unable to access email"). Clients usually understand ServiceNow much faster when they can follow a business process from issue creation to resolution.