A follow-up needs an owner and a clock.

A queue is useful when someone knows what to do with it.

Generating a suggested follow-up does not make it happen. The operating design needs ownership, timing, a current customer state, and a way to stop stale or duplicate actions.

What to put into the workflow.

• Name the responsible person or team.
• Record the reason and timing for the next action.
• Recheck booking, opt-out, and lifecycle state before proceeding.
• Make overdue and blocked items visible.

A concrete example.

An enquiry assigned yesterday may already have a booking today. Rechecking that state prevents an unnecessary follow-up.

What to take away.

Name the decision, keep the relevant evidence, and make the human responsibility clear. Start with a small, inspectable workflow before expanding what the system is allowed to do.