resolved
Zendesk
zendesk.com/agent/dashboard
landed in 38msBookSlash for Zendesk · Support
Tickets, views,
and CSAT — flat URLs.
Zendesk URLs are forgettable; agents need to reach the right view dozens of times a shift. BookSlash gives the support team a flat name for each — the open queue, the assigned-to-me list, the weekly CSAT dashboard.
inbox
other shortcuts you might save
b/inboxb/ticketsb/conversationsb/csat
Suggested slug patterns
Steal these. They work for most teams.
Battle-tested shortcut conventions for Zendesk, with notes on why each one survives the URL changes that break personal bookmarks.
- b/inbox
Default agent inbox.
Every agent opens it dozens of times a day.
https://{subdomain}.zendesk.com/agent/dashboard - b/tickets
Open tickets across the team.
Managers and team leads reach it constantly.
https://{subdomain}.zendesk.com/agent/filters/{filter-id} - b/conversations
Active conversations / chat queue.
Chat agents reach it every shift.
https://{subdomain}.zendesk.com/chat/agent - b/csat
CSAT analytics dashboard.
Weekly leadership review URL.
https://{subdomain}.zendesk.com/explore/dashboards/{dashboard-id} - b/route
Routing / triggers configuration.
Support ops debugs routing from this URL.
https://{subdomain}.zendesk.com/admin/objects-rules/rules/triggers - b/automate
Automations and triggers list.
Support ops reaches it weekly during automation reviews.
https://{subdomain}.zendesk.com/admin/objects-rules/rules/automations - b/onboard
Agent onboarding view / training URL.
New agents land here day one.
https://{subdomain}.zendesk.com/hc/en-us/categories/{onboarding-id}
Common workflows
Three patterns that pay back in week one.
01
Daily agent startup
Every agent opens b/inbox on shift start. The Zendesk view evolves as the team adds filters; the slug stays. New agents are productive day one with three slugs.
02
Weekly CSAT review
Support leadership opens b/csat every Monday. The dashboard underneath evolves; the slug carries through. Same numbers, every week, no re-bookmarking.
03
Routing / automation debug
When a ticket misroutes, ops opens b/route to inspect rules. Pairs with b/automate for trigger debugging. Two slugs replace a five-minute navigation tour.
With and without
Same Zendesk. Different team experience.
Without shortcuts
Each agent has a private bookmark folder for Zendesk views. Onboarding includes a 30-minute "here’s the inbox" walkthrough.
With BookSlash
b/inbox, b/tickets, b/conversations, b/csat, b/route, b/automate, b/onboard. Seven slugs cover the support surface for the whole team.
Related integrations
Pair Zendesk with one of these.
Frequently asked
BookSlash + Zendesk
Yes — every Zendesk product exposed as a URL works. Namespace per product: b/sell-pipe (Sell), b/support-inbox (Support).
No — Zendesk handles ticketing; BookSlash routes URLs. Together: BookSlash gets agents to the inbox in one keystroke; Zendesk handles everything that happens after.
Point a slug at the customer view URL: b/customer-acme. Replaces the 80-character Zendesk URL paste in handoff Slack threads.
Most support teams use both for different surfaces. Namespace: b/zendesk-tickets vs b/intercom-inbox. Or keep them flat: b/inbox (Zendesk) and b/chat (Intercom). The b/ pattern unifies both tools.
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