Creating Service and Subservice Levels (SOP)

Decision: Do they want to a) Select Service Level then vehicle size (e.g. Express - 1T) or b) Vehicle then Service (e.g. 1T - Express)  

• This SOP is designed to document the process of creating service and subservice levels.
• Focus on taxi truck or courier type work as a common scenario.

• Service levels are the main categories (e.g., taxi truck).
• Subservice levels are variations under the main service level (e.g., vehicle size).

• Create a standard line service level for the main service (e.g., taxi truck).
• This will serve as the parent service level.

• Create additional service levels that point back to the parent service level.
• Ensure that each subservice level name starts with the parent service level name (e.g., taxi truck 3-ton).

• Hide the parent service level from customer view to avoid confusion.
• Only the subservice levels should be visible for selection.

• Treat each service level as an individual entity when creating rate cards.
• There is no parent-child relationship in rate cards; each is standalone.

• Review examples of configurations from other clients (e.g., regular courier with hidden parent).
• Understand variations in setup based on user preferences.

• Ensure that subservice levels are correctly named to match the parent service level.
• Double-check that the parent service level is hidden from customer view to prevent confusion.

• Document each step clearly to avoid errors during setup.
• Regularly review and update the SOP based on user feedback and changes in processes.

Setting Up Service and Subservice Levels (Step-by-step)

• Overview of the Loom video purpose: documenting service and subservice levels.
• Importance of this documentation for future reference.

• Typical scenario: taxi truck or courier type work.
• Users may require subservice levels based on vehicle size.

• Users select a service level (e.g., taxi truck) and then a subservice level (e.g., three-ton vehicle).
• Interaction is straightforward from the consignment creation screen.

• Service levels and subservice levels are treated as a single service level in the backend.
• Importance of understanding this for setup.

• Step 1: Create a parent service level (e.g., taxi truck).
• Step 2: Create subservice levels that start with the parent name (e.g., taxi truck three-ton vehicle).
• Step 3: Hide the parent service level from users.

• Each service level is treated as a standalone for rate cards.
• No parent-child relationship in rate cards; manage them as individual service levels.

• Example from SOS: taxi truck and transport services.
• Mention of another client (multi-transport) using a similar setup with hidden parent service levels.

• Both configurations (parent first or subservice first) are valid.
• Choose the setup that makes the most sense for user experience.