> ## 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.

# Closing the Loop

> Use Woes to follow up when product work, docs fixes, or support issues are resolved.

# Closing the Loop

Closing the loop means telling customers when their problem, request, or docs
gap has been addressed. It turns support work into trust.

## What To Close

* Issues created from customer conversations.
* Documentation gaps that caused confusion.
* API behavior changes customers asked about.
* Feature requests that shipped or were declined.
* Workarounds that are no longer needed.

## Loop Workflow

<Steps>
  <Step title="Resolve the underlying work">
    Confirm the product, docs, or support process changed.
  </Step>

  <Step title="Update the issue">
    Move the issue to the correct status and add a clear internal note.
  </Step>

  <Step title="Refresh context">
    Rescan docs or source context if the agent should know the new behavior.
  </Step>

  <Step title="Notify affected customers">
    Reply in the original conversation, update the portal item, or publish an approved widget Update.
  </Step>

  <Step title="Measure the result">
    Watch future questions, issue volume, and survey results for the same topic.
  </Step>
</Steps>

## Good Follow-Up Messages

* State what changed.
* Link to updated docs when available.
* Explain whether action is required.
* Avoid overpromising future work.
* Offer a clear next step if the customer is still blocked.