AI agentLive AISample data

Operations agent

Ask about jobs, revenue, and who sold what. It asks before it acts.

Same agent, same data. The viewer's role decides what it can see and do. Switching starts a new session.

Northbay Ops Agent

Viewing as the owner

Answers questions about the business and handles the follow-ups, with your approval.

Reads

Jobs, completions, and revenue
Paid and unpaid invoices
Rep leaderboard and commission
Service mix
Jobs with no seller

Does

Marks who sold a jobapproval, logged
Emails a rep their own commission summaryapproval, logged
Opens a follow-up taskno approval, logged
Drafts a customer email for the office to sendno approval, never sent

Guardrails

Scoped to the viewer. A rep sees only their own jobs and can only open follow-ups for themselves.
One action at a time, each on its own approval card. Decline and nothing changes.
Every action is logged in the activity feed, with what changed and where.
The portal's own records and email are the only things it writes. The field software is never changed.

Try a sequence

Each one is a starter under “Do” in the workspace.

1
Fix an attribution
Ask which August jobs have no seller, then assign one to Priya. It lists them, proposes the change on an approval card, and writes the correction only after you approve.
2
Email a rep their numbers
Ask it to email Marcus his June commission summary. It pulls only his jobs, shows you the numbers and the address, and sends when you approve.
3
Open a follow-up
Ask for a follow-up on the unpaid Walnut Creek job. That one is low risk, so it finds the invoice, opens the task, and logs it without a card.

portal.northbaycrawl.com/agents/ops

Northbay Ops Agent

Answers questions about the business and handles the follow-ups, with your approval.

Ready

ReadsJobsInvoicesRepsService mixCommission

ActsMark 'Sold by'Email rep summariesOpen follow-upsDraft customer emails

Ask me about jobs, revenue, unpaid invoices, or who sold what. I can also fix an attribution, email a rep their summary, or open a follow-up. I ask before anything that changes a record or contacts someone.

Ask

Activity

Ready

Every lookup, change, and approval shows up here as it happens. Nothing runs quietly.

What just happened

You approve
A consequential action pauses on a card: what it will do, which system it touches, and the risk.
It executes
On approve, the write runs against the portal's records or goes out as email. On decline, nothing changes.
It's logged
The result lands in the activity feed with an artifact: the record that changed or the email that went out.

Sample data

Northbay Crawlspace & Insulation is fictional: 315 made-up jobs from January 2025 through August 2026, with “today” fixed at September 2, 2026 so answers stay stable. Reps, customers, addresses, and dollar figures are invented. Actions write to an in-memory copy of the portal's records and reset on their own.

What this mirrors

A home-services company's agent on House Call Pro, with actions.

The real agent answers from 3,500+ synced jobs using lookup tools: job counts, revenue, paid and unpaid, per rep, per service.
The agent's actions write to the portal's own records and go out as email. Nothing it does can change a job in the field software.
The approval pattern mirrors the firm's accounting agents, where writes to QuickBooks and outbound sends are gated behind Approve and Reject cards.
Owner corrections of who sold a job are preserved across every nightly sync. The agent writes the same manual flag the portal's commission app uses.
Every action is audit-logged with what changed, which system it touched, and who approved it.
Answers are scoped to the viewer. An employee only sees their own numbers and can only open follow-ups for themselves; the owner sees the whole company.

Everything on this page runs on fictional sample data. No client names, no client numbers.

Want this for your business?

Every build is scoped to your tools and your team. Book a call and we'll show you the real thing.

Book a call Next demo: Bookkeeping agent