Support org handoff
The service operations manager at fictional Juniper Scheduling needs a new support intake. Build a queue, ordered routing, a technical support type and layout, a response deadline field, and a workload report.
The completed org must send urgent cases to the team queue, route unmatched intake to Support, preserve an unresolved case, and report active workload by priority. A generated acknowledgment would not count as a resolution.
You own the complete support org handoff described in the brief. The next person needs working configuration and enough evidence to explain its behavior. Start with the business requirement, then keep each completed part while you add the next one. Your own saved state carries between steps.
A later task can expose a mistake that an isolated form would hide. A queue may exist without usable membership, a report may have the right title but the wrong population, and a rule may work for the example while rejecting an allowed record. Test those boundaries as you go. The final step asks for the operational conclusion or completed deliverable, and the checker keeps earlier requirements in scope.
Business requirement → configuration → boundary tests → handoff
Build a connected deliverable and retain its controls.