resolved
ServiceNow
servicenow.com/now/nav/ui/classic/params/target/incident_list.do
landed in 38msBookSlash for ServiceNow · IT
ITSM URLs
humans can remember.
ServiceNow URLs are the kind of URLs that look like database queries — because they are. BookSlash lets your IT and ops teams reach the helpdesk queue, the CMDB, and the change-approval board with shortcuts they actually remember.
helpdesk
other shortcuts you might save
b/helpdeskb/incidentsb/changesb/cmdb
Suggested slug patterns
Steal these. They work for most teams.
Battle-tested shortcut conventions for ServiceNow, with notes on why each one survives the URL changes that break personal bookmarks.
- b/helpdesk
Open helpdesk ticket queue assigned to the IT team.
Replaces a fragile saved-filter URL that breaks every Now Platform upgrade.
https://{instance}.service-now.com/now/nav/ui/classic/params/target/incident_list.do - b/incidents
Active incidents view in the IT module.
IT operations leads check this multiple times daily.
https://{instance}.service-now.com/incident_list.do?sysparm_query=active%3Dtrue - b/changes
Change approvals dashboard (CAB queue).
Managers and approvers need it weekly; saving it ends the recurring "where’s the link?" thread.
https://{instance}.service-now.com/change_request_list.do - b/cmdb
Configuration management database starting view.
IT and security reach this constantly during audits.
https://{instance}.service-now.com/cmdb_ci_list.do - b/agent
Agent workspace for triaging tickets.
Service desk agents open it dozens of times a day.
https://{instance}.service-now.com/now/agent-workspace - b/portal
Self-service portal for end users.
IT shares this slug with every employee; saves the link from rotting in onboarding docs.
https://{instance}.service-now.com/sp
Common workflows
Three patterns that pay back in week one.
01
Service desk daily startup
Every agent starts their shift at b/helpdesk. The URL is the team’s shared filter; the destination changes as IT tunes the priority rules. Agents see the same queue, never train new agents on a private bookmark.
02
Change approval flow
Engineering proposes a change in ServiceNow; the approver clicks b/changes from a Slack thread. Approvers see the same view, the slug stays consistent across CAB membership rotations.
03
Audit prep
Auditors get a curated list of slugs (b/cmdb, b/incidents, b/changes) instead of a Notion doc that drifts. The audit log in BookSlash records every URL change, satisfying SOC 2 change-control evidence.
With and without
Same ServiceNow. Different team experience.
Without shortcuts
IT keeps a private Confluence page of "useful ServiceNow URLs" that drifts every quarter. Service desk onboarding includes a 30-minute "here are the dashboards" walkthrough.
With BookSlash
b/helpdesk, b/incidents, b/changes, b/cmdb, b/agent, b/portal. Six slugs, the whole IT team. Audit logs prove who changed what URL when.
Related integrations
Pair ServiceNow with one of these.
Frequently asked
BookSlash + ServiceNow
Yes. Slugs are URL → URL redirects; any ServiceNow module exposed as a URL works. Most teams namespace by module: b/itsm-helpdesk, b/itom-cmdb, b/hrsd-portal.
No — slug resolution is URL-only. For automated ticket creation, use ServiceNow’s native API. BookSlash is the discovery layer; ServiceNow is the action layer.
Mobile slug resolution lands the user at the URL in their phone browser. ServiceNow’s mobile app handles deep links via its own URL schemes — those work too if you point a slug at a deep-link URL.
One BookSlash edit per affected slug. The audit log shows who edited which slug after the upgrade; end users keep typing the same shortcut and never feel the migration.
Start with one team. Roll out when it sticks.
Your stack. Your shortcuts.
One keystroke for everyone.
2,400+ teams reach every important destination in their stack with a single keystroke. Save the first slug in 30 seconds.
Free for personal use · No credit card · 14-day team trial