Customers want help, not another form.
Direct calls and emails matter. Recording the same interaction again adds work; usable case history must survive the handoff.
Meeting 01 · Insights & actions
Customer onboarding & support
Keep the personal service. Remove the chasing, re-entry and lost context.
Reported findings and proposed direction—not verified system behavior or approved delivery scope.
Meeting takeawaysWhat the discussion revealed
Scott’s directionMapped from his “Product Discovery Meeting” follow-up
Capture once; keep the human connection.
Capture support across channels, suggest classification and routing, and preserve the issue, response and resolution history.
Getting complete information is the bottleneck.
The customer contact may need several people to supply the data. Chasing gaps delays readiness; file conversion is only part of the problem.
Guide the customer through what is missing.
Show the next step and who holds missing information. Accept existing customer files and map them into the required imports.
Bad identifiers create rework; more fields are not always better.
Conflicting badges, provisional serials and changing asset names need confirmation. Department and shift needs differ by customer.
Reconcile identities and validate the handoff.
Surface conflicts for review. Ask for configuration fields when needed for reporting or access; verify records reach the right site and assets.
A technically uploaded checklist can still be unusable.
Missing failure-action fields and truncated questions can change meaning. A 62-character display limit was reported, not independently verified.
Protect meaning and device compatibility.
Preserve answers and failure actions. Confirm the display limit and hardware/firmware boundary before choosing a presentation fix.
Actions to take next
1. Walk one real onboarding account
Compare sent, returned, corrected and imported data. Identify missing owners and manual re-entry; confirm required fields.
2. Trace support and establish a baseline
Follow a case from first contact to closure; check history access and portal routing. Review ticket volumes and categories.
3. Shape two linked PRD workstreams
Onboarding and support. Carry validated problems into requirement sections, linked cards and product/engineering review.
Proposed follow-up; owners and dates are not assigned. Confirm checklist behavior and device limits before specifying a fix.