Customizable time savings per Journey run
Business problem
The current time savings displayed for Journey runs (e.g., 55 seconds) is often an underestimation because it doesn't account for external actions in the CRM that are now automated. This means we lack insights into the actual efficiency gains, such as the elimination of manual note-taking and case file research.
Desired outcome
The ability to manually set an estimated time saving for each Journey. This would allow us to more accurately report on the full impact of an automated workflow, based on the actual time saved per run.
Reminder: Insights help guide our direction. Votes and discussions help us understand demand, but don't guarantee development. Every insight receives a response within 30 days.
Discussion (1)
Sign in to join the discussion