Why deals were lost, and when to call back
When a deal is lost, AI records why and when to reach out again
A B2B sales team whose deals take months to close set up a flow where AI rereads the meeting notes, emails, and memos of every lost deal, records the real reason and when to reach out again, and reminds the rep on that day.
The problem
- 01
Loss reasons end up as "Other"
Busy reps picked any reason or left it blank, so later no one could tell why a deal was lost.
- 02
Second chances slip by
No one remembered when to call back, such as when a competitor’s contract ends, until that moment had passed.
- 03
The same losses repeat
Nobody tallied why deals were lost, so the same reasons cost deals quarter after quarter.
How Trackit solves it
- 1
The rep only moves the stage to Lost
When a deal is lost, the rep changes its stage to Lost. No reason to pick or write. The stage change starts the workflow through a record-updated trigger.
- 2
A custom agent rereads the deal’s history
A custom agent reads the deal’s meeting notes, emails, and interactions, and returns set fields: the loss reason (price, competitor, timing, budget), the competitor, the sentence it is based on, and how many months until a good time to reach out. The agent only reads; later blocks save the values.
- 3
The reason stays on the deal, the re-contact becomes a dated task
Adjust time adds those months to the day the deal was lost, and update record fills the reason, competitor, evidence, and re-contact date on the deal. Create task gives the rep a re-contact task due on that date. On the dashboard, loss reasons add up into counts by reason.
- TriggerRecord updatedA deal’s stage changes to Lost.
- AICustom agentReads notes, emails, and interactions to find the reason and re-contact timing.
- ActionAdjust timeAdds the months to the day it was lost.
- ResultUpdate recordFills the reason, competitor, and re-contact date.
- ResultCreate taskGives the rep a task due on the re-contact date.
What changed
Before Trackit
With Trackit
More use cases
B2B SaaSRouting leads to owners by score
An agent scores leads from web forms and the meeting scheduler, then hands each to an owner on the matching team with a call request or a first email.
Meeting-heavy B2B sales teamA customer brief the day before the meeting
Every evening it finds tomorrow’s customer meetings and leaves a brief with past history and questions to ask on the record and in Slack.
Sales organizationWeekly sales reports written by an agent
Every Monday morning, an agent reads last week’s sales activity and leaves a team report.