Fusion Service Redwood Implementation — Lesson 2: Service requests, queues, assignment, milestones, knowledge, communication, and agent experience

Learning Objectives

• Break down the roles, prerequisites, records, and decision points involved in Service requests, queues, assignment, milestones, knowledge, communication, and agent experience.
• Complete a controlled activity for Service requests, queues, assignment, milestones, knowledge, communication, and agent experience and capture configured service flow and agent journey evidence.
• Challenge the result with a scenario involving milestone timers starting from the wrong status transition, then justify the corrective action.

Detailed Topics

• Service requests
• Queues
• Assignment
• Milestones
• Knowledge
• Communication
• And agent experience
• Decision ownership, prerequisites, and acceptance evidence for Service requests, queues, assignment, milestones, knowledge, communication, and agent experience
• Relevant access, data, integration, performance, recovery, and support considerations

Instructor Demonstration

The instructor configures and tests Service requests, queues, assignment, milestones, knowledge, communication, and agent experience within a scenario aimed at a Redwood-based Fusion Service implementation with purposeful user experience, service process configuration, integration, and production controls. The walkthrough contrasts a valid setup with a flawed one and uses configured service flow and agent journey evidence to make the difference explicit.

Hands-On Exercise

Complete a guided task covering Service requests, queues, assignment, milestones, knowledge, communication, and agent experience. After establishing a working baseline, reproduce “milestone timers starting from the wrong status transition,” isolate the responsible setting or data condition, apply a reversible fix, and update configured service flow and agent journey evidence with before-and-after proof.

1. Record the starting state, assumptions, identities, data, and expected outcome.
2. Execute the planned workflow and collect evidence at each material checkpoint.
3. Test one valid path, one boundary condition, and the stated failure scenario.
4. Document the correction, retest result, rollback option, and follow-up owner.

Scenario Analysis

• Clarify the business trigger, affected roles, required records, and acceptable result for Service requests, queues, assignment, milestones, knowledge, communication, and agent experience.
• Compare at least two implementation or correction choices and identify which evidence would distinguish them.
• Decide how configured service flow and agent journey evidence should be reviewed, approved, retained, and handed to the next owner.

Troubleshooting Guidance

Diagnose Service requests, queues, assignment, milestones, knowledge, communication, and agent experience by checking effective settings, ownership, source records, dependencies, and recent releases. Use configured service flow and agent journey evidence to locate the earliest divergence. Treat “milestone timers starting from the wrong status transition” as a hypothesis until the same test passes after correction and still passes for a boundary case.

Validation Checklist

• Prerequisites and role permissions for Service requests, queues, assignment, milestones, knowledge, communication, and agent experience have been confirmed before execution.
• The result agrees with the expected values documented in configured service flow and agent journey evidence.
• Exceptions are explained with evidence rather than hidden by manual correction.
• The final record names the approver, monitoring point, and next improvement action.

Lesson Outcome

Learners can apply Service requests, queues, assignment, milestones, knowledge, communication, and agent experience, explain the decisions made, and defend the result with configured service flow and agent journey evidence.