Why it matters
AI filtering helps users build useful contact audiences without knowing every available field or condition. It is most effective when users describe the audience clearly and then verify the generated rules before taking action.
Key Concepts
AI Filter Builder: The AI-assisted option in the Contacts filter panel for describing the audience you want in natural language.
Prompt: The plain-language instruction entered into the filter panel, such as finding contacts with birthdays today or excluding unsubscribed contacts.
Generated rules: The filter conditions created from the prompt. These should be reviewed before exporting, messaging, or saving the audience.
Segment: A saved version of the filter that updates automatically as matching contact data changes.
Step-by-Step: Create an AI-assisted contact filter
Open Contacts from the main sidebar.
Select All contacts.
Select Filter above the contacts table.
Choose AI filter or use the prompt field at the top of the filter panel.
Describe the contacts you are looking for using specific fields, statuses, dates, tags, lists, or communication preferences.
Review the generated filter rules.
Apply the filter and check the matching contacts in the table.
Select Save as segment when the audience should be reused.
Tips and Best Practices
Ask for one audience at a time so the generated rules are easier to review.
Use exact terms from Whippy when you know them, such as tags, list names, birthdays, or unsubscribed status.
Check the final contact list before exporting or messaging the audience.
Use manual filter conditions when a compliance-critical audience must be built from exact known rules.
Troubleshooting
Issue | Possible Cause | Fix |
The AI result is too broad | The prompt did not include enough field or status detail | Add specific criteria such as tag names, list names, dates, channels, or subscription status |
The AI result is too narrow | The prompt includes too many constraints or a field that is not populated | Remove one requirement and confirm the underlying contact data exists |
The AI filter uses the wrong field | Similar fields or object properties exist in the workspace | Edit the generated rule manually or rewrite the prompt with the exact field name |