> For the complete documentation index, see [llms.txt](https://threadly.gitbook.io/threadly/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://threadly.gitbook.io/threadly/sending-messages/message-acknowledgements.md).

# Message Acknowledgements

**Acknowledgements** are an optional button you can add to any Threadly message that requires recipients to explicitly confirm they've read it. Unlike a CTA link or form, the acknowledgement button records a simple "I've read this" response — tracked per user, per message.

{% hint style="info" %}
Acknowledgements are a **Premium** feature.
{% endhint %}

***

## When to Use Acknowledgements

Acknowledgements are ideal whenever you need proof of receipt, not just delivery:

* **Policy updates** — confirm employees have read and acknowledged a new policy
* **Compliance notices** — verify that required disclosures were seen
* **Onboarding checklists** — prompt new hires to confirm each step
* **Critical announcements** — know who has seen a time-sensitive message
* **Training materials** — mark that a training resource was received and read

***

## How to Add an Acknowledgement

1. In the Threadly message composer, click **Add Action**.
2. Select **Acknowledgement** from the action types.
3. Optionally customize the button label — the default is "I've read this".
4. Compose the rest of your message and send.

Recipients will see the acknowledgement button appear beneath your message in Slack. Clicking it records their response instantly.

***

## What Recipients See

Recipients see a button beneath your message in Slack. Once they click it:

* The button updates with a visual confirmation
* Their name and timestamp are recorded in Threadly’s analytics
* The button cannot be clicked a second time (one acknowledgement per user)

***

## Viewing Acknowledgement Data

1. Go to the **Logs** tab in Threadly.
2. Select the message.
3. Click the **Acknowledgements** view to see who has and hasn’t responded.

| View                                | Free | Premium |
| ----------------------------------- | ---- | ------- |
| Total acknowledgement count         | ✓    | ✓       |
| Individual user acknowledgements    | ✕    | ✓       |
| Timestamp per user                  | ✕    | ✓       |
| Pending (not yet acknowledged) list | ✕    | ✓       |

***

## Tips

* **Pair with a workflow** — use a scheduled workflow to follow up with users who haven’t acknowledged within 24–48 hours
* **Export for compliance** — download acknowledgement analytics as CSV from the Logs view to maintain an auditable record
* **Combine with other actions** — an acknowledgement button can coexist with CTA buttons and forms in the same message

***

## See Also

* [Using Logs & Analytics](/threadly/analytics/using-logs-and-analytics.md) — navigate the analytics dashboard
* [How Threadly Tracks Responses](/threadly/analytics/how-threadly-tracks-responses.md) — form submission tracking
* [How to Send a Message with Threadly](/threadly/sending-messages/how-to-send-a-message-with-threadly.md) — full send guide


---

# 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://threadly.gitbook.io/threadly/sending-messages/message-acknowledgements.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.