6 ways to help users find Salesforce records faster

Searching for a customer, case or opportunity should be a small part of the job. Yet users can lose time opening similar records, trying several spellings or asking an administrator whether a record still exists.

The answer is not always a new tool. Salesforce already provides configurable search layouts, filters, sorting, Search Manager, list-view search, recent items and favourites. The platform behaviour below comes from current Salesforce guidance; the order in which to review it is practical Ostrelis advice. Start with one heavily used object and a few real examples of failed searches.

1. Make search results easy to recognise

For admins: search is only useful when people can distinguish one result from another. Salesforce search layouts control the columns on result pages and can also affect the secondary information and previews shown in instant results. Choose fields that answer the user's recognition question.

For Accounts, that might be postcode, account owner and customer status. For Cases, it might be status, contact, created date and subject. Do not simply add every available field. Salesforce allows up to ten fields in a search layout, while mobile users see only the first six, so put the strongest identifiers first.

Quick action: collect five pairs of records that users commonly confuse and check whether the current result columns separate them.

2. Add filters and sorting that match real questions

For admins and users: a broad keyword can produce a broad result set. Salesforce lets supported objects use selected fields for filtering, and visible result fields can be sortable. The practical choice is to expose the few dimensions people actually use: perhaps owner, status, region or record type.

A filter should narrow a meaningful choice, not reproduce the entire data model. Ask users what they know when they begin a search. If they normally know that a case is open and belongs to a particular customer, those clues are more useful than an internal field that few people understand. Test permissions too: adding a field to a search layout does not override field-level security.

Quick action: take the most common failed search and identify the one filter that would remove most irrelevant results.

3. Confirm what Salesforce can actually search

For admins: changing result columns does not change which fields are matched by a keyword. Salesforce explicitly distinguishes search layouts from the search index. In Lightning Experience with Einstein Search, Search Manager provides the organisation-specific view of searchable objects and fields.

Check this before telling users that a field can be searched or building a workaround. Searchability varies by field and configuration; formula, lookup and some non-text fields often behave differently from plain text. A field displayed on the page is not automatically indexed for search.

Quick action: use Search Manager to verify the three fields users most often expect to search, and document the result in the admin guide.

4. Use list-view search with its limits in mind

For users: when you already know the object and the working set, the search box inside a list view can be quicker than global search. It searches searchable fields even when those fields are not shown as columns. Quotation marks can also stop spell correction when an exact term matters.

There is an important confirmed limit: Salesforce searches only the first 2,000 records in the list. If a record is missing from a large view, narrow the list filters or change the sort order before assuming the record does not exist. Partial strings also have limits, and the search-box tooltip can identify fields that are not searchable.

Quick action: turn one very broad operational list into a focused view, then show the team where its search box and unsearchable-field tooltip are.

5. Stop searching repeatedly for repeat work

For users and managers: not every navigation problem needs another search. Lightning Experience surfaces recently searched items, navigation-item dropdowns and the Recent Records component. Favourites provide a direct route back to important pages and records.

Use these features for genuine repeat work: a manager's core dashboard, a queue view used every morning or a record involved in a short-running project. Avoid favouriting everything, because another uncurated list simply moves the findability problem.

Quick action: ask each user to favourite two high-frequency destinations and remove favourites that no longer support current work.

6. Diagnose a missing record before adding automation

For admins: when a user cannot find a record, reproduce the search with the same object, terms and access context. Check spelling, list filters, ownership, sharing, field-level security and whether the expected field is indexed. Also confirm that the record's identifying data is complete and consistent.

Salesforce documents a Flow-based workaround that copies otherwise unsearchable content into a custom text field, but warns teams to assess scale and search crowding. Treat that as a designed solution, not the first response. A new field and record-triggered Flow create data, testing and maintenance responsibilities; a better layout, clearer name or corrected access may solve the real issue more simply.

Quick action: add a short search-troubleshooting checklist to support requests so the team records the query, user, object and expected record before changing configuration.

Make findability part of everyday Salesforce care

Good search depends on more than the search box. Users need recognisable records, useful ways to narrow results, realistic expectations about indexed fields and dependable data. Improving one busy object can remove a surprisingly common source of friction without becoming a major project.

Ostrelis can help teams improve everyday Salesforce usability, administration and data quality. Explore our Salesforce administration service, managed Salesforce support and Salesforce health checks.