Skip to content
ConversionIQ Docs

Get Started – Step 1: Select channels

Route

Section titled “Route”
  • Path: /get-started (step 1)
  • Parent: stepper.md

Historical design reference

Section titled “Historical design reference”

These Figma links are kept for legacy context only. If they differ from the onboarding docs or the shipped overlay, follow the docs and current implementation.

Purpose (business goal)

Section titled “Purpose (business goal)”

Let admins choose which channel types the workspace will support (what conversation sources to centralize).

User roles & permissions

Section titled “User roles & permissions”
  • Workspace Admin
  • Permission: channels.configure (TBD)

Reference: Roles & Permissions Model

Layout structure

Section titled “Layout structure”
  • Fullscreen overlay wrapper (see stepper.md)
  • Top-right controls (in overlay header):
    • Optional pill action: Chatti Live (opens the assistant panel within the overlay)
    • Close icon: exits the overlay (see overlay dismissal rules in stepper.md)
  • Step header: horizontal 3-step indicator (number + label) (interactive; see stepper.md)
  • Title + subtitle explaining channel selection (copy is UI-level)
  • Channel card grid:
    • Each channel type is presented as a ChannelCard: Component: Channel Card
    • Selection is controlled via an on/off switch in the card header (selected vs unselected)
    • Card bottom section shows the App name associated with that channel type
  • Primary CTA: Next (enabled only after at least one channel type is selected)
  • Variant: if the user opens Chatti Live, a right-side assistant panel is shown while keeping the step content visible.

Components used

Section titled “Components used”

States

Section titled “States”
  • Empty: no prior selections
  • Loading: load available channel connectors
  • Error: connector catalog unavailable
  • Complete: selection saved

Business logic (high-level)

Section titled “Business logic (high-level)”
  • Selecting a channel type (toggle on/off) creates/updates workspace setup intent.
  • Selection must persist so the user can navigate between steps and resume later.
  • Selected channel types must be reflected on Account > Channels (users can connect/configure channels there as well).

Domain refs:

API dependencies

Section titled “API dependencies”
  • GET /channels/connectors
  • PUT /workspaces/{id}/channel-selections

Enterprise constraints

Section titled “Enterprise constraints”
  • Channel availability may vary by contract/plan

Edge cases

Section titled “Edge cases”
  • Connector temporarily disabled

Security & compliance considerations

Section titled “Security & compliance considerations”
  • Do not expose connector secrets; selection is metadata only.

Reference: Security & Compliance

Analytics events (if applicable)

Section titled “Analytics events (if applicable)”
  • get_started.channels.selected

Reference: Analytics Events (MVP)