> For the complete documentation index, see [llms.txt](https://ac.docs.landis.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ac.docs.landis.cloud/daily-usage/call-history.md).

# Call History

{% hint style="info" %}
The Call History panel can be enabled under [Layout](/settings/layout.md)
{% endhint %}

This feature is [preview.](/appendix/feature-states.md)

The Call History panel displays information about past calls answered in this instance of Landis Attendant Console. 

There are two options for storing call history data:

1. **Local Storage (Default)** Call history is stored locally in the browser or application cache. When this option is used, missed calls and calls answered from other Landis Attendant Console instances or Microsoft Teams endpoints are not synchronized and will not be displayed.
2. **Landis Server Storage.** Call history is stored and synchronized through Landis servers. With this option enabled, missed calls and calls answered from any Landis Attendant Console instance are displayed across all connected instances. Enable this option by navigating to Settings > Advanced > Save and Sync Call History.

The historical call records will appear at the top of this panel and will be sorted from most to least recent. 

Calls handled in Attendant Console from the last 14 days will appear in this panel.

A call record can be selected, and more detail will appear in the bottom panel. See below:

{% tabs %}
{% tab title="Caller Info" %}

#### Caller Info

Caller information will appear at the top of this panel.

#### Notes

Notes about the caller can be viewed, edited, or added for future reference. By default, these notes are personal, but they also can be shared with multiple users.

To configure notes, see [Notes](/settings/contacts-settings.md#notes)
{% endtab %}

{% tab title="Closed Captions (Preview)" %}
The historical transcription of this call will be displayed in this area.  The text can be coped to the clipboard by selecting the clipboard button. To enable historical transcription, go to Settings | Advanced | enable Save Transcription to Local Call History.

{% hint style="info" %}
Real-time speech to text is required to be enabled for closed captions to function. Settings | Advanced | Call Settings | Enable Real-Time Speech to Text
{% endhint %}

{% endtab %}

{% tab title="AI Prompts (Preview)" %}
AI prompt history will appear on this tab. The response text can by copied by selecting the clipboard button. For more information, see [AI Prompts](/settings/ai-prompts.md)

{% hint style="info" %}
Real-time speech to text is required to be enabled for AI Prompt history to function. Settings | Advanced | Call Settings | Enable Real-Time Speech to Text
{% endhint %}

{% endtab %}
{% endtabs %}


---

# 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://ac.docs.landis.cloud/daily-usage/call-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.