Conversation history on the contact card
Two views — automation sessions and full history. Every line on a session card, how paging works, and why some sessions drop off the list.
Last updated: September 30, 2026
Two views — automation sessions and full history. Every line on a session card, how paging works, and why some sessions drop off the list.
Last updated: September 30, 2026
When a customer asks "what did you write to me last month?", or when you want to understand why an automation took the wrong branch, scrolling down the contact card is enough. The Conversation history section shows all the messaging with that person and every automation session that ran on them, in one place. This guide covers the two views, every line on a session card, and the limits of the history.
💡 This section may not be drawn on every account: it depends on your plan and your permission. And you cannot read the history of a conversation you could not open in the inbox — both screens pass through the same gate.
In this article you will find:
Two tabs sit under the section's heading:
Clicking a tab does not jump to the top of the page; it lands on the history section. The tab you chose is kept in the address bar, so you can share the address of the view you found.
If no automation has ever run for the person and you have not picked a tab yourself, the section opens Full history directly: you never land on an empty tab. If the sessions view is switched off on your account, the tab strip is not drawn at all and the full history is always shown.
This view shows all the messaging with the person using the same bubbles as the inbox. Here the bubbles are read-only: you cannot write a reply or retry a message that failed to send. To reply, use the Open conversation button in the header.
Paging works by two rules, and the one-line note above the section says so:
Each page holds 40 messages. Use the page numbers to go further back.
If there is no messaging at all it says "No messages with this contact yet." That is normal for people who arrived from an ad or a comment and never exchanged a message.
A session is one run of one automation on this person. If the person triggered the same flow three times, you see three session cards.
Cards start closed and open when you tap them. Closed, each card shows:
Each page holds 10 sessions; because every card also carries its own messages and steps, the page is deliberately kept small.
If there are no sessions it says "No automation has run for this contact yet."
Opening a card reveals:
If a session has very many steps, only the first part is drawn on the card and a line below says so; the whole log lives on the Session log screen. A card shows at most 200 steps.
Knowing this detail helps you read the messages on a card correctly:
The reason is the order of events: the person's message is saved first, then the automation starts. So it is normal for the message that started a session to sit slightly before it, and the matching therefore begins a little earlier. The lower bound is cut off at the end of the previous session, so two sessions never claim the same message.
The explanatory line under the cards states this on screen too.
The history section is not drawn when:
The Automation sessions tab can also be switched off separately: in that case only the full history is shown.
A cosmetics brand resolves a "the customer got the wrong message" complaint like this:
vip tag, the flow went down the standard branch.vip tag is added in the Details section of the person's card, and the next time the flow takes the right branch.Five minutes turn a suspected broken automation into a missing tag.
If the history section does not appear at all, check your permission and your plan, then get in touch with our Support team.
Was this article helpful?