Building a Scalable Customer Education & Support Ecosystem

nVoq | Healthcare SaaS, speech recognition, clinical documentation, mobile applications, enterprise administration, and APIs

As nVoq’s healthcare technology products and development teams expanded, customers, administrators, partners, and internal teams needed a scalable way to learn the software and find accurate technical information.

My role evolved from Training Developer to Senior Training Developer and ultimately included ownership of both customer learning and technical documentation. I built and maintained an ecosystem that brought together product documentation, training, video, release communications, troubleshooting, and knowledge management in a single customer-facing environment.

The Challenge

As nVoq’s products and development teams expanded, customers, administrators, partners, and internal teams needed a more scalable way to learn the software and find accurate technical information. Product documentation was moving out of the applications themselves and into an online environment, while training was also evolving beyond live classes and handouts.

The content challenge was not simply volume. nVoq’s platform included healthcare-focused speech recognition, enterprise administration, mobile applications, integrations, APIs, authentication, release-specific behavior, and later AI-assisted clinical documentation features.

Different audiences needed different levels of depth—from clinicians learning dictation skills to ISV partners and administrators working with backend settings, identity providers, and APIs.

I designed and maintained the structure of a customer-facing environment that brought documentation, training, troubleshooting, and product education together.

I began at nVoq as a Training Developer, creating videos and handouts for instructor-led training and facilitating live courses. When I later took on the Technical Writer function in addition to training, I became responsible for the technical documentation supporting the development organization.

Over time, that scope grew from dictation/linguistics and administration products to include nVoq Voice, nVoq Administrator, Android, iOS, and related platform capabilities. By the end of my tenure, I was documenting work produced by approximately 20–30 developers while continuing to own customer and partner learning.

• Owned technical writing for multiple development teams, including user and administrator documentation, release notes, knowledge-base content, and instructional video.

• Partnered directly with software developers, Product Owners, QA, Support, Customer Success, Sales Engineers, Sales, and Marketing.

• Created content for end users, administrators, customers, partners, ISVs, trainers, and internal customer-facing teams.

• Selected and implemented the platforms used to deliver the online knowledge and learning experience.

My Role & Ownership

What I Built

1. A Public Technical Support & Knowledge Environment

When product documentation moved to an online environment, I researched and selected ProProfs Knowledge Base and built the documentation site there. Years later, when the organization needed a different solution because of platform, pricing, and support concerns, I evaluated alternatives, selected Document360, and rebuilt the environment on the new platform while keeping the familiar support.nvoq.com address.

In both systems, I built the information architecture, categories, article structures, templates, workflows, and content organization. The environment included user and administrator guides, release documentation, FAQs, troubleshooting and knowledge-base articles, embedded video, training resources, and quick-start materials.

The Support Center grew into a large multi-product content system spanning end-user help, administrator guidance, training, troubleshooting, releases, and technical reference material.

2. A Learning Ecosystem That Evolved with the Business

Customer education evolved several times during my tenure. I began with live training, videos, and printed handouts, then moved online learning into Moodle. As needs became more sophisticated, I researched LMS options, selected Absorb, and built the learning modules used for customer train-the-trainer and ISV partner education.

Later, when the organization chose to reduce LMS costs, end-user training moved into Document360. I rebuilt that learning experience with input from Customer Success, Sales Engineers, and Support, integrating training more closely with the product documentation customers already used.

• Customer train-the-trainer learning

• ISV partner training with administrator and API-related content

• Self-paced end-user training with videos, practice activities, and supporting resources

• Quick-start guides and task-based performance support

• Reusable videos and handouts for Sales, Sales Engineering, Customer Success, and Support

A large part of the work required understanding software behavior deeply enough to explain it accurately—not simply formatting SME notes. I worked directly with Engineering and QA to understand how features, defects, server behavior, authentication, and configuration changes affected different users and products.

The public Support Center illustrates the breadth of the environment, with separate documentation and training for Windows, Android, and iOS products.

It also included a substantial Administrator guide covering accounts, organizations, API keys, logging, identity providers, auto-provisioning, shortcuts, substitutions, vocabulary, and other enterprise controls.

Extensive version histories supported Administrator, Administration APIs, Dictation APIs, and multiple client applications.

• Enterprise authentication and identity-provider workflows, including Okta and Microsoft Entra ID / Azure AD

• Administrator configuration, account and organization management, logging, API keys, and auto-provisioning

• Speech-recognition behavior, vocabulary, substitutions, formatting logic, and dictation-server behavior

• Product and API release notes that translated defect fixes and feature changes into customer-facing explanations

• Cross-platform behavior and workflows spanning Windows, Android, iOS, and backend administration

Technical Depth

Technical content included enterprise administration, authentication, identity-provider configuration, APIs, and other high-complexity workflows.

Documentation was the final step in my part of the Agile development workflow. After QA completed a user story or defect, the item came to me. I determined what documentation needed to be created or updated, wrote the corresponding release note, and decided whether additional knowledge-base or instructional content was needed.

QA reviewed my documentation for accuracy and errors. When I had misunderstood a behavior—or when the software itself was difficult to explain—I worked directly with QA and/or the Software Engineer until I understood it well enough to document it correctly. Documentation, training, and video were reviewed and updated as needed for every product release.

Embedded in the Software Release Process

Release communication required translating developer and QA work into precise explanations of what changed, who was affected, and how behavior differed across products or modes.

Governance, Findability & Continuous Improvement

The Support Center was not a one-time documentation project. I maintained it as an ongoing product-learning system. I reviewed and refreshed written documentation, videos, and training for releases; maintained publishing consistency; and worked with Support and Customer Success to turn recurring questions into new or improved self-service content.

I also reviewed Support Center analytics and search behavior, updating keywords and search terms when needed so customers could find the information they were looking for more easily.

• Information architecture, taxonomy, templates, and article patterns

• Release-by-release review and lifecycle maintenance

• QA / Engineering accuracy review

• Support- and Customer Success-driven content improvements

• Search analytics, keywords, and findability optimization

Support and Customer Success needs fed directly into the content backlog, helping turn recurring questions into reusable self-service resources.

Impact

The impact was visible in the way the ecosystem became part of customer onboarding, product releases, technical support, partner readiness, and day-to-day self-service.

Customers regularly complimented the documentation for being thorough and easy to understand. I also worked directly with Customer Success to refine training based on where customers needed more support with onboarding, usage, and adoption.

Document360 • ProProfs Knowledge Base • Absorb LMS • Moodle • Camtasia • Snagit • Vyond • Adobe Illustrator • VersionOne (Digital.ai) • Microsoft 365

Tools & Platforms

• Customer education and product adoption

• Technical instructional design and multimedia

• Technical writing for complex SaaS and APIs

• Knowledge-platform evaluation, implementation, and governance

• Information architecture and self-service strategy

• LMS evaluation, implementation, and administration

• Cross-functional collaboration across Engineering, QA, Product, Support, Customer Success, Sales Engineering, Sales, and Marketing

• Translating complex technical systems for multiple audiences

What This Project Demonstrates