An inquiry can remain open long after the work around it has stopped. It may have a stage and an owner, yet nobody can say what happens next or when.
That is the gap next-action coverage makes visible.
Define the denominator first
The denominator should be the active inquiries that genuinely require commercial movement. Closed, merged or no-longer-actionable records do not belong in it.
Active inquiries with action + date + responsible person
---------------------------------------------------------
All active inquiries in scope
× 100
If 60 inquiries are active and 45 have all three elements, coverage is 75%. The missing 25% is not automatically poor performance. It is the inspection list.
What makes a next action useful?
“Follow up” is an intention, not an operational next action. A usable action answers three questions:
- What specifically needs to happen?
- When should it happen?
- Who is accountable for making it happen?
“Send the revised multi-hotel proposal on Thursday after Revenue approves the Madrid alternative” is actionable. “Chase client” is not.
The responsible person does not have to be the Inquiry Owner. A central sales manager may remain accountable for the complete inquiry while a hotel revenue manager owns the next pricing input. Both responsibilities need to be visible.
Responsibility matters as much as activity
Some inquiries are waiting on the hotel team. Others are legitimately waiting on the customer. Treating both as inactivity produces the wrong management response.
A useful workflow records work responsibility explicitly:
| Responsibility | Example |
|---|---|
| Hotel team | Confirm space availability or approve a discount |
| Customer | Review the proposal or provide missing room requirements |
The next action should reflect that context. While the customer is reviewing an offer, the hotel's next action may be a scheduled follow-up rather than immediate intervention.
Use coverage to run an exception review
Next-action coverage is most useful when it narrows a weekly review to the inquiries that need a decision:
- no action exists;
- the action has no date;
- responsibility is unclear;
- the due date has passed;
- the customer replied but the old follow-up is still scheduled;
- the inquiry changed stage without a new next action.
The purpose is not to create more tasks. It is to prevent incoming demand from remaining technically open while depending on personal memory.
Benvio connects next actions with the Inquiry Owner, work responsibility, stage, SLA, interactions and follow-up sequence. Explore the inquiry workflow.