> ## Documentation Index
> Fetch the complete documentation index at: https://docs.waterfall.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Prospector multiple title filters

> Use ordered `title_filters` arrays for fallback targeting.

Use `title_filters` when you need multiple prioritized filter strategies.

<Info>
  Waterfall tries filters in the provided order until it reaches the requested `limit`.
</Info>

```json theme={null}
"title_filters": [
  { "name": "ceo level", "filter": "ceo OR founder OR owner" },
  { "name": "sales", "filter": "revenue OR growth OR sales" },
  { "name": "marketing", "filter": "marketing OR operations" }
]
```

## Guidance

* Put highest-value persona first.
* Keep filter names human-readable for debugging.

## title\_lists — exact title matching

Use `title_lists` when you have a curated set of exact titles rather than a boolean expression. Each entry in `titles` is matched exactly against the contact's title.

```json theme={null}
"title_lists": [
  { "name": "founders", "titles": ["Founder", "Co-Founder", "CEO"] },
  { "name": "sales", "titles": ["VP of Sales", "Head of Sales", "Director of Sales"] }
]
```

Up to 5 lists per request. Lists are evaluated in order — same priority behavior as `title_filters`.

**`title_filters` vs `title_lists`**

|             | `title_filters`              | `title_lists`                |
| ----------- | ---------------------------- | ---------------------------- |
| Matching    | Boolean / keyword expression | Exact title string           |
| Flexibility | High — catches variations    | Low — must match precisely   |
| Best for    | Broad persona targeting      | Known, controlled title sets |

Only one of `title_filter`, `title_filters`, or `title_lists` is used per request — they are mutually exclusive.