Kept for Customer success.
Renewals are relationships with a memory. Three films on keeping the account story when the CSM changes.
All industriesFor executives
Every CSM departure is a renewal event you did not schedule.
The account record shows the health score. It does not show why the customer stays.
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
An account changes hands and the new owner learns its history from the customer, one awkward call at a time.
Commitments and risks made in conversation vanish at handoff, and renewals get lost for reasons nobody can name.
Kept is a voice interview. June calls, asks about your work, and keeps what you say, in your words, in your knowledge base.
The new owner asks what we promised Halden. Kept answers with the commitment and the risk, cited to the Q B R debrief.
Customer commitments survive reassignment, and renewal risk is visible before it’s late. Kept. Keep the knowledge behind the work.
Success runs on accumulated relationship knowledge: who the real champion is, what almost caused the churn scare, which promise from two quarters ago the customer still remembers. When a CSM leaves, that story leaves, and the customer notices the new voice knows none of it.
Kept captures the story from your CSMs while they run the accounts, and keeps it cited and current. A transition becomes a briefing instead of an apology tour. The book of business stays the company's book, with the relationships intact.
For managers
A book transition should not begin with an apology.
The new CSM's first three calls are spent discovering what the old CSM already knew.
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
An account changes hands and the new owner learns its history from the customer, one awkward call at a time.
Every reassignment costs you a month of ramp and one avoidable escalation.
Kept is a voice interview. June calls, asks about your work, and keeps what you say, in your words, in your knowledge base.
The new owner asks what we promised Halden. Kept answers with the commitment and the risk, cited to the Q B R debrief.
Handoffs take a day, not a month. Kept. Keep the knowledge behind the work.
Every reassignment burns relationship capital. The customer repeats their history, the new CSM guesses at context, and the notes in the CRM turn out to be titles without stories. Multiply by every parental leave, promotion, and resignation, and coverage becomes your biggest quiet churn driver.
Kept interviews your CSMs about their accounts as they work them, keeping the story in their words with every claim cited. Transitions hand over the relationship, not just the renewal date. You see coverage across the book. Nobody gets scored, because Kept refuses to.
For partners
You carry every account's story. Put it somewhere with your name on it.
You know which customer needs the Thursday call and which one will churn politely. None of that fits in a health score.
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
An account changes hands and the new owner learns its history from the customer, one awkward call at a time.
You inherit an account with promises you didn’t make and can’t find.
Kept is a voice interview. June calls, asks about your work, and keeps what you say, in your words, in your knowledge base.
The new owner asks what we promised Halden. Kept answers with the commitment and the risk, cited to the Q B R debrief.
You know what was promised before the customer reminds you. Kept. Keep the knowledge behind the work.
Kept talks with you about your accounts the way a good handoff conversation goes, and keeps it in your words. When you are out, or promoted, or finally taking the vacation, whoever covers gets the real story, citing you. Your relationship work becomes visible as yours.
Capture starts with each partner's consent. They can skip a question, stop a session and review their captured knowledge. A business workspace's access rules determine who else can use it.
Knowledge captured for a business workspace belongs to that workspace. Partners retain visibility, removal from view and in-session retraction controls. Permanent deletion follows the workspace request process, unless a provisioned legal erasure window applies.
Kept's internal partner model is not employer-facing. A business workspace can see a red, amber or green capture band, based on contributed knowledge, alongside the access and audit records described in the Privacy Notice. It is not a score of a person's work or judgment.
Where it starts in customer success.
One process, one question the team already asks.
Start at zero.
Pay once when the KPIs land.
The KPIs we would propose for a customer success team:
- Questions asked of Kept per week, and the share answered with a source
- The ten most repeated questions, and whether each has a kept answer
- Partners with capture on, and using Kept, through the whole window
- Knowledge kept per role in scope, and its coverage band moving from thin to covered
Agreed before the pilot starts and measured from the workspace's own ledger over a window we set together, with a minimum number of partners using Kept through it. Nothing to pay to begin. A one-time payout when the KPIs are met, then the recurring rate.
How the proof of value worksUseful knowledge.
Visible limits.
Kept supports the work. It does not assess competence, monitor people or replace training, supervision or required qualifications. Business knowledge follows workspace access and ownership rules.
Kept is designed to ground answers about your work in available sources and say when it does not know. AI can still make mistakes. Inspect the sources and review important answers before relying on them.
Security and compliance