The AutoAlert Story

Dealership Transformation Only Happens When Users Can Find Value

AutoAlert is a data-mining and CXM platform built for car dealerships. Its tools help dealership sales teams identify, track, and act on high-profit opportunities using predictive analytics and customer behavior signals. That value depends on execution: salespeople, admins/managers, and other roles need to complete workflows quickly and correctly inside the product, even when the product changes often.

AutoAlert operates two apps where enablement complexity piles up fast. AlertMiner spans multiple hostnames, and AlertMiner Pro + CXM introduces additional user role types, segments, and dealership add-ons. With frequent new releases landing every two weeks and major updates every six weeks, AutoAlert needed an enablement layer that could ship alongside the product experience to guide users of new capabilities, showcase value, and drive adoption.

The Challenge

Content Sprawl and Segmentation Complexity Require Advanced Digital Adoption Platform Capabilities

AutoAlert had invested for years in its in-app enablement and digital adoption strategy using WalkMe, but the program hit practical limits. Customization requirements and support needs outgrew what they were receiving from WalkMe, and long-term pricing added pressure. 

At the same time, AutoAlert’s in-app content library had become dense and hard to consume. Its curriculum was highly detailed, including 50 to 60 processes inside a single Task List, which created drop-off risk for new and occasional dealership end-users.

End-users also had to leave the application to find help. With its legacy DAP solution, many resources were stored in SharePoint repositories, forcing users to leave their workflow and skim through documents to find answers to their questions. That added time and effort to everyday tasks, contributed to rework, and made it harder to sustain feature adoption through AutoAlert’s rapid release cadence.

The Solution

Governed, Role-Based Guidance That Runs Like Product Ops With Whatfix

AutoAlert migrated to Whatfix as one of the first official DAP Migration Fastrack projects, moving from WalkMe to Whatfix with a structured content replication approach using downloaded pieces and live content as reference. 

Fast Track is a structured, five-phase approach that enables organizations migrating from a legacy DAP to Whatfix, helping reduce migration risk, remove low-value content, and launch with stronger governance and better long-term scalability.

This structured migration maintained continuity while also improving underlying content by rebuilding the entire enablement architecture layer for better consumption – this included:

Making learning achievable, not tedious

Legacy content from its previous DAP provider was more exhaustive than helpful. By migrating to Whatfix, it received support from digital adoption and instructional design experts that help re-imagine its in-app content, with examples including things like:

• Breaking down a lengthy curriculum into sequential Task Lists aligned to real workflows.
• Adding quizzes between modules to reinforce learning and accelerate time-to-competency.
• Converted unhelpful tooltips into a larger guided Flow after collaborative redesign to improve guidance depth

“We’d been on WalkMe for years, but we hit limits on customization and support. Whatfix was a better fit on both, and the migration moved fast once we got started,” said Maggie Huffman, VP of Operations at AutoAlert

Targeting the right guidance to the right user, at the exact moment of need

AutoAlert required tight governance, including a lengthy list of role tags, visibility rules, and segmentation across its applications, geographies, dealership types, and product add-ons. 

Whatfix supported a role-based experience across languages (English, French, Spanish) and a large asset library: 450 content assets, including 46 Flows, 15 Task Lists, and 315 Self Help resources. 

Resources and media were segmented by role, different Task Lists were created by application and role, and different Self Help experiences were created by application.

Embedding support into the workflow to contain support escalation overload

A key pain point before Whatfix was that AutoAlert’s end-users needed to click into external knowledge repositories like SharePoint to find and consume how-to articles, best practices, and troubleshooting documentation. Below is an example of 

With Whatfix, it integrated these resources directly into its application UI and workflows, including:

• Deployed a customized chatbot integration with live chat support directly into its Self Help, so real-time support surfaced when it mattered to resolve how-to issues on the dealership floor.
• Implemented Smart Tips for in-context access that drove adoption of its Self Help portal.
• Supported ongoing change management through continuous content updates tied to release cycles.

Instrumenting Adoption Ops to Make Better, Data-Driven Decisions

AutoAlert used reporting and dashboards to understand what users searched for, how content performed, and how users interacted with new features. The goal was operational control: ship features, guide behavior, measure adoption, and adjust the experience.

The Results

Faster guidance access, higher dealership engagement, and scalable change management

AutoAlert’s ROI shows up in operational metrics that map directly to execution and retention, including:

• Workflow efficiency gains: Moving support from SharePoint into in-app guidance reduced time spent hunting for documents and cut the effort time per task. Before Whatfix, finding the right document could take a new user 5 to 7 minutes. With in-app guided access, the path to an answer was only a click away.
• Customer adoption evidence that is defensible to leadership: A Smart Tip guiding users on “Blocks” inside AlertMiner was accessed 1,726 times in a 90-day period, demonstrating that users consumed guidance in the flow of work when it was placed contextually to specific dealerships depending on their location, customer type, and add-on products used.
• Reduced rework and stronger completion: Role-governed Self Help and in-context guidance reduced the likelihood that users followed the wrong process for their segment or permission level, supporting improved workflow completion rates and lower error and rework rates.
• Change management that scales with the release machine: With frequent releases across both its Pro and CXM apps, AutoAlert built an enablement operating system that can keep pace. That protects productivity through UI changes and supports retention by reducing churn risk tied to poor onboarding and weak feature adoption.