The missed callback problem: I built a promise-tracking workflow and want brutal operator feedback

[Rozeena]

A customer is told "I'll call you back at 3." At 3:30 nobody has called. By the next morning they've bought somewhere else.

You know this one. It rarely shows up in a report, because a promised callback that never happens doesn't get logged as a lost deal. It just disappears.

I built a workflow called Dealership Brain to attack that specific problem:
• Promise tracking: when a salesperson tells a customer "I'll call you back by X," that promise is logged with a deadline.
• Automatic escalation: if the deadline passes with no callback recorded, the manager gets alerted so someone can recover the lead before it goes cold.

That's the whole idea. Nothing flashy.

Where it stands: prototype stage. I haven't proven this works in a live store, which is why I'm posting here instead of pitching anyone.

What I want from you, bluntly:
1. What would make you trust this in your store?
2. What would make you reject it in the first five minutes?
3. Would your salespeople actually log promises, or does that kill it from the start?
4. Is escalating to the manager the right move, or does it create its own problems?

If you want to poke at it, there's a free demo here: https://dealership-brain.vercel.app

Tear it apart. I'd rather learn what's wrong from the people who'd actually use it.

 

[ASNSoftware]

Good problem to attack — the missed callback is invisible in every report, and it's where deals quietly die.

Blunt answers from our side of the fence (I work at ASN Software — we build the DMS/CRM a lot of independent and BHPH stores run on, and our AI Collector lives or dies on promise-tracking):

1. Trust comes from the log, not the workflow. I'd trust it if the promise is captured from the actual conversation — the text, the call, the CRM note — with a timestamp, not typed in afterward. The moment a promise record depends on someone's memory or honesty, it's a story, not a record. When a customer disputes something, the log is what settles it.

2. What kills it in five minutes: manual logging. If your workflow needs the salesperson to type "promised callback by 3" into a form, it's dead on arrival. Salespeople won't do it consistently, and the ones who do will backfill it at end of day. The promise has to be captured in the channel where it was made, automatically.

3. Escalate the account, not the person. Alerting the manager that "Salesperson X missed a callback" builds a blame feed — salespeople will start avoiding the system. Alerting that "this customer was promised a callback by 3, it's 3:30, nobody called" frames it as a recovery job. Same alert, completely different culture. And the escalation should carry a recovery move — reassign it, or auto-text the customer — not just a notification.

4. The real test isn't the alert, it's the follow-through. In our collections work, the pattern that actually closes the loop is: promise logged → automatic reminder on the promised date → if the human doesn't follow up, the system follows up anyway. The alert tells you something broke; the automatic follow-up fixes it before the customer buys elsewhere.

If you can capture the promise without asking the salesperson to do extra work, you've got something. If you can't, the workflow will be perfect and unused.

 

[Rozeena]

Hi Alex, thank you for such a detailed and honest breakdown. It's more useful than most of the feedback I've gotten.

Your "capture, don't log" point is the sharpest one, and it's the one I'm most focused on. A record that depends on someone remembering to type it in afterward is exactly the "story, not a record" problem you described. So in Dealership Brain, promises are pulled from the customer chat conversation itself, where the promise was made. The system extracts the promise and its due time from the conversation, with timestamps, and nobody fills in a separate promise form.

On follow-through, there's a "Promise Watch" sweep over the logged promises. When one goes overdue, it escalates and prepares a follow-up draft for the customer, so the recovery move comes with the escalation rather than just a notification. Your point about escalating the account instead of the person is a good check on that design, and I'm keeping it in mind.

I also recently added proper sign-in with private workspaces per dealership, and everything now lives in a persistent database.

One honest caveat: I don't work at a dealership, I build software for them, so I'm learning a lot from people who live this daily.

When a promise is made on a phone call rather than in text, how does your team see that handled today, if at all?

Thanks again,
Rozeena

 

[ASNSoftware]

Rozeena — appreciate the detailed response. Extracting the promise from the chat itself, and having the escalation arrive with a recovery draft already prepared, are the right design choices — that's how it stays a recovery system instead of becoming another notification feed.

On the phone-call question, honestly: it's the weakest link everywhere. Most collection promises in our world happen over text — that's deliberate, because text is where capture is automatic. When a promise does get made on a call, the pattern we see work is moving it into the captured channel right away: immediately after the call, the customer gets a short confirmation text — "confirming what we just discussed: $X on Friday" — and from that moment the promise lives in the same system as every text promise. Same timestamp, same reminder on the promised date, same escalation if it goes quiet. The customer has a copy too, which settles most "nobody told me that" disputes before they start.

Where a call is recorded and transcribed, you can extract the promise from the call the same way you extract it from chat. Where it isn't, the confirmation text is the bridge. It beats asking the collector to fill in a form afterward — we both know that's where the record goes to die.

And don't let perfect be the enemy here. A call promise confirmed by text two minutes later is a real record. A call promise that lives in someone's memory is a story.

Curious about one edge case on your side: if a promise made in chat and something said on a later call contradict each other, which one wins in Dealership Brain?