Tutorial 14

Build your first Dashboard

Pin the answers that matter — sales totals, daily metrics, weekly summaries — to one page you can check at a glance, with each answer drafted by the agent best suited to write it.

Plus: three prompts that turn the Admin Agent into your dashboard architect — recommending which widgets to pin first, drafting the prompts each widget should use, and turning your daily reading list into a single morning view.

Audience Admins · Executives
Time ~5 min
Prerequisites An Auxot account on any tier. At least one custom agent (Tutorial 07) that can answer the kinds of questions you'd want pinned. Helpful: a clear sense of what you'd want to look at every morning.
You'll end up with One dashboard with at least two widgets, each one an agent answering a specific question — pinned where you can scan it in ten seconds tomorrow morning.

Why this matters

Most of what you want from AI isn’t a one-off conversation. It’s the same questions, every day or every week: what did we sell yesterday, what’s the customer pipeline looking like, which support tickets matter, what changed in our metrics this week.

A dashboard is the page where those answers live. You pin one widget per question, and each widget is an agent answering that question — drafting the table, charting the data, summarizing the trend. The widget refreshes on whatever cadence you set, so the answer you see in the morning is the morning’s answer, not last Tuesday’s.

The page’s own helper text says it well: “Keep important answers in one place so you can quickly scan what matters.”

Today, build one dashboard with two widgets. Tomorrow morning, the dashboard tells you what’s going on without you opening anything else.

A dashboard is a named page that holds widgets. Each widget is one agent answering one question, displayed as a metric, chart, table, or short text summary. You decide what to pin, who to ask, and how often it refreshes.


Quick start

  1. Sign in — open Auxot in your browser and log in.
  2. Open Dashboards — click Dashboards in the left menu.
  3. Click New Dashboard — give it a name (something like “Morning briefing” or “Sales pulse”), pick visibility (Just for me or My team), create.
  4. Add a widget — click Add widget. Pick an agent, write the question you want it to answer (“Summarize this week’s customer support tickets in three sentences”), pick a refresh frequency.
  5. Add a second widget — same flow, different question, maybe a different agent. Drag the widgets to arrange them.

Done? You’ve got a working dashboard. From now on, every time you open it the widgets update with the latest answers — no clicking, no re-prompting.


The agent can do that?

The Admin Agent can’t create dashboards or widgets directly — those are UI-only actions. But he can help you decide what to pin and which agent should answer each question. Three prompts that turn dashboard-building from staring at a blank page into a guided conversation.

1. Have the Admin Agent recommend your first widgets

Open chat with the Admin Agent and ask:

I'm building a dashboard for my [role — e.g., "morning executive briefing"]. Looking at the agents and context files I have today, recommend three to five widgets I should pin first. For each one: what should the widget be called, which of my agents should answer it, what prompt should the widget use, and what display type (metric, chart, table, or text) the answer will probably land as.

Why it’s non-obvious: Empty-canvas paralysis is the real reason most people never build a dashboard. The Admin Agent already knows your agents, your context files, and what they’re each for. He can match those to the kinds of questions worth pinning — and gives you a starter dashboard sketch that’s specific to your account, not generic advice. Five-minute conversation; saves the “what should even go here” dead-end.

2. Have the Admin Agent draft a widget’s prompt

Once you know which question you want pinned, ask:

I want a widget on my dashboard that shows [describe the answer you want — e.g., "this week's customer support trends in three sentences, with the most concerning issue called out separately"]. Using my agent "[name]," draft me the exact prompt I should put in the widget's prompt field — tight enough that the agent gives me the same shape of answer every time it refreshes.

Why it’s non-obvious: Widget prompts are the part most people get wrong. Too vague (“summarize the week”) and the format jumps around every refresh — sometimes a paragraph, sometimes a list, sometimes a table — making the widget hard to scan at a glance. The Admin Agent writes a prompt tight enough to produce consistent shape, so the widget actually becomes scannable.

3. Build your “Monday morning” dashboard

Build me a "Monday morning briefing" dashboard plan. I want to know what happened over the weekend, what to focus on today, what's drifting, what needs my attention this week, and any red flags. Tell me which agents to use, which prompts to write for each widget, and what refresh frequencies make sense. Give me the whole sketch.

