Agility Recovery — Storyline Interactive Click-Throughs (Salesforce & SalesLoft)

Overview

As part of the broader ^[1] onboarding training program, a dedicated Articulate Storyline course is planned to provide hands-on, interactive click-through training for the two primary sales tools used by Agility's team: Salesforce and SalesLoft. This module is separate from the Rise360 course content and requires coordination with Agility's internal tech stack owner.

Scope & Purpose

• Format: Articulate Storyline (interactive click-through simulations)
• Target Tools: Salesforce and SalesLoft
• Goal: Give new hires (primarily AEs and CSMs) guided, hands-on practice navigating the tools they will use daily — without needing live system access during onboarding
• Audience: Sales and customer-facing roles (AE, CSM, Recovery Manager, Tech Services)

Key Decisions

• Salesforce and SalesLoft were confirmed as the two priority tools for Storyline click-through development (other tools may be added later but were not scoped in this session)
• Gus Donelson acknowledged limited familiarity with Storyline's authoring process and deferred to Agility's internal tech stack contact to guide content decisions and provide source assets (e.g., screen recordings, workflow documentation)
• The tech stack contact may already have existing recordings or documentation that can seed the Storyline builds

Dependencies & Blockers

Action Items

• [ ] Gus Donelson — Connect Asymmetric team with Agility's tech stack person to initiate Storyline kickoff for Salesforce/SalesLoft modules
• [ ] Mark Hope — Coordinate kickoff call once tech stack contact is introduced; assess available assets and define click-through scope per tool

Production Notes

• Storyline click-throughs typically require more lead time than Rise360 content due to the need for screen-capture assets, branching logic design, and iterative QA
• If the tech stack contact has Loom or Zoom recordings of tool walkthroughs, these can accelerate the scripting and simulation-building process
• Consider scoping one tool at a time (e.g., Salesforce first) to allow for a pilot build before replicating the approach for SalesLoft

Related

• ^[2]
• ^[3]
• ^[4]
• ^[5]