CXB Console is the operator surface of the CX Bridge platform. It is where teams create bots, configure campaigns, monitor calls, manage integrations, review recordings, and operate Agent Desk. CXB Console should stay thin in the right way: it owns user experience, form behavior, validation, display, and workflow ergonomics. CXB API remains the API and data source of truth.

​
Product Role

​
Main Workflows

WorkflowWhere it happens
Create and edit botsBot list, create bot wizard, bot detail page
Test call qualityBot detail test call and call detail review
Create campaignsCampaign wizard, CSV upload, number pool, dialler config, review
Monitor campaignsCampaign list, campaign detail, attempt reports
Review callsCall list, call detail, transcript, recording, events, analysis, QC
Manage carriersCarrier list, carrier create/detail, Exotel detail
Manage fleetFleet page and system settings
Configure providersSettings page for API keys, storage, fleet, Agent Desk, Agent Assist
Build CRM integrationsAPI Keys page and bot Integration tab
Manage knowledge basesKnowledge Bases pages and bot KB attachment
Operate human handoffAgent Console, Agent Desk metrics, supervisor views

​
Route Map

The route map lives in the Console app’s top-level router.
RouteSurface
/loginLogin
/dashboardAdmin overview
/dashboard/botsBot list
/dashboard/bots/createBot creation wizard
/dashboard/bots/:idBot detail, editing, integration guide
/dashboard/knowledge-basesKnowledge-base list
/dashboard/callsCall logs
/dashboard/campaignsCampaign list
/dashboard/campaigns/newCampaign creation wizard
/dashboard/carriersCarrier management
/dashboard/fleetFleet health/capacity view
/dashboard/api-keysCRM API key management
/dashboard/settingsSystem settings
/dashboard/usersUser management
/agent-consoleAgent Desk queue for agents/supervisors
Agent Desk routes are gated by the ADK feature flag and role-based access.

​
Important Modules

FileWhy it matters
src/App.tsxApplication routes, lazy-loaded pages, role-based layouts
src/api/client.tsShared Axios client, VITE_API_URL, JWT header injection, 401 handling
src/layouts/DashboardLayout.tsxAdmin dashboard shell
src/layouts/AgentLayout.tsxAgent console shell
src/pages/BotCreate.tsxBot creation wizard
src/pages/BotDetail.tsxBot detail, edit modes, integration tab
src/hooks/useBotForm.tsBot form state, defaults, validation, serialization
src/pages/CampaignCreate.tsxCampaign creation/edit wizard
src/pages/CampaignDetail.tsxCampaign monitoring and attempt review
src/pages/CallList.tsx / src/pages/CallDetail.tsxCall search, transcript, recording, metrics, events
src/pages/Settings.tsxProvider keys, storage, fleet, Agent Desk, platform settings
src/pages/ApiKeys.tsxCRM API key lifecycle
src/pages/KnowledgeBases.tsxKB management

​
Branding

CXB Console is white-label at build time. Client-specific values live under brands/<name>/ and are copied into the build by scripts/build.sh <brand>.
Brand inputPurpose
.envVITE_* config such as API URL, brand name, token key, theme colors
logo.pngHeader/app logo
favicon.pngBrowser favicon
CSS variablesInjected into dist/index.html during build
Do not hard-code client names, colors, favicons, or logos inside src/. That is how brand leakage happens.

​
Ops Usage Pattern

For production bot and campaign work, ops should follow this order:
  1. Configure provider keys, fleet URLs, storage, carrier numbers, and integration settings.
  2. Create or update the bot.
  3. Run test calls and review transcript, recording, events, latency, analysis, and QC.
  4. Create the campaign only after the bot passes test calls.
  5. Start with conservative concurrency, then raise it after observing fleet, SIP, and provider behavior.
  6. Monitor attempts, retries, failed calls, post-call pushes, and recording playback.

​
Engineering Rules

  • CXB Console should not invent state that CXB API does not store or return.
  • Keep client-specific behavior in brand config or server-side settings, not shared React code.
  • Keep bot/campaign forms explicit and reviewable; ops users need to see what will affect real calls.
  • Treat call detail as the source for debugging: transcript, event timeline, recording, provider latency, tools, RAG, QC, and CRM push.
  • Build and lint before deployment; existing legacy lint issues should be separated from new changes.

Create a bot

Ops guide for building production bots.

Create a campaign

Campaign setup and review checklist.

Test calls

What to verify before campaign launch.

Repos and boundaries

Where CXB Console ends and CXB API begins.