> ## Documentation Index
> Fetch the complete documentation index at: https://docs.palantrix.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Feedback Loops
> Capture what happened in real conversations, and feed it back into preparation.
Practice is only half of it. The other half is what actually happened in the room, and that knowledge usually stays in one person's head or in a CRM note nobody reads.
Feedback Loops close that gap. After a real conversation takes place, Palantrix sends a short message in Slack or Microsoft Teams asking how it went, and what comes back feeds straight into the Client Digital Twin.
**How it works**
Once a conversation has happened, Palantrix messages the person who took part. The questions are short and specific: what came up, which objections were raised, what the customer pushed on, what's happening next.
It takes a minute to answer, in the tool your team already has open. That's the point. A form in a separate system gets filled in for the first week and abandoned by the third.
**What happens to the answers**
They go back into the Client Digital Twin for that contact. The next person preparing for that customer starts from a better picture than the last one did.
Over time this changes what practice conversations look like. If a client has raised the same objection in three meetings, it turns up in the rehearsal. If a new decision maker has appeared, the next person preparing knows about them.
**Why it matters**
Most organisations lose this information twice over. Once when it isn't written down, and again when the person who knew it moves on or leaves.
Feedback Loops turn each real conversation into something the whole team benefits from, without asking anyone to write a report.
**Setting it up**
Connect Slack or Microsoft Teams from Settings. Available on all plans, including free.
You choose when the follow-up is sent, and who receives it. If nobody responds, Palantrix sends one reminder and then leaves it. It won't chase.
### Quick Tips
Record what happened, not how you found the person. Note the questions they asked, the objections they raised and the points they wanted to dig into. "Asked twice about implementation timelines and wanted them in writing" is useful to whoever prepares next. "Hard work" is not.