At Ozmo, our SaaS offerings within the tech support space had multiple touchpoints across our customers’ ecosystems, affecting different user groups at various points typically across broad Service-level journeys.

Platform coherence leveraging Service Design

I fostered journey mappings and blueprints as artifacts to best represent the intricate relationships of our experiences amidst a broad service ecosystem. For example, an end-user might choose to self-support their tech issues using one of our customer’s support ecosystems. Our Self Support solution was integrated into enterprise ecosystems like AT&T, Verizon, or Rogers and as users engaged, it was critical to explore graceful hand-offs to Customer Service and potentially our other product, Ozmo for Agents.

I led repetitive and consistent onsite context inquiries where design and other cross-functional colleagues could observe the points where the CSR would shift into our product and why. This level of observation and study enabled countless new innovative features and explorations on how Ozmo could be more competitive amongst the typical support agent environment. This was especially critical in the advent of advancing AI capabilities where this direct observation led to automation innovations and workflow simplification.

Here's an example of how I leveraged Service Design to reduce cognitive burden:

💼 Case:

One early example of this was through observation, we witnessed the repetitive workflow step where CSRs would document their call summary into their CRM platform, detailing the customer interaction.

⚠️ The problem:

With Ozmo occupying a space shared with many other tools for CSR workflow, asking them to remember all the steps they took at the end of their experience supporting the customer was a heavy cognitive burden.

🛠️ Process:

As part of Ozmo’s AI evolution, I was constantly evaluating our products and known user needs / pain points in search of opportunities to advantageously implement intelligent features and capabilities.

Through consistent content inquiries, it was clear Ozmo fit within a larger user journey made up of tools and workflows outside of our control. As required by most workflows, CSR users were intended to supply call notes into their CRM platform at the end of their support experience. I explored how intelligent automation could remove the expectation that the agent would need to keep track of support content they used within Ozmo for Agents.

✅ Results:

I suggested a simple additional feature within our product to automatically capture what support guides and steps CSR agents utilized as an active historical feature - provided to them automatically after each engagement. Not only did this add convenience and simplify their workflows, but by supplying a record of activity within our product - it offered a strategic opportunity for the subsequent CSR to easily jump back into our product by following links supplied within the captured notes.

Even better, this proposed feature could be coupled with an existing capability which enabled sending tutorials and support content to the customer from within Ozmo for Agents. This automatic, intelligent capture of what content the CSR used meant they could now leverage their history easily for either their CRM Call Notes or for recommended packages to be shared with the customer as summary.