---
title: "Conversation history"
description: "Page through messages, events, activity, and transcripts in deterministic order."
image: "https://help.tidymessages.com/og.svg"
---

> Documentation Index
> Fetch the complete documentation index at: https://help.tidymessages.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Conversation history

Page through messages, events, activity, and transcripts in deterministic order.

## How it works

Page through messages, events, activity, and transcripts in deterministic order. TidyMessages keeps channel-specific behavior explicit while providing stable identifiers, safe retries, and auditable lifecycle events.

## Set it up

1. Choose the sending identity, conversation, channel, and environment.
2. Check capability, consent, current state, and channel policy.
3. Use an idempotent request and verify the resulting event history.

## What to expect

- The operation is traceable by stable request and resource identifiers.
- Acceptance, provider delivery, and customer interaction remain separate states.
- Retries and reordered events do not duplicate the customer action.
> [!TIP] Keep API keys, signing secrets, customer addresses, and message bodies out of source and logs.

Source: https://help.tidymessages.com/chats/conversation-history/index.mdx