> For the complete documentation index, see [llms.txt](https://docs.spara.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spara.com/scout/how-scout-works/jobs/stalled-deals.md). # Stalled deals Scout finds the deals in your pipeline that stopped moving and drafts the check-in for each. Deals stall quietly. A stakeholder stops replying, a next step never gets booked, and the deal sits in the same stage until it's too late. Scout finds those deals and drafts the check-in that gets each one moving again. **Offered** once your CRM is connected, with a real result from your own pipeline. Say yes to keep it running. See [HubSpot](/scout/connections/hubspot.md) and [Salesforce](/scout/connections/salesforce.md). ## What it does * **Finds deals that haven't moved**: open deals with no activity or stage change for longer than they should, judged against your pipeline, not a fixed number of days. * **Works out why**, from the thread in your inbox and the notes in your CRM: an unanswered question, a missing stakeholder, a budget that slipped. * **Drafts the check-in** to the right person, picking up where you left off rather than restarting the pitch. ## Tuning it Tell Scout which stages or deal sizes to watch, how long is too long, or which accounts to leave alone, and it updates the job. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.spara.com/scout/how-scout-works/jobs/stalled-deals.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.