> 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` 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 optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.