> ## Documentation Index
> Fetch the complete documentation index at: https://dialnexa.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# DialNexa Dashboard Platform Map

> Use the DialNexa dashboard platform map to understand Agents, Phone Numbers, Batch Calls, Workflows, Integrations, Call History, Keys, and Webhooks.

The DialNexa dashboard platform map shows which tab owns each part of Voice AI operations. Agents design caller behavior, Phone Numbers route traffic, Batch Calls launch campaigns, Workflows automate lead paths, Integrations connect tools, Call History audits calls, Keys protects access, and Webhooks sends events.

<img src="https://mintcdn.com/dialnexa/0efoAN-6So4r-6NC/images/documentation/screenshots/dashboard-sidebar-full.png?fit=max&auto=format&n=0efoAN-6So4r-6NC&q=85&s=59c079b9336d0960a9553c97792a25d9" alt="DialNexa left sidebar showing workspace context, dashboard navigation tabs, help access, and profile controls." style={{ width: '100%', maxWidth: '1100px', margin: '8px 0 24px', border: '1px solid #e5e7eb', borderRadius: '6px' }} width="1586" height="1974" data-path="images/documentation/screenshots/dashboard-sidebar-full.png" />

<Note>
  This page is the map you open before clicking randomly. Random clicking is a traditional debugging method, but it does not deserve documentation glory.
</Note>

## What Each Main Tab Owns

Use this as the first routing table for the dashboard.

<CardGroup cols={2}>
  <Card title="Agents" icon="sparkles" href="/agents/overview">
    Create, import, organize, edit, test, publish, duplicate, export, move, and delete Voice AI agents.
  </Card>

  <Card title="Phone Numbers" icon="phone" href="/calls/phone-numbers">
    Buy or link numbers, assign inbound and outbound agent versions, manage SIP trunks, and place single outbound calls.
  </Card>

  <Card title="Batch Calls" icon="list-checks" href="/batch-calls/overview">
    Upload recipient CSVs, choose an outbound number, set schedule and retries, save drafts, and start campaigns.
  </Card>

  <Card title="Workflows" icon="git-branch" href="/workflows/overview">
    Build node-based automation with voice calls, conditions, wait times, application actions, leads, and lead history.
  </Card>

  <Card title="Integrations" icon="plug" href="/dashboard-integrations/overview">
    Connect available providers, validate connections, inspect actions, and request new integration coverage when enabled.
  </Card>

  <Card title="Call History" icon="activity" href="/monitoring/call-history">
    Filter calls, open details, play recordings, read transcripts, review extracted fields, inspect transfers, and export data.
  </Card>

  <Card title="Keys" icon="key" href="/api-access/api-keys">
    Create API keys, rotate access, create webhook secrets, and copy credentials that are shown once.
  </Card>

  <Card title="Webhooks" icon="webhook" href="/api-access/external-webhooks">
    Configure the workspace HTTPS endpoint that receives call events, retries, and delivery results.
  </Card>
</CardGroup>

## Sidebar Behaviors Worth Knowing

The left navigation changes state based on workspace context and account readiness.

| Behavior                | What users should expect                                                                                            |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------- |
| Workspace switcher      | Switching workspace changes the agents, numbers, campaigns, workflows, integrations, keys, and logs you can access. |
| Collapsed sidebar       | The sidebar can collapse to icons, but active routes still highlight the current product area.                      |
| Batch Calls readiness   | Batch Calls can be disabled until KYC is verified. If the tab is blocked, complete account readiness first.         |
| Wallet and profile area | The lower sidebar area exposes balance, recharge access, profile actions, and workspace settings where available.   |

## Move Through The Platform Without Losing Context

<Steps>
  <Step title="Start with the owner tab">
    Open the tab that owns the object you need to change: agent, number, campaign, workflow, integration, key, or webhook.
  </Step>

  <Step title="Publish before routing">
    For agent behavior, publish the version before assigning it to numbers, batch campaigns, or workflows.
  </Step>

  <Step title="Launch from the execution surface">
    Start one call, a batch, or a workflow from the page designed for that launch mode.
  </Step>

  <Step title="Confirm in Call History">
    Use Call History as the common proof layer after any live or test action.
  </Step>
</Steps>

## Navigation Confusions To Avoid

<AccordionGroup>
  <Accordion title="Webhooks versus agent webhooks">
    Use Webhooks for the workspace event endpoint. Use Agent Webhooks from agent settings when you only need to enable or disable webhook events for that agent.
  </Accordion>

  <Accordion title="Phone number assignment versus test call">
    A test call can prove the agent talks. Phone number assignment proves the right published version is routed for live inbound or outbound traffic.
  </Accordion>

  <Accordion title="Workflow status versus call status">
    Workflow status describes the automation. Call status describes one call inside that automation.
  </Accordion>

  <Accordion title="Integration connection versus integration action">
    Connection stores credentials. Actions are the actual things an agent function or workflow application node can perform.
  </Accordion>
</AccordionGroup>

## Related Reading

<CardGroup cols={2}>
  <Card title="Dashboard Overview" icon="layout-dashboard" href="/platform/dashboard-overview">
    Understand overview behavior.
  </Card>

  <Card title="Navigation Reference" icon="panel-left" href="/platform/navigation-reference">
    Read the navigation details.
  </Card>

  <Card title="Phone Numbers" icon="phone" href="/calls/phone-numbers">
    Route live traffic correctly.
  </Card>

  <Card title="Call History" icon="activity" href="/monitoring/call-history">
    Audit what happened.
  </Card>
</CardGroup>
