> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/mobile-app/ios-outsmart-app/module-overviews/clients-relations/client-history.md).

# Client history

## Client history

Use **Client history** to review previous customer activity.

The screen can filter by customer, invoice, address, object, or project context.

### What you can do

* switch display types and filters
* review work-order and form history when both are enabled
* open a work order, PDF, or form from a history item

{% stepper %}
{% step %}

### Open **Client history**

Open the client record, then open **History**.
{% endstep %}

{% step %}

### Narrow the list

Use the available filters or display controls.

In work-order context, the screen can also show a filter menu.
{% endstep %}

{% step %}

### Open the item

Select a history entry to open its related content.
{% endstep %}
{% endstepper %}

### Keep in mind

History labels change with the active history type.

The segmented control only appears when multiple history views are enabled.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledge.out-smart.com/mobile-app/ios-outsmart-app/module-overviews/clients-relations/client-history.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.