Amara Chukwu LXD
  • Home
  • About
  • Portfolio
  • Design Process
  • Resume
  • Blog
  • Contact
  • More
    • Home
    • About
    • Portfolio
    • Design Process
    • Resume
    • Blog
    • Contact
Amara Chukwu LXD
  • Home
  • About
  • Portfolio
  • Design Process
  • Resume
  • Blog
  • Contact

Call Documentation Practice: Kapture CX

View Case Study

Call Documentation Practice: Kapture CX

View Low-Fidelity Instructional Material Prototype

Detailed Case-Study

Call Documentation Practice: Kapture CX

 A realistic practice experience that helps existing Member Advocates document customer interactions accurately and completely while transitioning from Genesys to Kapture CX. 

Deliverable

 Rise 360 eLearning course featuring an embedded Storyline 360 practice scenario and a Google Forms reflection activity. 

Audience

 Existing Member Advocates who document customer calls in Kapture CX during or immediately after the interaction. 

Tools

  • Articulate Rise 360
  • Articulate Storyline 360
  • Google Forms
  • Microsoft PowerPoint
  • Canva

Responsibilities

  • Performance and task analysis 
  • Action Mapping 
  • Learning-objective development 
  • Instructional design 
  • Low-fidelity prototyping 
  • Text-based storyboarding 
  • Scenario and feedback writing 
  • Rise 360 development 
  • Storyline 360 development 
  • Google Form design and embedding 
  • Accessibility planning 
  • Functional testing and revision

Key Skill Demonstrated

 Transforming a software transition into realistic, performance-based practice instead of information-heavy system training. 

Project Overview

 Existing Member Advocates were transitioning from Genesys to Kapture CX in a high-volume, compliance-driven customer-service environment. They needed to learn more than where fields were located. They also needed to make accurate documentation decisions while handling realistic customer situations.


I designed a practice-first learning experience that allows advocates to work through the major documentation decisions they make during or immediately after a call. Learners select the correct call category and subtype, write notes, choose a disposition, receive immediate feedback, and reflect on how their documentation habits must change when moving from Genesys to Kapture CX.

The Problem

 Accurate call documentation depends on several connected actions. Advocates must:

  • Open the call-documentation area 
  • Select the correct call category 
  • Select the appropriate call subtype 
  • Enter call notes using the 4C rule 
  • Document actions taken 
  • Apply the correct disposition 
  • Review, save, and submit the record 


A traditional system demonstration could show learners where to click, but it would not give them enough practice deciding what information belonged in each field.


The design challenge was to help experienced advocates transfer their existing call-handling knowledge to a new documentation system without overwhelming them with unnecessary explanation.

The Solution

 I designed a short Rise 360 course containing an embedded Articulate Storyline scenario.

The scenario places the learner in the role of a Member Advocate handling a call about the status of a premium payment. Instead of reading a long explanation, the learner must:

  1. Identify the main reason for the call 
  2. Select the correct call category 
  3. Select the matching call subtype 
  4. Write complete call notes 
  5. Select the correct disposition 
  6. Reflect on how documentation in Kapture CX differs from documentation in Genesys 

Correct and incorrect selections lead to different feedback. Learners can retry decisions and apply the feedback before continuing. The final Google Forms reflection helps learners connect the simulation to their actual work.

My Process

1. Analyze the Performance Need


I began by defining what advocates must do in Kapture CX during or immediately after a live customer call.

I focused on the parts of the workflow that require judgment, including selecting categories and subtypes, deciding what belongs in the notes, and choosing the disposition that accurately represents the call outcome.


2. Build the Action Map


I connected the desired performance outcome to the actions advocates must complete on the job. This helped me avoid turning the course into a tour of every system feature.


3. Develop the Low-Fidelity Prototype


I used Microsoft PowerPoint to create:

  • A job-aid wireframe 
  • A scenario flow 
  • Sample decision points 
  • Correct and incorrect feedback paths 
  • A reflection activity 
  • Early screen and content structure 

The prototype allowed me to plan the learning flow before investing time in full development.


4. Write the Text-Based Storyboard


I created a detailed Storyline script covering:

  • Screen titles 
  • On-screen text 
  • Optional narration 
  • Visual direction 
  • Button labels 
  • Trigger logic 
  • Correct and incorrect feedback 
  • Text-entry activities 
  • Accessibility notes 


5. Create the Visual Mockups


I translated the low-fidelity structure into polished screens that reflected the Kapture CX workflow while using mock information instead of actual member data.


6. Develop the Experience


I built the course structure in Rise 360 and created the interactive scenario in Storyline 360.

The Storyline interaction was embedded in Rise so learners could move between supporting information, realistic practice, and reflection within one experience.


7. Add Reflection and Skill Transfer


I embedded a Google Form that asked learners to compare their previous Genesys documentation habits with the behaviors required in Kapture CX.


8. Test and Revise


I reviewed the experience for:

  • Navigation 
  • Trigger accuracy 
  • Correct and incorrect feedback paths 
  • Text-entry functionality 
  • Rise and Storyline integration 
  • Google Form access 
  • Readability 
  • Accessibility 
  • Use of sanitized information

Action Map

Business or Performance Goal


Support accurate and complete call documentation as existing Member Advocates transition from Genesys to Kapture CX.


Critical Job Behaviors


Advocates must be able to:

  • Open the correct documentation area 
  • Identify the customer’s primary reason for calling 
  • Select the correct call category 
  • Select the correct call subtype 
  • Write notes using the 4C rule 
  • Document information provided and actions taken 
  • Record the resolution or required next step 
  • Select the correct disposition 
  • Review, save, and submit the documentation 


Practice Activities


Learners practice by:

  • Reviewing a realistic customer-call situation 
  • Selecting a call category 
  • Receiving immediate corrective feedback 
  • Selecting a call subtype 
  • Writing free-response call notes 
  • Applying the appropriate disposition 
  • Comparing Genesys and Kapture CX documentation habits 
  • Identifying a behavior they will apply during future calls 


Essential Supporting Information


Learners receive only the information needed to perform the activity, such as:

  • Category and subtype guidance 
  • Documentation expectations 
  • The 4C rule 
  • Definitions of disposition options 
  • Examples of complete documentation 
  • Access to the applicable job aid

Guiding Principles Applied

Action Mapping


The activities focus on the actions advocates need to perform, rather than presenting every available Kapture CX feature.


Problem-Based Learning


Learners enter a realistic call situation and solve documentation problems through decisions and practice.


Scaffolding


The learning experience progresses from guided decisions and feedback to open-text documentation and reflection.


Adult Learning


The scenario is directly connected to the learners’ work and respects their existing customer-service experience.


Backward Design


The objective, activities, and feedback were built around the documentation behaviors advocates need to demonstrate on the job.


Mayer’s Multimedia Principles


The experience uses focused screens, short instructions, visual signaling, and segmented practice to reduce unnecessary information.


Skill Transfer


The reflection activity asks learners to compare the previous Genesys process with the expected Kapture CX process.

  • About
  • Portfolio
  • Design Process
  • Resume
  • Blog

Copyright © 2026 Amara Chukwu LXD - All Rights Reserved.