Contextual answers(On the roadmap)
Ask about the job, customer or invoice in front of you, and get an answer from ShieldBook's own records, within your permissions.
AI in ShieldBook
Most AI in business software is a chat window that can't see the work. ShieldBook's direction is assistance and agents that understand the real record, act through the same permissions and rules as your people, and leave a name on everything they do.
ShieldBook's AI is direction, not a released feature. The foundation it stands on, permissions enforced on the server and a recorded history of every action, is built today.
01Why context matters
AI is only as useful as what it can see and what it's allowed to do. ShieldBook already holds the whole job on one record, with rules on every action. That's the difference between an assistant that guesses and one that knows.
02What it will help with
Everything in this chapter is planned direction. Each one builds on records and actions ShieldBook already has.
Ask about the job, customer or invoice in front of you, and get an answer from ShieldBook's own records, within your permissions.
Job summaries from a technician's notes, follow-ups after an estimate, invoice drafts from sold work. Prepared for a person to check.
Replies and follow-ups that know the history, drafted in your voice, sent only when someone approves.
Approved work not sold, visits to book, balances to chase, members coming due: surfaced before anyone asks.
Confirmations, reminders and outreach that start from what happens on the record, not from a timer polling for changes.
An office assistant, a dispatch agent, a lead agent: each with a narrow role, its own permissions and a person it answers to.
In development On the roadmapEverything else is built and working today.
03How an agent will act
An agent in ShieldBook is never a borrowed staff login and never a shortcut around the rules. It proposes through the same actions a person would use, the server checks its permissions, and anything consequential waits for a person.
An agent is its own actor with its own permissions. When it acts for a person, the history records both.
Agents use the same actions, permissions and business rules as people. There are no separate AI versions of anything.
What an agent did, when, and who it acted for, in the same activity history as everyone else.
An agent works inside one company's records and nowhere else.
One controlled interface for any capable AI. ShieldBook isn't tied to a single AI provider.
04Human oversight
Some actions change what a customer is promised, charged or told. When agents arrive, those will wait for a person, enforced by the server: an instruction in a prompt is guidance, never permission.
An approval boundary can be narrowed for a specific, proven workflow. It is never removed by default.
05Current and future
ShieldBook isn't building speculative AI ahead of the work. The operating system comes first, proven on real days in the field. AI arrives in steps, starting with reading and ending, for narrow jobs, with agents that run on their own within strict limits.
Customers, jobs, estimates, invoices and payments on one record, with rules on the server.
In place
Run a working service business on it, every day, before anything is automated.
Happening now
Every business action built once, permissioned and recorded whoever invokes it, and a structured history that grows with every job.
Happening now
Answers from ShieldBook's own records, within the asker's permissions.
Ahead
Drafts and proposals through the same actions people use, with a person approving what matters.
Ahead
A call-out, an approved estimate, a visit coming due: agents react, inside their permissions.
Ahead
Narrow processes that run on their own, with budgets, limits and stop conditions.
Ahead
In place today
The rules an agent will follow are the rules ShieldBook already enforces for people. That's why AI can come later without a redesign.
We'll show you the foundation in ShieldBook today and walk through where assistance and agents are going.
ShieldBook is being developed and proven inside a working service business as it prepares for broader use. A demo is a walkthrough and an honest conversation about fit.