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

# Close the Loop and Assign Journey Owners

> Route journey signals to a journey owner, track each case to recovery, and keep journeys owned over time.

Route journey signals to a journey owner, track each case through closed-loop tracking, and keep journeys owned over time.

## Purpose

A signal changes a journey only when it leads to action. Closed-loop tracking records what was done and whether the customer recovered; a journey owner stays accountable for the journey's end-to-end performance. Together they keep journeys from decaying into static artifacts. It lets you:

* Get each detection signal to the person who can act on it
* Turn a pattern register into tracked outer loop tickets
* Record both what customers said and what was done (closed-loop tracking)
* Keep every journey under an owner with a review cadence (journey governance)

## Formbricks Approach

* [Webhooks](/platform/features/integrations/webhooks) to push signals into your warehouse, journey tool, or a custom service
* [Native integrations](/platform/features/integrations/overview) to route into Slack, a CRM, or an issue tracker with no code
* [Feedback Records](/unify-feedback/feedback-records) to log the action taken and the recovery outcome
* [Feedback Directories](/unify-feedback/feedback-directories) per journey so the journey owner has one place to review