History and insights
History search and filters
History filters narrow the completed-conversation record by responder, member scope, site, visitor contact, label, date, and transcript text.
- Availability
- All plans
- Configured in
- Dashboard → History → filter bar above the conversation list
- Category
- History and insights
- Reference status
- Current
How filtering works
Each control contributes to one active result set. Stand combines the selected criteria, refreshes the list, and uses the same result definition when preparing a bulk JSON export.
Clear filters returns to all responder types, the member’s default scope, all sites, all visitors, all labels, no date boundaries, and no text query.
Available filters
| Control | Values or behavior |
|---|---|
| Handled by | All, Human, or AI. |
| Scope | Mine or Team; Team is available to owners. |
| Site | All sites or one site represented in the accessible results. |
| Visitor | All visitors, Has email, Has phone, or Any contact. |
| Label | All labels or one available conversation label. |
| From / To | Inclusive calendar boundaries for the result period. |
| Search | Text query applied to searchable conversation content and metadata. |
Result behavior
- The result count updates with the active filters.
- Results are paginated and can be sorted through the History grid controls.
- Selecting a result opens the conversation detail while keeping the current filter context.
- Text input is normalized and debounced before the request so every keystroke does not start a new search.
Relationship to export
The download action exports all conversations matching the current filters, not merely the rows visible on the current page. Stand preserves the filter state while the browser starts the download so the user can return to the same result set.
Scope and interpretation
- Mine and Team describe member access scope, not whether a human or AI handled the conversation.
- Contact filters reflect captured email or phone data; page-known visitor identity is a separate field.
- Date boundaries and reporting periods should not be assumed to match a user’s local timezone without checking the displayed context.
- A label filter matches applied conversation labels; it does not rerun the signal definition against old conversations.
Example
The screen below shows the feature in its normal Stand context. Labels and surrounding controls may vary with account state and plan.
