Hello Alex Docs

SMS History Overview

Track conversations, response flow, and per-thread delivery state. Read the SMS History guide in Hello Alex documentation.

Overview

SMS History shows message continuity per contact, which helps teams evaluate engagement and resolve delivery issues.

Conversation lists provide quick visibility into active and recent threads by contact and line.
Thread details show full message timelines and status transitions so troubleshooting and follow-up decisions are evidence-driven.
Threads are paged twenty-five at a time with numbered pages, the same way call history is paged, so a long list can be jumped through rather than scrolled.

Good to know: thread context is most useful when reviewed alongside campaign or batch metadata.

Conversation lists surface workload and engagement at a glance.

Open threads tied to active campaigns and confirm initial response quality.

Each row represents a contact thread, making queue scanning and prioritization straightforward.
Opening a thread reveals detail needed for follow-up and resolution.
Line: Outbound SMS number for the thread.
Good to know: batch sends naturally expand the thread list, so line filters help keep review focused.
High-volume thread triage
Line-level engagement review

Thread-level history explains how contacts respond over time and where delivery or logic breaks occur.

Inspect failed or stalled threads and decide whether reroute, retry, or manual follow-up is needed.

Inbound and outbound messages are presented chronologically, preserving context for support and sales workflows.
Delivery indicators show whether failures are content, carrier, or recipient-side related.
Delivery: Sent, delivered, or failed states.
Good to know: preserving thread continuity improves human handoff quality when agents step in.
Failed delivery diagnosis
Conversation quality review

The filters the call history uses, applied to threads, with the same export beside them.

Filter to the campaign you last sent, read the threads that replied, then export the range.

Search matches a phone number, a contact name, or a conversation ID.
Active and History separate the threads still in play from the threads that are finished.
Changing a filter returns you to page one, so the count and the page always describe the same thing.
Export takes a date range, the threads you ticked, or only the page on screen.
Date range: Today, yesterday, the last 7, 30 or 90 days, or two dates you choose.
Status: Where the thread stands -- delivered, failed, or waiting on a reply.
Pathway: Threads on one pathway, on any pathway, or on none.
Campaign: Threads a batch send started.
Sort: Newest first, oldest first, or the threads carrying the most messages.
Export scope: A date range, the threads you ticked, or the current page. The file carries phone, direction, message count, the last message and its time, pathway, campaign, status and cost.
Good to know: a batch send adds one thread per recipient, so filtering by that campaign is the only comfortable way to review it.
Good to know: the export holds each thread's last message, not the whole conversation. Open a thread for the full exchange.
Reviewing a batch send
Reply-rate reporting
Finding one conversation from a number

Review recent high-value threads and confirm delivery plus reply patterns before the next send window.