Head into every renewal with a brief that pulls together account health, usage trends, and support history, plus the talking points and risks to walk in with, so the conversation is a foregone conclusion, not a coin flip.
Prepare a renewal prep brief for [account], whose contract renews in [timeframe]: pull account health, usage trends, and support history, and give me the talking points and risks to walk in with, using our account records in the Knowledge Center.
Un esempio illustrativo: il tuo risultato dipenderà dalle tue fonti, dai tuoi dati e dalle tue richieste.
I pulled this from Brightwave Retail's usage records, the support log, and the last two QBR notes in the Knowledge Center. The account is in good shape, with one open thread worth closing before the renewal call.
This is a healthy renewal with room to grow. Usage is up year over year, satisfaction is solid, and there's a clean case for the expansion you floated in Q2. The one caution is a billing dispute that's still open. Settle it before the renewal conversation so it doesn't become the whole conversation.
| Signal | Where it stands |
|---|---|
| Overall health | Strong and steady |
| Active users | 96 of 110 seats, up from 71 a year ago |
| Weekly active use | 68%, trending up since February |
| Support | No open product tickets; one billing dispute open 9 days |
Talking points to lead with.
Risks to get ahead of.
Where to take it. Renew at current terms as the floor, then make the expansion case for the two new regions (roughly 20 added seats) while adoption is trending up. Close the billing item first so the conversation starts on the value, not the invoice.
Want me to draft the expansion proposal for the two new regions, or talking points for the billing conversation with their finance contact?
Renewal Prep Brief assembles the picture you need before a renewal conversation from the account records in your Knowledge Center: health, usage trends, support history, the value you've delivered, and the risks worth naming. You ask once and get a brief that tells you where you stand and what to say.
Add usage data, support history, QBR notes, and the contract terms to the Knowledge Center, or connect where you keep them. Joy reads them at ask time.
Tell Joy which account is up and when it renews, plus anything specific: an expansion you want to test, a past escalation you're wary of.
Joy returns account health, the usage trend, support history, the value delivered, and the risks to watch (each tied to a source), along with suggested talking points.
Copy the brief into your renewal notes, your account plan, or a message to the team. Joy drafts the text; you run the conversation.
Save this ask as a custom command on the assistant your team already uses, so anyone can run it in one step.
A plain-language view of where the account stands and which way it's trending into the renewal.
Whether adoption is climbing or slipping, and which teams are driving or dragging it.
Open tickets, past escalations, and anything that could resurface in the conversation.
The value delivered and the case to make, ordered so you lead with your strongest ground.
Lead with adoption momentum and the next-tier use cases worth putting on the table.
Center the brief on churn signals, the recovery plan, and the concessions worth considering.
Frame the value delivered to date and the case for a longer commitment.
Assemble the usage evidence and outcomes a buyer will want before they sign off.
Ask Joy to prepare a renewal prep brief for the account. It assembles account health, usage trends, support history, the value delivered, and the risks to watch from your connected records, so you know exactly where the renewal stands before you dial in.
A plain-language health read, the usage trend, support and escalation history, the value delivered to date, suggested talking points, and the risks worth naming, each grounded in the sources you connect.
Only from your connected sources: usage and health data, support history, QBR notes, and contract terms in your Knowledge Center. Joy reads them at ask time; it doesn't invent numbers or pull from outside your records.
It surfaces the signals (slipping usage, open escalations, single-threaded relationships) so you can judge risk with the full picture in front of you. You decide how to act; Joy assembles the evidence.
No. Joy drafts the brief as text in chat. You review it and copy what you need into your renewal notes, account plan, or a message to your team. Any updates to systems stay in your hands.
Iscriviti alla lista d'attesa e sii tra i primi a provare questo workflow quando JoySuite sarà lanciato.