For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
DashboardGet an API key
SetupCustomersOnboardingsWorkbenchAsk PiIntegrations
SetupCustomersOnboardingsWorkbenchAsk PiIntegrations
  • Customers
    • Overview
    • Add a customer
    • Edit customer details
    • Health score
    • At risk and churned
    • Add contacts
    • Manage contacts
    • Search customers
    • Tags and metadata
    • Customer history
LogoLogo
DashboardGet an API key
On this page
  • How the matching works
  • Worked examples
  • What ⌘K does not search
  • The gotcha: stale custom field values
  • Related
Customers

Search customers

⌘K from anywhere, plus the query syntax that turns search into a quick filter.

|View as Markdown|Open in Claude|
Was this page helpful?
Previous

Manage contacts

Next

Tags and metadata

Built with

Press ⌘K (or Ctrl+K on Windows and Linux) anywhere in the app to open Workbench search. The cursor lands in an empty input. Start typing and Pivotal queries name, domain, contact emails, and any custom field you’ve configured. Results appear under headed groups (Customers, Onboardings, Tasks, Contacts) so you can tell what kind of record you’re about to open. Hit Enter on the first result or arrow down to pick another.

How the matching works

By default, search does a case-insensitive substring match on every searchable field. Type acme and you’ll get Acme Co, acme.com, and jeff@acme.com. Type gro and you’ll catch every customer on the Growth plan plus anything with gro in the name.

Three operators sharpen that:

  • Quoted strings match exactly. "Acme Co" won’t match Acme Corporation. Use this when a short string is showing up everywhere.
  • field:value filters on a custom field. region:emea returns customers whose region custom field has the value emea. The field name comes from your custom field configuration.
  • -term excludes. acme -churned matches “acme” and drops anything with churned anywhere in the indexed fields. Combine with field:value for things like plan:enterprise -region:emea.

Worked examples

QueryWhat it finds
acmeAnything containing “acme” in name, domain, emails, custom fields
"Northwind"Exact match on the string “Northwind”
plan:EnterpriseAll customers with plan set to Enterprise
domain:.ioCustomers on .io domains
region:emea owner:meEMEA customers you own
at_risk -archivedAt-risk customers that aren’t archived

owner:me is a shortcut for your user. Use owner:<full-name> to filter by a teammate.

What ⌘K does not search

Search hits the Customer record and its Contacts. It does not search the body of task descriptions, comments, or activity-feed entries. For those, use the dedicated Workbench search page, which has a wider index and supports date-range filters.

The gotcha: stale custom field values

The search index updates within a minute of most edits, but bulk edits that touch hundreds of records can take a few minutes to reflect. If you ran a bulk update and a field:value query is still showing old results, give it five minutes before assuming something’s broken.

Related

  • Tags and metadata
  • Filters and views
  • Workbench search

Email help@pivotal.app with a screenshot of where you got stuck and the customer or onboarding id from the URL.