Auxot
Tutorials Docs Pricing Login

Build your first Dashboard

Pin the answers that matter — sales totals, daily metrics, and 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 Admin-Agent pasted plans — ordering first widgets wisely, tightening widget prompts so refreshes produce the same shape, and sketching the Monday scan without pretending dashboards build themselves.

Audience Admins · Executives
Time ~5 min
Prerequisites An Auxot account on any tier. At least one custom agent ([Create an agent from scratch](/tutorials/create-an-agent-from-scratch)) 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 ≥2 widgets — each pinned question still needs an agent wired for it — so **your clicks** assemble a skim-friendly board instead of juggling browser tabs.

When a tutorial shows italic text in quotation marks, it usually mirrors a label or helper string inside Auxot. Product copy changes between releases — if something reads differently in your workspace, trust what you see on screen.

Callouts with a Worth knowing gold accent are meant as must-read context before you move on. Blockquotes that open with Tip are lighter, optional depth.

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, and what changed in our metrics this week.

A dashboard is where those repeat questions live. Each tile stores one prompt you wrote (or pasted after Admin Agent drafts it) plus which agent runs it. Auxot reruns that job on the schedule you set; widgets don’t run on their own.

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

Today, assemble one board with two tiles. The next time you open Dashboards, the numbers reflect whatever refresh jobs ran since you last looked; the page doesn’t recompute on its own when you open it. Pick refresh rates that match the value of the answer, since each refresh costs tokens (Stay ahead of agent usage and cost).

A dashboard holds widgets, and each widget pairs one agent with one repeatable prompt that Auxot runs on the schedule you configured. You write the wording; Auxot runs the job when the schedule says so.

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), and 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”), and pick a refresh frequency.
  5. Add a second widget: same flow, different question, maybe a different agent. Drag the widgets to arrange them.

Done? Tiles run on their timers: reopen whenever you want; simply opening the page isn’t what costs tokens unless your refresh cadence is aggressively short.

The agent can do that?

Drag-and-drop still happens in the Auxot UI. Before clicking Add widget, brainstorm in Admin-Agent chat (you paste first): the reply cuts blank-page paralysis and gives you copy/paste-able prompts.

1. Recommend starting tiles from today’s roster

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: Most people don’t finish a dashboard because they open the empty grid and don’t know what to put on it first. Paste once; the reply lists concrete widget recipes against the agents and context files you already have, simply because you asked. You still configure each widget in Add widget yourself.

2. Tight widget prompt drafts

Send after you picked the question:

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: Vague widget prompts return a different shape each time the widget refreshes, so you can’t scan the dashboard at a glance. Paste the shape you want once; tighten the literal wording yourself before you save a refresh cadence that wastes tokens.

3. “Monday briefing” scaffolding

Build me a "Monday morning briefing" dashboard plan. I want to know what happened over the weekend, what to focus on today, what's lost momentum, 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: Morning boards mix numbers and narrative: planning beats guessing tile order. Paste the ritual ask; borrow layout, agents, refresh hints. You still build each widget in the UI because chat never drops tiles for you.

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, and signups by source.
  • Line chart: trend over time. Best for: weekly signups, daily revenue, and pipeline value over the past month.
  • Table: structured rows. Best for: top deals, tickets needing attention, and contacts to follow up with.
  • Text (markdown): short prose summary. Best for: ”what changed since yesterday,” ”what to watch this week,” and qualitative briefings.

If the agent’s answer is in a clean format that matches one of these (a number, a list of items, or 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, an outage, or 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, and 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 View your audit logs 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,” or ”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,” or ”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: see Add your first context file.)
  • 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, or 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 (Give your agent its job description) or attached context files (Add your first context file): 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, or signups today).
  • A table widget showing the top items needing attention (deals to close, tickets to triage, or 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 earn its spot.

What’s next

  • → Set up an Escalation. When one of your widgets surfaces something that needs a human’s attention, escalations are how you route it.
  • → Run a workflow. Many pinned answers summarize work that started as workflow tasks; the board is easier to read when you already know how those jobs move.
  • → View your audit logs. The source of truth when a widget fails or shows unexpected output.
  • → Give your agent its job description. The agents your widgets use answer better with sharper Descriptions.

Reference

  • Pages in Auxot: Dashboards (/app/dashboards), individual dashboard detail (/app/dashboards/:id)
  • A widget is: one agent, one prompt, and one display type
  • Display types: metric, bar chart, line chart, table, or 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: Run a workflow, View your audit logs, Give your agent its job description
Browse all tutorials