Skip to main content

Workflow Walkthrough

This walkthrough follows the most important product loop in Builder Insights:

capture in the field, sync safely, then review and operationalize the result in the admin portal.

1. Sign in​

Mobile​

  • open the mobile app
  • sign in with a valid allowed-domain account
  • land on the Home screen

Admin​

  • open the admin portal
  • sign in with the same system identity model
  • land on the dashboard

2. Choose or confirm context​

In the mobile app, the user should confirm event or session context before capture when relevant.

This is important because:

  • event metadata drives later filtering and reporting
  • session context improves the quality of insight interpretation
  • leadership views depend on accurate event attribution

3. Capture an insight​

The core field workflow is:

  • enter text or record voice
  • classify the insight type
  • choose product areas
  • set sentiment and priority
  • attach event or session context
  • save optimistically

Expected behavior:

  • local save happens first
  • the user gets confirmation without waiting on the network
  • drafts or pending items remain recoverable if the flow is interrupted

4. Handle offline and reconnect states​

If the user is offline:

  • insight creation should still succeed locally
  • pending count should increase
  • the UI should not imply data loss

When the connection returns:

  • sync should retry automatically or via manual sync tools
  • pending count should return toward zero
  • duplicate or corrupted items should not appear

5. Verify in the admin portal​

After sync, the admin portal should make the captured data visible in the right places.

Typical verification path:

  • open Insights
  • search or filter by event, product area, or recent content
  • confirm the new insight is present and readable
  • open the detail view if needed

Depending on the role and page, the data may also appear in:

  • dashboard summaries
  • leaderboards
  • world map and activity views
  • executive reporting

6. Act on the data​

The admin side turns captured information into operational or leadership value.

Examples:

  • identify recurring pain points
  • validate demand for a feature request
  • compare event outcomes
  • prepare executive summaries or exported reports
  • triage bugs or follow-up work

7. Report issues with the workflow​

If the loop breaks, capture where it failed:

  • login
  • context selection
  • local save
  • offline queueing
  • reconnect sync
  • admin visibility
  • reporting or export

Then log the issue with:

  • Operations > Bug Report Template
  • Operations > Bug Reporting Guide
  • Mobile App > Overview
  • Mobile App > Offline And Sync
  • Admin App > Overview
  • Shared Platform > Roles And Permissions