> 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/renewals-customer-success-management.md). # Renewals (Customer Success) Management Use Zentitle's usage history as an early warning system for renewal conversations, spotting declining, overdraft, or growing accounts before contracts come up for renewal. {% embed url="" %} One of the key aspects in any software company's business is handling renewals and getting clear visibility into how customers are using the licenses you sold them a year ago. Zen Title can be a renewals team's best friend by acting as an early warning indicator. For example, let's say you sold a customer 100 concurrent seats. By analyzing their usage over the past 6–12 months, you may notice that they initially used almost full capacity, but usage has declined over time. This early warning signal suggests you may face challenges at renewal time—will they renew at all, or reduce their seat count? Having good visibility well ahead of renewal is critically important. On the other hand, you may identify customers who make additional use through overdraft licenses, exceeding their authorized amount. This historical data becomes valuable input for renewal conversations: "It looks like you're making great use of the software above capacity—shall we renew at 120 or 150 licenses?" Similarly, with brand-new accounts that may start small with just 20 seats, you can expect consistent growth over time. This demonstrates better penetration into the account—more usage, more time spent, and greater value derived from the software. This enables fact-based conversations about increasing their seat count at renewal. You can even provide these same visualizations to your customers through our end-user portal. This allows them to analyze their own usage and recognize when they're growing beyond their purchased licenses, helping them budget for a higher tier next time. This makes Zen Title and renewals a perfect match, arming you with clear usage trends to inform your renewal conversations. [See our Zengain "Retain" module for churn prevention](https://docs.nalpeiron.com/zengain-docs/welcome/introduction-to-zengain). --- # 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/renewals-customer-success-management.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.