> For the complete documentation index, see [llms.txt](https://help.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.distro.so/routing-rules/distribution-rules/distribution-history.md). # Distribution history Use **Distribution History** from a distribution rule's actions to review assignments across its teammates. Click Routers have their own distribution history for fallback assignments. Review the assignment counts, booking outcomes, weights, and available credits together. A booked-meeting total alone does not explain a member's position in the next assignment: repeat prospects, credits, vacation handling, and the configured reset period also matter. Admins can open a member's credit control, adjust the non-negative credit balance, and click **Save**. A credit gives priority in a future eligible assignment; it is not a booking or a reserved time. Review the current balance before changing it. Use [Calibration](/settings/workspace-settings/calibration.md) for automatic compensation and reset frequency. For an individual prospect, open the router's **Routing Logs** to inspect the attempt and its result. --- # 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://help.distro.so/routing-rules/distribution-rules/distribution-history.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.