01 / The organization
Technical expertise across North America
A North American railroad relies on technical employees across a national transportation and logistics system. Its internal center of excellence and troubleshooting team brings together more than 40 seasoned technicians and engineers, all with experience working in the field.
This is support grounded in first-hand operational knowledge. The team provides real-time assistance across multiple North American time zones and regions, helping employees work through technical questions with people who understand the environment.
Requests for assistance arrive by radio, phone, and chat. Chime V5 handles the chat component through a custom web client embedded in the employee portal.
02 / The story
Routing technical questions as support assignments change
Connect technical employees to the right expertise, even as responsibilities change. Internal teams rotate chat-support assignments daily, so workflows and routing must adapt to the current roster across regions and time zones.
First-line assistance and Level 2 expertise both matter. The chat experience needs to support that tiered model while reflecting the team currently assigned to help.
03 / The story
Connecting chat with an established support operation
The support operation brings together requests arriving by radio, phone, and chat. Its internal specialists rotate chat-support assignments as part of the daily operating model.
The requirement for the chat component is to fit that established support model: give employees a portal-based entry point and keep routing flexible as responsibilities change.
04 / The story
Employee-portal web chat with priority-based agent routing
A custom web chat client is deployed inside the employee portal, giving employees a direct way to ask for assistance from their existing workspace.
Chime V5 provides the chat workflows and agent routing for a team of field-experienced technicians and engineers. Flexible configuration supports changing daily assignments and the organization’s first-line and Level 2 support structure.
Employees bring a wide range of everyday questions to chat: ID badge queries, vacation requests that will not submit, issues opening VS Code on a desktop, and printer problems. The value is access to people with the expertise to investigate the issue.
Agent routing follows a configured sequence: Priority 1, then Priority 2, then All Agents. This routing order works alongside the L1/L2 support structure; priority groups and support levels are separate concepts.
Start in the employee portal
Employees request help through an embedded custom web chat client.
Reflect today’s assignments
Flexible workflows and agent routing accommodate the rotating support roster.
Connect to the appropriate support level
The chat model supports first-line assistance and Level 2 expertise.
Route to agents
A clear priority order. A flexible support team.
- 1Priority 1
First configured agent group
- 2Priority 2
Next configured agent group
- 3All Agents
Expand to the wider agent pool
Priority groups guide agent selection. L1 and L2 describe support levels.
05 / The story
Connected chats, employee feedback, and agent answer times
The value of this service is access to seasoned technical expertise. Portal-based chat connects employees across North American regions and time zones with technicians and engineers who have worked in the field.
The November 2026 month-to-date report records 508 chats connected to agents. That figure represents connections to support, rather than a count of confirmed resolutions.
Submitted employee ratings average 4.41 out of 5, with 88% of the feedback shown at four or five stars.
The median of the positive agent-level average-speed-to-answer values is approximately 2 minutes 19 seconds after excluding the identified 639.31-second outlier. This is a summary of agent averages, not a chat-weighted service-wide response time.
From the service desk dashboard
Real conversations. Employee feedback.
November 2026 · month-to-date dashboard snapshot
88% of submitted ratings were four or five stars.
Positive agent averages only; the 639.31-second outlier is excluded. This is not a chat-weighted overall ASA.
A direct chat channel to experienced technical support. Connected chats are not a measure of confirmed resolutions.
About these results and how they were calculated
Ratings are calculated from the supplied feedback chart and describe submitted responses. The ASA report filter is November 1–18, 2026; the capture was supplied on November 17. These are snapshot results, not a completed-month comparison. The inbound-versus-connected report uses the same November 1–18 filter and shows no activity for November 18. The connected total is the sum of the displayed connected series.
The ASA summary is the median of positive agent-level averages. Zero entries are omitted because they do not establish an instantaneous answer. The identified 639.31-second outlier is excluded. Agent chat counts are unavailable, so an overall chat-weighted ASA cannot be calculated. No connection rate, resolution rate, or response-time improvement is inferred.
06 / The story
Web chat technical support architecture
The employee portal hosts the custom web client. Chat requests enter the Chime V5 workflow and are routed according to the current support assignments, with first-line and Level 2 assistance available within the support model.
Employee portal
Embedded custom web chat client
Chime V5
Flexible chat workflows and agent routing
Current support assignments
Rotating internal teams; assignments change daily
Center of excellence
40+ troubleshooting and support specialists
Level 1 support
First-line assistance
Level 2 support
Specialist troubleshooting
Chime V5 technologies and features
- Route to Agents
Connect employees to the right human expertise.
- Configure priority-based agent selection: Priority 1 → Priority 2 → All Agents.
- Support live handoffs and escalation between support tiers or departments.
- Custom Reporting & Analytics
Turn session-level activity into useful service insights.
- Review connected chats, agent performance, answer times, and employee feedback.
- Use reporting APIs and JSON or CSV data with tools such as Power BI.
- Custom Chat Workflows
Adapt the support journey as operating needs change.
- Arrange workflow steps, collect information, and route to agents.
- Extend workflows with FAQ, AI, or integration steps where configured.
- Custom Web Chat Client
Bring the chat experience into the employee’s existing workspace.
- Customize the web client and chat journey for a company or department.
- Connect web conversations to priority routing, agent tools, and feedback.
- Help Center Dashboard
Organize support services in a single starting point.
- Bring IT, HR, training, and internal support services together.
- Surface FAQ collections, featured services, and quick actions.
Microsoft technologies in this solution
- Microsoft Azure (opens in a new tab)
Cloud foundation for the connected support platform.
- Cloud services for application hosting and integration.
- A foundation for extending support workflows with AI services.
- Microsoft Entra ID (opens in a new tab)
Employee identity and directory context. Formerly Azure AD.
- Identity and access management for connected applications.
- Directory context that can inform personalized support and routing.
- Azure Translator (opens in a new tab)
Language translation for multilingual support experiences.
- Text translation and language detection through APIs.
- Translation capabilities that can be incorporated into chat workflows.
- Azure Communication Services (opens in a new tab)
Communication APIs for connected chat experiences.
- APIs and SDKs for embedding communication in applications.
- Chat capabilities for custom web-based experiences.
- Microsoft Teams (opens in a new tab)
Collaboration capabilities within the Microsoft technology stack.
- Team communication and collaboration across locations.
- Complements the custom Web Chat entry point used by employees in this story.