resolved
Salesforce
salesforce.com/lightning/o/Opportunity/list
landed in 38msBookSlash for Salesforce · Sales
Salesforce URLs are punishing — IDs, sub-IDs, and an interface that re-routes itself with every Lightning release. BookSlash gives revenue teams a stable name for each view they actually open: the active pipeline, the at-risk deals, the weekly forecast.
resolved
Salesforce
salesforce.com/lightning/o/Opportunity/list
landed in 38msother shortcuts you might save
Suggested slug patterns
Battle-tested shortcut conventions for Salesforce, with notes on why each one survives the URL changes that break personal bookmarks.
Sales pipeline view (open opportunities).
Reps and managers both check it daily; replacing the lightning URL with b/pipe pays back in week one.
Active deals filtered by quarter.
Revenue ops updates this filter as the quarter progresses; the slug stays.
Forecast roll-up dashboard.
Weekly forecast call always opens here; saving it as a slug is the lowest-friction path.
Closed-lost opportunities for re-engagement campaigns.
Marketing and sales review this together; the slug carries no auth burden.
Pattern for sharing an account view (e.g., b/account-acme).
Replaces 80-character Salesforce URLs in Slack threads. Renders cleanly in chat.
Data-hygiene dashboard (missing fields, stale records).
Revenue ops runs this weekly; a slug ends the recurring "where’s the dashboard?" ping.
Default revenue reports folder.
Sales leaders, marketing, finance all reach it weekly.
Common workflows
Every revenue leader opens b/forecast at 9 a.m. The URL underneath evolves as Salesforce admins tweak the dashboard; the slug never changes. The forecast call starts on time, every time.
When a deal closes-won, the AE pastes b/account-acme in the handoff Slack thread. The CSM clicks once, lands on the account view, runs the post-close checklist. No 80-character URL paste, no auth-required preview that fails to render.
Revenue ops runs a quarterly data-hygiene sweep from b/hygiene. The dashboard underlying the slug evolves — new required fields, new owners — but the slug remains the team’s shorthand.
With and without
Without shortcuts
Every rep has a private bookmark folder. The forecast URL changes every quarter when ops rebuilds the dashboard. Account URLs in Slack are 80 characters of ID soup.
With BookSlash
b/pipe, b/deals, b/forecast, b/closed-lost, b/hygiene, b/reports. Six slugs cover the whole revenue team. Account references in Slack become readable: b/account-acme.
Related integrations
Frequently asked
Both. Slugs are URL → URL — Salesforce serves a URL, the slug points at it. Most orgs are on Lightning today; the slug pattern is identical.
Slugs are workspace-scoped in BookSlash, but the destination URL is what gets visited. For different sandboxes, namespace: b/account-acme-prod vs b/account-acme-uat.
Point the slug at the report folder URL or the report URL itself. Most revenue teams keep a slug for the team folder (b/reports) and named slugs for the high-traffic individual reports (b/forecast, b/qbr).
No — slugs are not data syncs. BookSlash gets you to Salesforce in one keystroke; Salesforce is still where deal data lives. For a "deal at a glance" experience, embed Salesforce reports on a BookSlash board.
Start with one team. Roll out when it sticks.
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