> ## Documentation Index > Fetch the complete documentation index at: https://docs-old.aisync.link/llms.txt > Use this file to discover all available pages before exploring further. # Dispositions & Pipeline Mapping > How call outcomes move leads through stages, why new dispositions do not move anything, and what to do about it. This is the part of setup that quietly fails. Everything looks configured, reps dial happily, and a week later the client asks why nothing is moving in their pipeline. **Read this before you add a disposition.** The link between a disposition and a pipeline stage is built **once, when the company account is created**. Adding a disposition afterwards does **not** create a link, no matter what you call it. The rep can pick it, the call saves, and the lead never moves. This is a current product limitation, not a setup mistake you can fix by renaming things. *** ## ๐Ÿงฉ How the pieces actually connect What the **rep picks** at the end of a call. "Not Interested", "App Set", "Call Back". Where the **lead sits** in the sales process. "New Lead", "Contacted", "Appointment Set". A **saved rule** created at signup that ties one specific disposition to one specific stage. Not the name. ```mermaid theme={null} graph TB A[๐Ÿข Company account created] --> B[๐Ÿ“‹ Six dispositions created] A --> C[๐Ÿ—‚๏ธ Six matching stages created] B --> D[๐Ÿ”— Rules built, pairing each one to a stage] C --> D D --> E[โœ… Rep picks a disposition โ†’ lead moves] F[โž• A disposition added later] -.->|no rule is built| G[โฌœ Rep picks it โ†’ nothing moves] style E fill:#1f7a4d,color:#fff style G fill:#a33,color:#fff style D fill:#2a4d7a,color:#fff ``` Because the starter dispositions and stages are created together with the same names, it **looks** as though names are what connect them. They are not. The names match by coincidence of setup, and renaming either one does not break anything. *** ## โœ… What this means in practice The link survives a rename. If a client wants "App Set" to read "Appointment Booked", change it. Leads keep moving exactly as before. This is the opposite of what you might expect, and the opposite of what earlier versions of this guide said. It will appear for reps, save correctly, and show in reports. It just will not move the lead to a stage, because no rule exists for it. **What to do:** use it for reporting and move those leads by hand, or raise it with support so the mapping can be built for that client. Same reason. Existing rules point at the stages that already existed. The rule refers to a disposition that no longer exists, so nothing happens when its replacement is chosen. Prefer renaming over deleting. *** ## ๐Ÿงช How to check a client is actually wired up Do not trust the screen. Test it. Any contact you can safely move. Note which stage it is in now. Use one of the outcome dispositions, not Didn't Answer. It should be in the matching stage within a few seconds. The disposition has no rule behind it. That is the limitation above, not something you can fix by renaming. Raise it with support. Do this once per client during onboarding, with one disposition. It takes two minutes and it is the only way to know the wiring is real. *** ## โœ๏ธ Setting up dispositions Build the disposition list first. The pipeline is shaped to match it. If they say "DQ" rather than "Not Qualified", call it DQ. Reps pick the right option faster when it sounds like how they talk. Renaming the starter dispositions is safe and is the recommended way to customise. Six to ten is healthy. A rep scanning twenty options mid-call picks whatever is nearest, and your reporting becomes fiction. One disposition is wired to the **Didn't Answer** button. Set it with the **Didn't Answer** action on the Dispositions screen โ€” not the separate default option setting, which controls something else. "App Set", "Appointment Set", whatever they call it. This is the one that matters most for reporting. Full screen reference: [Dispositions](/manage/disposition). *** ## ๐Ÿ—‚๏ธ Setting up the pipeline Renaming is safe and keeps the links intact. Left to right should read like the real sales process. Every pipeline has one. Check it exists and sits where the client expects it. Full screen reference: [Pipelines](/pipeline/pipeline). **"Didn't Answer" deliberately does not move a lead.** Someone who did not pick up has not progressed, and moving them would make the pipeline meaningless. They stay where they are and remain in the calling rotation. *** ## ๐Ÿฉบ When leads are not moving Run the test above. If a starter disposition moves a lead and a newer one does not, you have hit the limitation โ€” the newer one has no rule behind it. Check whether a disposition or stage was **deleted** and recreated. A recreated one is a new record with no rule attached, even with an identical name. Expected if dispositions were added after signup. The originals work; the added ones do not. Check which pipeline it landed in. A client with several pipelines has rules pointing at one of them. *** ## โžก๏ธ Where to go next The full runbook this page belongs to. Organised by what the customer tells you. Every field on the screen. Stages and how to order them. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.