Skip to main content

Summary

Use this page when you know roughly what area of the product you are in, but you want the fastest route to the right docs page.

Who this is for

Readers who need a fast lookup rather than a narrative guide.

Main product areas

Product areaWhat it coversBest doc entry point
DashboardWorkspace entry point, setup progress, quick actions, and recent activityUse the dashboard
AgentsAI-assisted roles used in campaign and communication workflowsCreate your first agent
CampaignsCampaign definitions, runs, goals, and templatesCampaigns
CommunicationsUnified review of email, SMS, and calls with shared contextManage communications
ContactsContact records, segments, and audience managementManage contacts
Data SourcesImports and syncs that feed contacts into the systemImport and sync data sources
AnalyticsIn-app reporting, issues, and published reportsAnalytics and public reports
SettingsOrganization, email, SMS, tags, and history configurationOrganization settings

Channel map

The current product direction is to center users on Communications and use channel filters or related views from there.
Channel questionBest doc page
How does email fit the model?Email
How does SMS fit the model?SMS
How do calls fit the model?Calls
How should I think about all channels together?Omnichannel communications

Admin and setup map

If you need to…Best doc page
set organization defaultsOrganization settings
configure email delivery or inbound handlingEmail settings and domain authentication
configure SMS setupSMS settings
manage teammate accessTeam management
review tagsTags
inspect the audit trailHistory and audit trail

Troubleshooting map

If the problem is about…Start here
onboarding getting stuckCommon onboarding issues
imported contacts or sync confusionIntegration and import issues
email verification or deliverabilityEmail deliverability and DNS
permissions or missing accessPermissions and access
report links behaving unexpectedlyAnalytics and report links

Important note about route names

Some route names in the app are transitional or more implementation-specific than the product story the docs should tell. Simple version:
  • trust the docs page names first
  • treat raw route names as secondary
  • use Communications as the stable mental model for day-to-day channel work