> ## Documentation Index
> Fetch the complete documentation index at: https://docs.woes.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Create an Update

> Create, schedule, publish, and archive widget updates for customers.

# Create an Update

A good update is specific, useful, and tied to something customers need to know
while they are asking for support.

## Required Content

| Field       | Use it for                                                                         |
| ----------- | ---------------------------------------------------------------------------------- |
| Title       | The product area, change, or action required.                                      |
| Body        | A short explanation of what changed and who is affected.                           |
| Audience    | Whether everyone or verified customers should see it.                              |
| Target      | The workspace or agent/widget surface where the update should appear.              |
| CTA         | Optional link to docs, release notes, a migration guide, or the relevant app page. |
| Cover image | Optional visual context for the update.                                            |
| Expiry      | Optional date after which the update should no longer appear.                      |

## Lifecycle

| State     | Meaning                                                           |
| --------- | ----------------------------------------------------------------- |
| Draft     | Saved internally but not visible to customers.                    |
| Scheduled | Ready to publish at a future time.                                |
| Published | Visible in eligible widget Updates tabs.                          |
| Archived  | Removed from active customer visibility while preserving history. |

## Publishing Checklist

* The widget Updates tab is enabled for the intended surface.
* The target agent/widget is correct.
* The audience matches the customer trust level.
* The update has no internal notes, customer-private data, or secrets.
* Links point to public or customer-safe destinations.
* Operators know how to answer follow-up questions in Inbox.

<Warning>
  Updates are customer-visible. Do not use them for private incident notes,
  unreleased commitments, credentials, or account-specific support details.
</Warning>