Lark Harbor Logistics (fictional) runs an equipment desk for its depots. The service manager wants it moved into the HELP service project before winter.
The data: existing HELP requests, including HELP-2, which has been Waiting for customer since 2 November, and HELP-14, a tablet request raised on a Saturday.
Done looks like: an Equipment request filed correctly, a queue that lists open Equipment requests oldest first, an SLA that pauses on customer waits and counts working hours only, a rule that assigns new unowned Equipment requests to Ava Chen, and a routed request that proves it.
Lark Harbor's equipment desk has been running from a shared inbox. The service manager wants it in HELP: a clear request type, a queue in the order the team works, a service goal that pauses while customers are away, and routing so nothing waits unowned.
You build it in steps, and each step keeps the earlier ones. The queue in step two sees the request you file in step one, the SLA in step three reads its clock from the same requests, and the rule in step four routes the request you create in step five.
Two traps are planted. HELP-2 has been waiting on the customer since 2 November: if your SLA counts that wait, it breaches a request the desk is not holding up. And a request can arrive with an owner already chosen, which the routing rule must leave alone.
Set up an intake desk and prove each part on real requests.