Why it’s non-obvious: Most people think of a dashboard as one number per cell. The Admin Agent can sketch the whole executive ritual — what your Monday morning really needs to see — and turn it into a dashboard you build in fifteen minutes. The kind of plan that takes a consultant’s hour to deliver, in one chat.


Go deeper

Widget display types — what each is good for

Auxot picks the display type automatically based on the agent’s answer. Five types show up:

  • Metric — a single number with optional label. Best for: revenue, open ticket count, signups today, anything that’s a clean “here’s the one number that matters.”
  • Bar chart — comparison across categories. Best for: revenue by product, tickets by team, signups by source.
  • Line chart — trend over time. Best for: weekly signups, daily revenue, pipeline value over the past month.
  • Table — structured rows. Best for: top deals, tickets needing attention, contacts to follow up with.
  • Text (markdown) — short prose summary. Best for: “what changed since yesterday,” “what to watch this week,” qualitative briefings.

If the agent’s answer is in a clean format that matches one of these (a number, a list of items, a sentence), Auxot picks the right type. If your widget is rendering as text when you wanted a chart, the fix is in the prompt — ask for the data more structurally (“give me a table with columns: …”) and the display will follow.

Refresh frequency — when to use which

The auto-refresh dropdown has seven options. Rough guide:

  • Manual only — for snapshots you’ll refresh by hand when you want them, not for ongoing monitoring.
  • Every 5 / 15 / 30 minutes — for live monitoring during an active situation (a launch day, a outage, a campaign in progress). Don’t leave on long-term — every refresh runs an agent job, which costs tokens.
  • Every hour — for fast-moving operational data: queue depth, active customer count, support ticket flow.
  • Every 4 hours — for data that updates throughout the day but doesn’t need minute-by-minute precision.
  • Every 24 hours — for daily summaries, KPIs, anything you’d check in the morning. Most morning-briefing widgets work great at this cadence.

If you want a widget to update on demand, leave it on a longer cadence and use the refresh button on the widget when you need a fresh answer.

Troubleshooting
  • A widget says “Error” or shows a blank. The agent failed to answer — check Audit Logs (Tutorial 12) for the job error. Common cause: the agent doesn’t have the context files or tools it needs to answer the prompt. Fix in the agent’s settings, then refresh the widget.
  • The widget renders as text when you wanted a chart. The agent’s answer wasn’t structured enough for Auxot to detect a chart shape. Edit the widget’s prompt to ask for structured data: “return a table with columns X, Y, Z” or “give me numbers per quarter as a bar chart.”
  • The widget rendered fine the first time but later refreshes look different. The agent’s output isn’t deterministic — it varies a bit each time. Tighten the prompt to lock the format: “always return exactly three sentences,” “always use a table with these columns,” etc.
  • You can’t drag widgets on mobile. Drag-and-drop is desktop-only. On mobile, widgets stack vertically — rearrange from a desktop browser when you need to.
  • “My team” visibility doesn’t show the dashboard to a teammate. Make sure they’re actually on the same team in Settings → Users. Cross-team visibility isn’t supported — each team’s dashboards are private to that team.
Variations & edge cases
  • All tiers support dashboards equally. No tier-locking on the feature itself.
  • Visibility is locked at creation. Just for me dashboards can’t later be made My team; you’d recreate them as a team dashboard and delete the personal one.
  • Only the creator can rename or delete a dashboard. Other team members can view it (if it’s team-visibility) but can’t change the structure.
  • Widgets are tied to specific agents. If you delete an agent that a widget uses, the widget will fail until you re-point it at another agent. Pick a related one and re-save the widget.
  • Each widget runs as a separate agent job — token costs scale with the number of widgets times their refresh frequency. A 5-widget dashboard refreshing every hour runs 120 jobs a day per dashboard. Pick refresh frequencies thoughtfully.
  • Mobile layout is presentational. Widgets stack vertically on phones in a fixed order; rearranging on desktop doesn’t change the mobile order until you save the layout from desktop.

