Activity log
The audit trail: every send, every compliance check and every settings change, what a single row tells you and how far back it reaches.
Sidebar: Account → Activity log. Page heading: Every action, every check.
Every send that went through the compliance gate — and every settings change — in one audit trail. This is what makes "compliance-first" checkable rather than a claim.
Open to every role.
What a row tells you
Two kinds of row, kept visually distinct so they never blur.
Send rows
Format: "<source> sent a reply to <contact>" or "<source> failed to reach <contact>", with a status line underneath: status · channel · time ago.
Source is what produced the message:
| Label | Means |
|---|---|
| AI agent | The agent's own reply |
| You | A human reply typed in the Inbox |
| Automation | A flow message step |
| Scheduler | A resumed flow step |
| Follow-up | A nudge after an untapped link |
| Retry | A retried send |
| Sequence | A drip step |
| Broadcast | A broadcast |
| AI step | An AI Step node inside a flow |
| Dynamic block | A dynamic message block |
| system | An automatic acknowledgement — e.g. the confirmation sent when a customer texts STOP or START (shows lowercase in the log) |
Status is an honest three-rung ladder:
| Status | Means |
|---|---|
| sent | Instagram's API accepted the message |
| seen | The recipient actually opened it — strictly stronger than sent, so it stands in for it |
| failed | It did not reach them |
Settings rows
A different glyph and a plain-English summary of the change, tagged settings. Renaming the workspace, changing the timezone, pausing everything, flipping a channel — they all land here.
What it's for
Three real jobs:
- "Did that message actually send?" — find the contact, read the status.
- "Who changed this?" — settings rows record configuration changes.
- "Prove the AI didn't say something it shouldn't." — every send passed the gate, and blocked sends are counted in the Analytics trust row.
Scope
The log shows the most recent ~60 entries (sends and settings changes combined) for this workspace — a count limit, not a time window, so on a busy workspace older rows are pushed out quickly.
Empty state
"Nothing logged yet — once HyperDM starts replying, every sent and blocked message shows up here, alongside every settings change you make."
The button under it depends on your setup: Connect Instagram if you have not connected yet, Create an automation if you have.
Common questions
Why is a message "sent" but the customer says they didn't get it? "Sent" means Instagram accepted it. "Seen" means they opened it. If it stays at sent, the message was delivered to Instagram but not opened.
*Where do I see what was blocked? The Analytics Answered vs. held and Compliance activity cards, on every plan. See analytics.md. (A reply blocked by a guardrail* is recorded as a ⚠ note in that conversation in the Inbox instead — see agent-guardrails.md.)
Can I export it? Not from this page. Analytics has Export CSV for the metrics.
Does it show messages customers sent me? No — this is the outbound audit trail plus settings changes. Inbound conversations live in the Inbox.
More in Account & billing
- SettingsAll nine settings tabs: Channels, Main menu, Commerce, Billing & usage, Refer & earn, Team & roles, Workspace, Notifications and Security.Read
- Plans and billingEvery plan and what it includes, what each gate actually does, how overage protection works, and how to upgrade, downgrade or pause billing.Read
- Roles and permissionsThe four workspace roles, what each may do, what you see instead of a control you lack, inviting teammates and how seats are counted.Read
Try HyperDM for free
50 free conversations a month, no card. Connect Instagram and follow the guide you just read.