Decide who handles each next step
For C-104, the service owner confirms the appointment and records what the customer says. A team lead reviews whether the communication problem recurs. The customer should not have to reconstruct the history for every new staff member.
Define what happens when an owner is absent, a customer does not respond or a concern needs a restricted process. A route on paper is not enough; test it with fictional records.
Give access for the task
Support staff may need the relevant account history. Leadership may need aggregate patterns and selected approved evidence. Those purposes do not imply unrestricted access to every note or document.
Test source links, exports and shared views as well as the dashboard. A suitable summary should not open an unrelated private record through its citation.
Where analysis or routing is configured in Sopact, verify the actual behavior, ownership and limitations. Do not promise an alert, integration or access control simply because it appears in a course diagram.
Test one complete customer journey
Submit the fictional scheduling comment, review the service log, assign the response and record confirmation. Test a missing reply and an unauthorized account request too.
Prepare a short team learning note: what happened, what the evidence supports, what changed and what remains unknown. A positive customer response is useful without being treated as proof of a company-wide retention effect.
The completed plan should make follow-up and learning repeatable. The customer sees a meaningful response; the team sees a traceable issue and outcome; leadership sees the limits alongside the patterns.
Work through the Clearway example
This is a fictional teaching example. Adapt the fields and rules to the question your own workflow needs to answer.
| Reader | Needs | Responsibility |
|---|---|---|
| Customer | Clear response and next step | Confirm or clarify their experience |
| Service owner | Relevant sources and action status | Follow through |
| Team lead | Recurring patterns and gaps | Review process changes |
| Leadership | Scoped evidence and limitations | Choose justified action |
Build this part of your plan in more detail
These lessons address the next practical questions in this module. Choose the detail your workflow needs, then return to complete the exercise.
- How to Run a Continuous Stakeholder Feedback Loop
Follow an issue through action, a return to contributors and a later check.
- What Is Connected Data Intelligence?
Before repeating the workflow, test identity, source context, shared definitions, access and reproducibility.
More practical questions in this module (1)
- What Are AI Skills?
For a recurring analysis task, define reusable instructions, evidence rules, evaluation examples and review ownership.
Add this part to your plan
On workbook pages 6 and 7, run C-104’s issue from response to confirmation and team learning. Include a denied access test.
Download workbook (fillable PDF)Compare with a suggested answer
The owner records the action and customer response. Unconfirmed resolution remains visible. The team learns from the issue without exposing unrelated account data or claiming a measured retention gain.
Self-check: Can you show what the customer received and what the team learned?
Questions you may have
Is marking a ticket closed enough?
Only if the closure definition matches the question. Customer-confirmed resolution may require additional evidence.
Does course completion connect our systems?
No. It produces a plan and test cases for configuring and evaluating the workflow.
Apply the method to your work
Use the five-part plan to assess the sources, analysis and permissions your team needs. The solution page shows where a connected platform can support that workflow.
Explore the customer experience solution →