Product

Which renewals are at risk, and why?

TellStay answers it for every account in your book, with the evidence attached. Here is every screen your team works it in: the portfolio and each CSM’s My book, Account 360, health scoring, the Renewal Room, AI signals and briefs, the executive forecast, TAM config checks, expansion and call prep. Every screen below is live and clickable, with sample data.

01 · My book and Portfolio

You see the whole book. Each CSM sees theirs.

The leader view rolls up every CSM’s book, with ARR at risk by owner and the trend over 30, 60 or 90 days. Each CSM opens My book: their own accounts ranked by renewal risk, the top reason behind each one, the evidence and today’s actions.

Try it: filter by CSM or risk, switch the range to 30 days, hover the trend line, or click any account to open its Account 360 below.

02 · Account 360

One account, the whole story.

Health and the five dimensions behind it, each with a 12-week trend; adoption by feature; the signal timeline; stakeholders and their sentiment; and an AI brief that cites its sources. Your CSM opens it; you see why the renewal is at risk.

Try it: click a dimension to see its evidence, open any evidence chip to read the source, toggle “Show evidence”, or switch account.

03 · Health scoring

Health you can defend.

Five dimensions, each with a 12-week trend and a one-line reason. When data is missing, the dimension says so instead of pretending.

  • Five dimensions: Commercial, Adoption, Technical, Relationship and Outcome.
  • Clear bands: Healthy, Watch, At risk and Critical, plus Unknown when there isn’t enough data.
  • Rule-based and versioned. The same inputs give the same score, and history is kept so you can show why an account was red on any date.
  • AI never computes a score. It only explains one.
Ironvale Systems · assessment historySample data
Every assessment is kept, with the rules version that produced it
At risk44rules v3At risk ahead of the 11 Dec renewal · API errors +38% · P1 #4821 open
Watch55rules v3Ticket surge after v5.2
Healthy76rules v3Release v5.2 ships
Healthy78rules v2All signals steady
HealthyWatchAt riskCriticalUnknown

04 · Renewal Room

Every renewal in the window, with a plan.

Overdue, 0–30, 31–60 and 61–90 days. Every card shows health, owner, plan progress and the top reason. Accounts go At risk well before renewal, while there is still time to recover them.

Try it: switch between 30, 60 and 90 days, and click any card to open its recovery plan.

05 · AI signals

Every conversation, read. Every warning, caught.

TellStay’s AI reads every ticket, call transcript, email, Slack and Teams thread across your book and flags frustration, complaints, escalations and serious comments, plus the growth signals worth acting on. Each one links to its source.

Try it: filter by source, and open any signal to read the original ticket, transcript quote, email or message.

06 · AI briefs

Briefs that show their sources.

Account, renewal and portfolio briefs. Every claim cites its evidence and is labelled as a fact or a hypothesis, and every brief ends with the next best action.

  • Every sentence links to the signal it came from.
  • Facts and hypotheses are labelled, so nobody mistakes a guess for data.
  • Off by default. Your admin turns AI on per workspace, and pilot data stays out of AI until zero data retention is confirmed in writing.
  • Customer text is treated as untrusted input, never as instructions.
AI brief · Ironvale SystemsSample data
AI is off by default. An admin turns it on per workspace.

FactRelease v5.2 changed sync API pagination on 22 Sep, and API errors rose 38% the next day Release notes v5.2 API errors.

Fact14 tickets were opened since 25 Sep; P1 #4821 is still open Ticket #4821.

FactThe VP Operations wrote “third outage this month” Email · 7 Oct, and on the 14 Oct call raised alternatives Call transcript · 14 Oct.

HypothesisDispatch weekly active users fell from 412 to 238 because the morning batch fails. Fixing it should recover adoption before the 11 Dec renewal Usage · 26 Oct.

Next best action
Run an engineering-led recovery call with the sponsor before 6 Nov.
Ask: “Which Q4 renewals are exposed to release v5.2?”

07 · Share reports

Walk into the forecast with evidence.

Share an account or the whole Q4 outlook as a read-only page for your CRO or board. No login needed, and the link expires.

  • Read-only page, no login needed to view.
  • Links expire after 1, 7, 14 or 30 days (7 by default) and can be revoked at any time.
  • A frozen snapshot, so the numbers don’t shift under the reader.
  • Print or save as PDF straight from the browser.
Share report · Q4 renewalsSample data
Share link
Expires in
1 day7 days14 days30 days
  • No login needed to view
  • Frozen snapshot
  • Print or save as PDF
  • Expires 17 Dec 2026
Revoke link

08 · Executive forecast

The number your CRO asks for, with its working.

Commit, watch and at risk for the quarter, the forecast against what is renewing, GRR and NRR, and the risks the CRO will ask about, each with its plan and evidence.

Try it: hover the forecast line, open a plan, or create a read-only link.

09 · For TAMs

Technical health, and how to unblock it.

API errors and incidents over time, best-practice configuration checks for every account, and AI suggestions that unblock the customer, each grounded in the tickets and telemetry behind it.

10 · Expansion

Growth signals, sized and sourced.

Seat pressure, usage against plan, new teams and asks made on calls, found across healthy accounts and sized into pipeline you can share with the account executive.

11 · Call prep

Walk into every call already briefed.

What changed since the last call, talking points for the CSM, TAM or account executive, questions to ask, risks to address and sponsor sentiment across calls, read from the transcripts your note-taker already records.

Try it: switch the talking points between CSM, TAM and AE.

12 · Connectors

Every signal, read. Nothing written back.

TellStay reads your CRM, support desk, call transcripts, email, Slack and Teams channels, product usage and configuration, and turns them into one renewal risk per account. Every connector is read-only, and your admin confirms what is mapped before anything is scored.

  • Salesforce: read-only. TellStay never writes back to Salesforce.
  • Call transcripts: read from the note-taker your team already uses. TellStay does not join or record calls.
  • Email, Slack and Teams: only the customer mailboxes and channels your admin selects.
  • Missing values stay Unknown. They are never filled with a guess.
  • CRM and renewalsSalesforce, read-only
    Live
  • Support ticketsZendesk and Jira Service Management
    Live
  • Call transcriptsFrom the note-taker you already use
    Live
  • EmailGmail and Outlook
    Live
  • Slack and Microsoft TeamsShared customer channels
    Live
  • Product usageActive users and feature adoption
    Live
  • Config checksBest-practice configuration, checked daily
    Live
Salesforce · field mappingSample data
SalesforceRead-onlyLast sync 2 min ago · 31 accounts
Salesforce Account fields mapped to TellStay fields
Salesforce fieldTellStay fieldTypeStatus
Account.NameAccount nameTextConfirmed
Account.IdExternal IDIDConfirmed
ARR__cARRCurrencyConfirmed
Renewal_Date__cRenewal dateDateConfirmed
Account.OwnerIdCSMLookupReview
Description—Free textExcluded

Salesforce free-text fields are excluded at ingestion. Nothing is written back to Salesforce.

See your own book in TellStay.

Design partners onboard from 1 December 2026 on their own data, with 50% off for their first 2 years.