Postpone, On Hold and Cancel chased from one place without losing what each one means.
Status at ebf7cf0: Gap — the separate /followup interface uses browser-persisted mock data with Pending, Completed, Pass to Team B rather than the approved server workflow. Multiple Outstanding pages also remain.
A visit ends as postpone, on_hold or cancel, or Sales needs to record a later contact attempt.
One filter-driven queue for all three outcomes, while preserving their different meanings.
| Outcome | What the queue must preserve |
|---|---|
| Postpone | The agreed return date |
| On Hold | A reason and a follow-up action, with no firm date |
| Cancel | It is a visit outcome and does not itself cancel the order |
Story. As Indoor, I want one filter-driven queue for Postpone, On Hold and Cancel follow-up, so that customer contact is managed consistently.
Acceptance. Each attempt records actual handler, result, reason and next action date while the original salesperson remains KPI owner.
Story. As Indoor, I want Postpone to retain the agreed return date and On Hold to require a reason, so that urgency is visible.
Acceptance. Cancel remains a visit outcome until an authorised office user cancels the Order.
The Job Log stores outcome, reason and an optional follow-up date, and the office creates the next Job Log manually. The separate /followup interface uses browser-persisted data with Pending, Completed and Pass to Team B rather than the approved server workflow. Multiple Outstanding pages also remain.
New to these terms? See the Glossary.