rocket_launch ASAPilot
Get Started

Dashboard Overview

The ASAPilot dashboard is the authenticated product experience at app.asapilot.com. The current route truth lives in apps/dashboard/src/App.tsx, and the public docs below are aligned to those shipped routes rather than old drafts.

What the dashboard is designed to answer

Recommended workflow

  1. Step 1

    Connect and verify an ASA account

    Finish the Apple Search Ads connection wizard, sync orgs/apps, and confirm the account shows as connected before starting analysis.

  2. Step 2

    Use Home to spot the next highest-risk item

    Read the budget radar, automation spotlight, and insights feed first so you are not starting from raw exports.

  3. Step 3

    Open Chat for explanation and follow-up analysis

    Turn a suspicious metric, CPI shift, or wasted-spend signal into a scoped conversation with streaming answers and agent traces.

  4. Step 4

    Create or refine recurring automations

    Promote repeatable checks into Daily Account Health, Daily Budget Guard, Daily Summary, or CPI Spike Alert workflows.

  5. Step 5

    Review Runs for proof and debugging

    Inspect queue status, summaries, payload context, and failures so automation quality stays measurable.

  6. Step 6

    Tune Settings and plan limits

    Adjust persona, audit thresholds, AutoPilot policy, and billing only after the core reporting loop is already working.

Access and gating

Protected product routes require authentication. Most product routes also require an active subscription. Billing exists inside the dashboard because checkout, plan status, and portal access are part of the normal product flow, not a separate back office.

Best next guides

Frequently asked questions

Where should a new operator start?

Start on Home to understand the current account state, then move to Chat or Automations depending on whether you need explanation or action.

Which dashboard routes usually need a subscription?

Most protected core routes require login, and many of them also require an active subscription.

Why is billing inside the dashboard flow?

Billing lives inside the product because checkout, plan state, and customer portal actions are part of normal operations.