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

# Closing the Loop

> When work ships, the customers who asked for it hear back automatically — in the same place they raised it.

The hardest part of the feedback loop is the last step: telling customers you actually built the thing they asked for. It's the step that gets skipped, and skipping it is why customers stop bothering to give feedback. Closing the loop makes that step automatic — when a [Plan](/docs) ships, the people behind it are told, in the channel where they first spoke up. Nobody has to remember, and nobody has to keep a list.

## How it works

Closing the loop rides on two things you already have: a Plan's **committed feedback** and its **status**.

1. A Plan commits the specific pieces of [Feedback](/insights) it answers — each of which remembers its source and the customer behind it.
2. You pick the Plan **status** that means "shipped" for each connected tool.
3. When the Plan reaches that status, Lane reaches back to the source of every committed piece of feedback — automatically.

Because it's driven by Plan status, closing the loop fits your real workflow: the moment you mark the work delivered, the outreach happens.

## What Lane sends, by source

The outreach matches where the feedback came from:

* **Slack** — Lane replies in the original thread where the feedback was raised, so the customer or teammate sees it in context.
* **Intercom** — Lane adds an internal note to the conversation, so your support team can pass the update along.
* **[Zendesk](/zendesk)** — Lane adds an internal note to the ticket, and can optionally **reopen** a solved ticket so the update doesn't go unnoticed.

Each integration lets you choose the trigger status from your Plan statuses, so "shipped" means whatever your team decides it means.

## Setting it up

Closing the loop is configured per integration, in each connector's settings — connect the tool, then choose the Plan status that triggers the outreach. See [Slack](/slack), [Intercom](/intercom), and Zendesk for the specifics. It's available on **Pro and above**.

## FAQs

**Q: What triggers the outreach?**\
A: A Plan reaching the status you've designated as shipped for that integration. It's tied to Plan status, not to any individual feedback item's status.

**Q: Which feedback gets a reply?**\
A: The feedback a Plan has committed — the specific requests it set out to answer. Each is contacted at its original source.

**Q: Can I control exactly when it fires?**\
A: Yes — you choose the trigger status per integration, so the loop closes on the exact stage that means "done" for your team.

**Q: Does it post publicly to customers?**\
A: It depends on the source: Slack replies in the original thread, while Intercom and Zendesk add internal notes for your team to relay — with an optional ticket reopen in Zendesk.