Follow-ups & opportunities
Build a follow-up system that survives a busy day
Give customer follow-ups an owner, a useful next action, and a due time. Learn how to organize opportunities and reminders without relying on memory.
The short version
- Write the next action as a specific result, with one accountable owner.
- Choose timing from the customer’s request or the work’s dependency, not an arbitrary chase schedule.
- Close the loop by recording what happened and what remains.
“I’ll get back to them” sounds like a plan until the next call arrives. By the end of the day, several people may remember the customer and nobody may know who promised what. A follow-up system makes the promise visible. It should help your team decide what to do next, not just create another list of overdue reminders.
Replace vague reminders with useful actions
“Follow up with Taylor” makes the next person reread the conversation. “Confirm whether Taylor wants the revised scope before preparing the agreement” explains why the contact matters. A good reminder contains a verb and the decision or result it should produce.
In Zweelie, keep the opportunity’s summary and notes aligned with the next step. Use the opportunity for the piece of work, rather than creating another opportunity every time the same customer sends a message.
Give the promise one owner
A team can contribute while one person remains responsible for the next action. Assign that person and make the handoff explicit if responsibility changes. A team chat mention can help coordinate the work, but it should not be the only place the assignment exists.
For example, Priya prepares a proposal while Sam checks the delivery date. Priya owns sending the agreed response. Sam’s contribution is a dependency, not a reason to leave the whole opportunity unassigned.
Set timing that has a reason
Start with what the customer asked for and what your team can actually do. If they want to review the proposal next Tuesday, record that context. If you are waiting on a supplier, record the dependency and when you will check it.
A reminder prompts someone to act. It does not mean a customer has been contacted, a message has been sent automatically, or the underlying work has finished. Keep those outcomes separate when using follow-up reminders in Zweelie.
- What action is due?
- Who owns it?
- What information is still needed?
- What would count as finished?
Record the outcome, not just the attempt
After acting, leave a short update: reached the customer, waiting for a document, revised the scope, or no longer proceeding. Adjust the status and next reminder to reflect that outcome. Sending a message may complete an action while the opportunity remains open.
Agree what your team means by won, completed, and lost. An accepted piece of work and delivered work are different milestones. Keep estimated value and actual payment activity distinct as well.
Use overdue work to improve the process
Review a few overdue follow-ups together. Look for missing owners, unclear requests, impossible timing, or work waiting on the same dependency. Moving every due date forward hides these patterns.
Begin with one type of follow-up and a short daily review. When the owner can explain the next action from the record alone, you have a process the rest of the team can use—even on a busy day.
About the author
Alex Hanna is the founder and CEO of Zweelie. He writes about bringing customer conversations and everyday business work into one connected workspace.
