Priya has carried the biggest renewals for seven years. On a Friday at four she hands in two weeks' notice, and she means it. Ten working days. This is what they look like with Kept. Every name and every line of it is example material.
Prototype with synthetic material. No live workspace, customer content or input collection.
01 / The Friday
Two weeks.
It is a good offer and you cannot match it. You wish her well, and you mean it. Then you open the renewal calendar. Northwind renews in five weeks. Priya has saved that account twice, and nobody else has been on a call with them in a year.
Synthetic transcript · Senior account manager (fictional) · The Friday
“I'll do a proper handover. I'll write up the big accounts. There's a lot that's just in my head, honestly.”
This story is available entirely as text.
02 / Monday morning
The first conversation.
The write-up would take her last three days and cover the accounts, not the judgment. Instead, Priya turns capture on herself on Monday morning, and June asks her about Northwind while it is still fresh.
June
Tell me about the last Northwind renewal. What nearly went wrong?
Priya, Senior account manager
Their procurement lead will push for a discount in the last week, every time. The answer is never a discount. It's the extra seats for their support team at the same price, because that's what the sponsor actually needs to sign. If you offer money you lose the sponsor.
Capture is on, by Priya's own choice, and she can turn it off at any time.
Twenty minutes before her nine o'clock. Not a form.
03 / Ten working days
The accounts, in her words.
One conversation a day, on the accounts that matter most. Who the real decision-maker is, the pricing exception that was agreed by phone and never emailed, which escalation goes to the CTO and which never should. Each becomes a piece of knowledge with the trigger, the response and the reason.
Synthetic knowledge item · SalesReviewed by the partner
Northwind renewal: the last-week discount ask
Trigger
Northwind procurement asks for a discount in the final week of a renewal.
Response
Offer extra seats for their support team at the same price. Do not offer a discount.
Reason
The sponsor signs for the seats; a discount loses the sponsor's case internally.
Example review: checked against the source. Priya named the sponsor and the procurement lead.
On her last Thursday, Priya reads everything that was kept. She corrects a name, removes a guess about a contract date, and adds the one thing she had forgotten to say. Work captured for a business workspace stays with the workspace when she leaves, with every source intact.
Synthetic transcript · Senior account manager (fictional) · Day 6
“Never let the renewal call happen without their support lead in the room. If she's not there, reschedule. She's the one who says yes.”
About source availability
Keeping a knowledge item does not promise permanent access to its original transcript. Sources can become unavailable after retention or removal. Check what evidence is available before relying on an answer.
05 / After she's gone
“Northwind wants a discount. What do we do?”
Three weeks later, the renewal call is tomorrow. The colleague who inherited the account asks the workspace. The answer comes from what Priya said, and it cites the day she said it.
Colleague
Northwind procurement is asking for a discount before tomorrow's call. What do we do?
Kept
Do not offer a discount. Offer extra seats for their support team at the same price: the sponsor signs for the seats, and a discount loses the sponsor's case internally. Make sure their support lead is on the call; if she is not, reschedule.
Every answer cites the conversation it came from. AI can make mistakes: open the source and decide.
06 / What she never said
“What did we promise Northwind about the data residency?”
Ten days is not seven years. When the question is one Priya never answered, Kept says so and points at who to ask, instead of a guess dressed as an answer.
Unknown in this sample
Nothing about a data-residency promise is in what Priya kept. I can't establish the answer.
Check the signed order form and ask the account's executive sponsor.
Capture is opt-in, and each partner reads what was kept before it counts. What a workspace keeps follows that workspace's permissions, enforced in the database on every row, never by an AI model. It is encrypted in transit and at rest, never used to train a model, and a session transcript cannot be edited or deleted once recorded. Single sign-on, two-factor and an exportable audit ledger are part of the business plan. What is live, in progress and planned.
Does it bolt on to what we already run?
Kept runs beside your systems, not inside them. There is nothing to install in your stack and nothing it needs from your CRM or ticketing tool to work: your people talk to June in the browser or the companion window, sign in through your identity provider, and add the documents that matter. What it keeps stays yours: every answer cites its source, the workspace audit ledger exports as JSON or CSV, and each person can download a complete copy of their own record. How the systems you already use fit in.