Who’s Waiting on Who? The Simple Question That Stops Follow-Ups Getting Lost
“I thought I was waiting on them” has probably killed more follow-ups than most software bugs ever will.
Follow-up gets messy when responsibility gets blurry.
Take a quote.
You send it Monday.
Now you’re waiting on the customer.
Easy.
Wednesday morning they email back:
Looks good. Can you confirm how soon you could start?
The situation has changed.
They aren’t holding the job up anymore.
They’re waiting on you.
That distinction is one of the core ideas behind Dazza Follow-Up.
Waiting on them
This is the easy one to understand.
You’ve done your bit and somebody else has the next action.
Maybe you’re waiting for:
a customer decision;
a supplier price;
a subcontractor document;
a payment;
an answer;
or confirmation that somebody will attend.
You don’t necessarily need to do anything today.
But you do need to remember that the matter exists.
That’s where the secretary part becomes useful.
Waiting on me
This is the dangerous pile.
These are the things where somebody else believes the next move is yours.
Maybe you need to return a call.
Send revised pricing.
Confirm a date.
Answer a question.
Upload a document.
Or simply get back to someone because you said you would.
Those loose ends are easy to lose because nobody inside your business may be chasing you yet.
The customer just sees silence.
Why an inbox isn't enough
Email tells you that messages exist.
It doesn’t necessarily tell you who now owns the next action.
The newest email isn't always the most important follow-up.
And plenty of follow-ups don’t begin in email anyway.
Phone calls, forms, quotes, invoices and conversations can all create loose ends.
That’s why DFU isn’t being designed as another inbox.
The email, form or business system can be the source.
DFU keeps track of the follow-up responsibility.
The app makes the split visible
The current Dazza Follow-Up interface separates follow-ups so you can quickly see:
Waiting on Me
and
Waiting on Them
There are also separate views for urgent items, overdue items, snoozed items, paused follow-ups and completed history.
The point isn’t the number of buttons.
The point is that opening the secretary should answer the question:
What am I supposed to do next?
Sometimes the answer changes
Real business conversations aren't static.
Responsibility moves backwards and forwards.
That is why the follow-up itself needs continuity.
A customer response shouldn't require you to start an entirely unrelated record and lose what happened before.
The current DFU build keeps activity around the follow-up so changes can be understood later rather than relying entirely on memory.
That becomes increasingly important as more of the connector work develops.
Simple on the surface, careful underneath
This is one of those features that looks very simple on screen because the difficult part shouldn't be dumped onto the user.
That is deliberate.
As DFU develops, the intention is for connected sources to help identify and maintain follow-up information while still failing safely when the system can't be certain.
If Dazza doesn't genuinely know what's happening, the right answer isn't to quietly invent one.
The person remains in control.
Dazza Follow-Up is still under development and there is no announced release date.
But this basic idea isn't likely to change:
Know who's waiting on who.
Because once you know that, follow-up becomes a whole lot easier to manage.
Comments