Walkthrough

Step 1: Sign in

Open Auxot in your browser and sign in.

Step 2: Open Dashboards

Click Dashboards in the left menu. The page loads with the helper line: “Keep important answers in one place so you can quickly scan what matters.”

If you’ve never built a dashboard before, you’ll see the empty state explaining the concept: “A dashboard is a named page that holds widgets. Each widget is an agent plus a prompt plus a display type — so you are pinning answers (sales totals, pipeline tables, weekly summaries, and so on) where you can see them together.”

Step 3: Create a new dashboard

Click New Dashboard. If you’re on a multi-team account, a small modal asks for:

  • Title — what to call this dashboard. Something specific to its purpose: “Morning briefing,” “Sales pulse,” “Q3 KPIs,” “Customer support overview.”
  • Visibility:
    • Just for me — only you can see this dashboard.
    • My team — everyone on your team sees it.
  • Team — appears if you picked My team and you’re in more than one team.

Click Create Dashboard. Auxot drops you on the dashboard’s detail page — a blank canvas waiting for widgets.

(On a single-team account with no team picker, clicking New Dashboard just creates one with an auto-generated name and opens it directly. Rename inline by clicking the title.)

Step 4: Add your first widget

Click Add widget on the dashboard. A configuration card opens with the fields:

  • Title — a short label for this widget. “Weekly sales,” “Pipeline by stage,” “Open support tickets.”
  • Agent — pick the agent that should answer the question. The agent needs to have the context files and tools to actually know the answer. (If your sales agent doesn’t have your sales data attached, picking it as the agent for “Weekly sales” won’t work — Tutorial 04 covers attaching context files.)
  • Prompt — the question you want answered, every time the widget refreshes. “Summarize this week’s sales: top three deals, biggest deal size, total revenue.” Write it as if you’re asking a teammate.
  • Auto-refresh frequency — pick from Manual only, Every 5 min, Every 15 min, Every 30 min, Every hour, Every 4 hours, Every 24 hours. Most morning-briefing-style widgets work well at Every 4 hours or Every 24 hours.

Save the widget. Within a few seconds, the agent runs your prompt and the widget renders the result — as a metric, a chart, a table, or text, depending on what the agent’s answer looks like. (Auxot picks the best display type from the answer; you don’t have to choose.)

Tip: The first time a widget runs is usually the slowest because the agent is doing the work fresh. Subsequent refreshes are faster. If the widget shows an error, the most likely fix is in the agent’s job description (Tutorial 05) or attached context files (Tutorial 04) — not in the widget itself.

Step 5: Add more widgets and arrange them

Click Add widget again to drop another one in. Repeat for as many questions as you want pinned. A typical first dashboard has 3–5 widgets covering the day-to-day picture.

Once you have a few, drag the widgets around to arrange them. The grid is 12 columns wide on desktop — drag corners to resize, drag the header to move. Auxot saves the layout automatically.

A common layout for a “Morning briefing” dashboard:

  • One metric widget at the top showing the single most important number (yesterday’s revenue, open critical tickets, signups today).
  • A table widget showing the top items needing attention (deals to close, tickets to triage, contacts to follow up with).
  • A text summary widget with a one-paragraph briefing of “what changed since yesterday.”

Each widget refreshes on its own cadence. The page is yours.

Tip: Resist pinning ten things on day one. Start with two or three. If you find yourself ignoring a widget for a week, remove it — every widget on the page should pay rent.


What’s next

Reference

  • Pages in Auxot: Dashboards (/app/dashboards), individual dashboard detail (/app/dashboards/:id)
  • A widget is: one agent + one prompt + one display type
  • Display types: metric, bar chart, line chart, table, text (auto-detected from agent’s answer)
  • Refresh options: Manual only, 5/15/30 min, 1 hour, 4 hours, 24 hours
  • Visibility: Just for me (user-scoped) or My team (team-scoped)
  • Permissions: Anyone can create dashboards; only the creator can rename or delete; team members can view team-visibility dashboards
  • Tier: all tiers
  • See also: Tutorial 12: View your audit logs, Tutorial 05: Give your agent its job description