Cross-application guidance

• Best for: mixed desktop environments, including legacy enterprise applications.
• Important caveat: cross-app Flows require setup, and the relevant desktop applications must already be open.
• Official cross-application Flows documentation

2. WalkMe — strong fit for connected, multi-system journeys

WalkMe's Cross-App Solutions feature allows a Smart Walk-Thru to start in one system and continue in another, using shared WalkMe data and conditions that trigger the next guidance flow.support.walkme.com+1

• Best for: orchestrating a guided process across multiple enterprise systems.
• Important caveat: cross-app data sharing must be enabled, and the systems must meet the same-browser and environment requirements.
• Official Cross-App Solutions documentation

What your email → CRM → ERP journey should look like

1. Email

Identify a customer request, extract the relevant details, and launch the workflow.

2. CRM

Guide the user to find or create the customer record and complete required fields.

3. ERP

Continue with the appropriate order, invoice, purchasing, or approval process.

The key distinction is between guiding users across applications and automatically transferring data or executing transactions. Cross-app guidance can direct the user through the steps, but reliable data transfer and automated actions may require application integrations, APIs, or workflow automation.

My recommendation

Start by evaluating Whatfix and WalkMe side by side. Both have documented cross-application capabilities, but the best choice depends on whether your email, CRM, and ERP are browser-based, native desktop applications, or a mixture.

One question will help narrow this down: Which email, CRM, and ERP products are you using? For example, Outlook → Salesforce → SAP, or Gmail → Dynamics 365 → Oracle. The exact applications matter because cross-app support varies by platform and deployment type.

Key Evaluation Criteria Before Choosing:

1. Browser vs. Desktop Support: Ensure the tool supports the exact environment your email client runs on. If your team uses Outlook Desktop alongside web-based CRM/ERP tools, you need a DAP that bridges desktop client layers and web browsers natively.
2. State Persistence: Verify how the tool handles authentication boundaries or page reloads when jumping from the email wrapper into the CRM and ERP.

If you'd like to narrow this down, let me know:

• Are your email, CRM, and ERP running entirely in the web browser or a mix of desktop and web apps?
• Which specific platforms (e.g., Outlook, Salesforce, SAP S/4HANA) make up this workflow?

I can help outline how implementation differs for your exact tech stack.