> For the complete documentation index, see [llms.txt](https://docs.nalpeiron.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nalpeiron.com/zentitle2-docs/use-cases/use-case-directory/overuse-tracking-overdrafts.md). # Overuse tracking (overdrafts) Track overuse with Zentitle2's overdraft tracker, which lets customers exceed a purchased seat or usage limit up to a soft cap while flagging the extra usage for renewal or upsell conversations. {% embed url="" %} **The Overdraft tracker is a great way to grow sales. It provides an "evidence-based" approach for the sales team to discuss options with customers and upsell them to new revenue tiers (if that's your business model).**
If you have hard limits on paid licenses, as most vendors do, **you will never see any latent demand**. The overdraft tracker allows you to add a new limit to each license to enable the user to consume more up to a higher set limit (so you still control the overall usage). When users consume more than they paid for, they go into "Overdraft. " You can easily capture those users/entitlements in a report and use that at renewal time or for sales, in general, to contact your customers and sell them more based on your policies. It will also expose and capture license abuse while offering users "softer" policing. Softer policing is important, especially with business customers, as it avoids many issues associated with software license management and shows a level of trust in your customers. Nothing is more annoying to customers than just being locked out of their software, so Zentitle2 uses an automated ‘Overdraft’ tracker function to handle any “overuse.” Suppose someone within an organization exceeds the license limit. In that case, the entitlement is flagged along with the details necessary to enable sales staff to contact the entitlement user to find out more. You then have the choice of allowing the use to continue or asking for more license fees! The overdraft tracker allows you to add a seat or usage limit to each license, enabling the user to consume more up to a higher set limit (so you still control the overall usage). When users consume more than they paid for, they go into "Overdraft." You can easily capture those users/entitlements in a report and use that at renewal time or for sales, in general, to contact your customers and sell them more based on your policies. ### Overdraft use case explained You may have a customer who wants to purchase 100 seats of your application (whether SaaS or on-premises). Typically, the worst thing from an end customer's standpoint is being denied when they want to increase their usage, which we call a "hard enforcement" of those 100 seats. As a vendor, you want to encourage customers to use your software as much as possible; you want to get fairly paid for it. Overdraft licenses allow you to implement a soft limit. With 100 purchased seats, we can give feedback to customers about whether they're within their limit or starting to use overdraft licenses. We'll put a hard cap at 120 seats so they don't have unlimited access to your application. We can dynamically graph seat usage over time through our end-user portal. You can provide this capability to your customers to help them track usage and plan capacity. As usage fluctuates against the initial 100 seats, our APIs will indicate when overdraft licenses are used. This generates events through both APIs and webhooks, allowing you to handle notifications—perhaps sending emails to the account team or customer admin. If usage grows into those overdraft licenses, we'll still enforce the hard limit of 120 seats. Any attempt to activate a 121st seat will be denied, generating an event for automation. Customers can see how often they've been denied access through the end-user portal. If this happens frequently, they'll likely want to increase their capacity. Overdraft licenses foster the best working relationship between you and your end customer by selling them what they paid for, giving them room to grow, while maintaining control through a hard limit. {% hint style="success" %} Let's jump on a call and discuss how we can help, get in touch with your account manager today → [Setup a 1:1 discussion](https://www.nalpeiron.com/get-a-11-demo.html) {% endhint %} --- # 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.nalpeiron.com/zentitle2-docs/use-cases/use-case-directory/overuse-tracking-overdrafts.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.