Skip to main content
VantaSoft
Back to Insights

AI Agent Examples: 17 Real Agents and the Jobs They Do

AI agent examples by business function: the 17 agents that run VantaSoft, what each one does and when, where a person approves, and examples from eight other companies.

From our agent team 22 min read

Here are real AI agent examples, grouped by the job they do. At VantaSoft, 17 AI agents run our own company. One handles the inbox and calendar, one keeps the books, four work on sales follow-up and proposals, two look after customers, one runs content and four do engineering. The other four look after the company itself: security, compliance, our shared notes and the hunt for steps that still wait on a person. Each agent has a named job, its own logins, a schedule or trigger, and a person who approves the steps that matter.

After ours come examples from eight other companies, among them Microsoft, OpenAI, Epic in healthcare and Waymo in transportation, described from their own help pages and announcements. Everything about our agents comes from our own records as read on November 12, 2026.

If you are still choosing which job to hand an agent first, AI Agent Use Cases for Business sorts the options by role and industry. This post sticks to agents that are already doing the work.

AI agent examples by business function

Inbox and scheduling

Finance and billing

  • Graham, our finance agent, categorizes each company's new card charges at 7:00 and 7:30 every morning. He lists VantaSoft's past-due invoices every Monday and prepares each company's expense report on the 1st of the month. He can see the books and flag a deadline, but paying anyone is still a person's decision. His full week, and the six problems we hit, are in what our AI bookkeeper does every day.

Sales follow-up and proposals

  • Kyle, our outreach agent, sorts replies to our sales emails every 30 minutes, day and night, so an interested reply gets seen within half an hour. He also drafts follow-ups and sends a daily outreach report.
  • Taylor, our business development agent, reviews the sales pipeline at 7:00 on weekdays and researches the background for each day's sales calls at 8:00. The follow-up rules she and Kyle work by are in what an AI agent for sales can take off a small team.
  • Rafa reviews new government bids every night at 11:00 and drafts proposals. Every Monday he also gives Kyle a list of companies that recently won federal research awards and may need a software subcontractor.
  • Sam, our editor, works on proposal drafts, Rafa's included. She edits them for clarity, consistency and the bid's requirements before a person reviews them.

Support and customer delivery

  • The "Book a 30-minute call" button on this site opens a chat with a public version of Vance, kept separate from the one who works for us. He asks three questions about your work, answers what you ask and can book a call. When you leave your name and email or book a time, the founders get the conversation. He isn't counted in the 17.
  • Owen sets up our agent product for customers and ships the new versions our own agents run on. Every hour he checks that our agents' logins to outside services still work.
  • Reid, our project manager, tracks scope, milestones and customer sign-off. Every weekday morning he checks project timelines for slipping work, and he goes through project email twice an hour. His rules for what counts as at risk are in how to use AI for project management.

If support is the job you're weighing for your own business, AI Agent for Customer Service covers what to hand it first, and our customer support agent role spells out what that agent owns and what stays with your team. For the customers you already have, an AI account manager watches account health and drafts renewal reminders for your review. A person still decides discounts and renewal terms.

Content

  • Fiona, our content agent, runs the full editorial cycle for each of our two websites at 9:00 every morning: picking a topic, research, writing, editing, publishing and checking the live page. She also runs our company social accounts and reports the week's content results every Friday. She refreshed this article.

Engineering

  • Markus builds and maintains our own website, content system and internal tools. He checks his list of engineering tickets every 30 minutes.
  • Priya does engineering for our voice product. Every ten minutes she checks a live booking connection and flags it if bookings stop coming through.
  • Simone works on a client's software alongside one of our human engineers, and runs a monthly accessibility check on that client's website.
  • Leila tests the tickets assigned to her. She reproduces problems, re-tests fixes and recommends go or no-go before a release.

One more agent, Maya, runs on a separate cloud server and also works on that client's software. She is not part of our internal team, so she isn't counted here either.

Security, compliance and how we work

  • Nadia, our security lead, runs a security check across the agents every morning. She also tracks when our passwords and access keys expire, reviews who can reach what, and answers customers' security questionnaires. She reports problems and drafts the fixes, and changes to anyone's access still go to an owner.
  • Tobias, our compliance lead, checks our work against the terms of the AI providers we build on and the rules that apply to us, such as HIPAA for health information, the card industry's PCI rules and email and privacy law. He audits and drafts fixes. Compliance decisions stay with an owner, and he marks the questions that need a lawyer. He is our newest agent, added on November 12.
  • Walt, our director of knowledge, keeps our shared wiki accurate. Every morning he fixes broken links, merges duplicate pages and corrects anything that no longer matches how we work, and twice an hour he files new meeting notes into it.
  • Hana, our director of automation, looks for places where an agent sits waiting on a person and works out how to remove the wait or shorten it. She scans the previous day's approval requests and corrections every morning, and every Monday she sends one list of the tasks on our board that are still waiting on an owner. Removing an approval step still needs the owner of that part of the business.

On November 12, 2026, the 17 agents had 179 jobs set to run on a schedule, 153 of them switched on. Fifteen of the agents have scheduled work, and Sam and Tobias work on requests as they come in. Of the 153 switched on, 140 recur rather than running once on a set date. Fifty-three of those run several times a day, some as often as every minute, and 50 of the others fire before 9 a.m. Pacific, so their output is waiting when the owners start work. The schedule is what turns an assistant into a worker, because nobody has to remember to ask. When something needs attention, it comes to a person instead of the person going to look for it. How long it then waits for that person is in our count of 101 handoffs from agents to people. Deciding which jobs are safe to leave running is its own question, and we scored it out in the six-point test for what an AI agent can do on its own.

The 17 agents at a glance

Each of these is one agent with one job, running on our own hardware and reachable in Slack. The names stay consistent, so when someone says "ask Graham," everyone knows which agent and which area they mean.

AgentJob it ownsWorks inTypical output
VanceChief of staff: scheduling, inbox sorting, task list, coordinating other agentsEmail, calendar, Todoist, SlackMorning briefing, sorted inbox, new tasks
GrahamFinance: billing, money owed to us and by us, expenses, forecastingAccounting and card systems, SlackCategorized transactions, past-due lists, monthly expense reports
KyleEmail and outreach: strategy, sending, inbox placement, repliesMailboxes, sending platformSorted replies, outreach reports, follow-up drafts
TaylorBusiness development: researching accounts, finding and qualifying prospectsCRM, research tools, SlackProspect research, call prep, outreach drafts, pipeline review
RafaGovernment bid review and proposal preparationGovernment bid listings, document workspaceNightly bid review, proposal drafts, weekly leads for Kyle
SamEditing proposal draftsDocument workspaceEdited drafts ready for a person's review
OwenOur agent product end to end, plus customer setupsOur code, Linear (our ticket system), customers' serversCustomer setups, new versions for our agents, login checks
ReidProject management: scope, milestones, dependencies, customer sign-offLinear, emailStatus updates, flags on slipping work, closeout records
FionaContent and non-email marketing: research, search visibility, publishing, socialOur websites, Google Search Console, our social accountsPublished articles, social posts, weekly results reports
MarkusEngineering for our own website, content system and internal toolsOur code, Linear, our serversProposed code changes, code reviews, troubleshooting
PriyaEngineering for our voice productOur code, Linear, the product's error recordsBug investigations, fixes, checks before each release
SimoneEngineering on a client's softwareThe client's code, LinearFixes, new features, code reviews, monthly accessibility checks
LeilaQuality checks on assigned ticketsLinear, test copies of our systemsSteps to reproduce a problem, re-test results, go or no-go recommendations
NadiaSecurity: the agents' setup, access, keys and their expiry datesOur agents' settings, our codeDaily security check, access reviews, drafted fixes
TobiasCompliance: AI provider terms, health and card data rules, email and privacy lawOur policies and contracts, our agents' settingsCompliance reviews, a list of open items, drafted fixes
WaltKnowledge: keeping our wiki and the agents' written instructions accurateOur wiki, the agents' instruction filesFixed and merged pages, filed meeting notes
HanaAutomation: cutting how often an agent waits on a personOur task board, Slack, the agents' schedulesDaily automation scan, weekly list of owner asks

Two things about this list are worth copying. Every row describes a job rather than a tool, and no agent owns two areas. When we tried broader agents, the work that fell between them was the work that got dropped.

AI agent examples from other companies

These are products other companies sell or run. Each description comes from that company's own help page or announcement, read on November 12, 2026, so it is the company's account of what its agent does.

By business function

  • Inbox, meetings and scheduling: Microsoft's Facilitator agent joins a scheduled Teams meeting, takes notes everyone can edit and sums up decisions and open questions. It keeps an agenda timer, and if the meeting runs over, it says so and helps schedule a follow-up. It needs a Microsoft Copilot license. Source: Facilitator in Microsoft Teams meetings, Microsoft Support.
  • Finance and billing: Ramp's Agents for AP work on the bills you owe suppliers. They assign accounting codes to each line, check bills for signs of fraud before approval, sum up the vendor's history and recommend approval or a closer look, and pay eligible bills by card. Source: AP just became autonomous, Ramp, October 7, 2025.
  • Sales follow-up: HubSpot's prospecting agent looks for companies showing the buying signals you pick, finds the right contacts there and writes personalized outreach from your CRM data. You set which kinds of companies and people it goes after. Source: Set up and use the prospecting agent, HubSpot Knowledge Base, updated November 12, 2026.
  • Support: Intercom's Fin answers customer questions on your support channels from your help content and policies, in more than 45 languages. Intercom built a model into it that detects when to hand a conversation to a person. Source: Fin AI Agent explained, Intercom Help, updated November 2, 2026.
  • Content: HubSpot's content agent drafts blog posts, social posts, landing pages and other campaign material from your account data and brand voice settings. It doesn't publish anything on its own, so you review and edit every draft. Source: Create content with content agent, HubSpot Knowledge Base, updated November 6, 2026.
  • Engineering: GitHub Copilot takes a coding task, researches the project, plans the change and makes it in the background on a computer in the cloud, running tests as it goes. Developers can review its changes and ask for revisions before it opens a pull request. Source: GitHub Copilot on GitHub.com and GitHub Mobile, GitHub Docs.

By industry

  • Office work across a company: OpenAI's workspace agents let a team build an agent in ChatGPT, share it, and run it on a schedule for recurring work such as reviewing leads, summarizing support requests or producing reports. Admins can require a person's approval before an agent sends a message or updates a record. They are in research preview on ChatGPT's Business, Enterprise, Edu and Teachers plans. Source: Workspace agents, OpenAI.
  • Healthcare: Epic, which makes electronic health record software, has built AI for different people who use it. Emmie works with patients in MyChart, where they can schedule or reschedule an appointment by text and get answers to billing questions. Penny works with a hospital's billing staff and drafts appeal letters for denied insurance claims from the patient's chart, so the denial specialist starts from a draft. Sources: Emmie for Patients and Penny for Revenue Cycle and Operations, Epic.
  • Transportation: Waymo runs a fully autonomous ride-hailing service, with no human driver in the front seat, around the clock in cities including Los Angeles, Phoenix and the San Francisco Bay Area. Its Driver has more than 200 million miles of fully autonomous driving on public roads. Source: Waymo FAQ, Waymo.

Put these next to ours and the shape is the same. Each one does a single job inside the place where that job already happens, and most of them leave the final say to a person. Waymo is the exception, since nobody approves a car's next turn.

What counts as a real AI agent example?

A real AI agent example has four things a chatbot conversation does not: a defined job with an owner, its own approved logins to the systems where that job lives, the ability to start work on a schedule or when something happens instead of waiting to be asked, and a written-down point where a person approves or takes over. If any of the four is missing, what you have is a conversation. The same line, drawn against chat products that now call themselves agents, is in how a chat agent differs from an agent with a standing job.

This matters because an example that is a sentence long, such as "an agent that handles your email," leaves out which mailbox it reads, whose login it uses, whether it sends or only drafts, and what it hands to whom when it is unsure. Those details are the useful part of an example. We go deeper on how agents differ from other kinds of automation in AI Agents vs Automation vs RPA.

What access does each agent get, and where does a human approve?

Each agent gets only the logins its job needs, and actions with real consequences wait for a person. These are the standing rules we work under today:

  • Email replies to customers and prospects wait for a person. The agent drafts the answer, and an owner reads that specific message and approves it before it goes. Approval of one message never carries over to the next.
  • Moving money, changing live customer-facing systems and anything that cannot be undone need an owner's approval. Graham can see the books, prepare the report and flag the deadline, but a payment is a person's decision.
  • Taylor researches and drafts. Every email she writes to a prospect waits for an owner's approval, and she books a meeting only when the owner says to. The one exception is a sales messaging account of one owner's, where she answers replies and books meetings within his written rules and tells him when one is booked.
  • Rafa prepares proposals, and people keep signatures, pricing, commitments and submission. A proposal is a legal document, so the agent's work stops at the draft. Our look at how our proposal agent handles government bids shows each step and who decides it.
  • Nadia, Tobias, Walt and Hana find problems and fix what their role allows, such as a broken wiki link. A change to a rule, an approval step or someone's access needs an owner, and so does any compliance decision.
  • Passwords and access keys stay in each agent's own locked storage. They never go into a shared document, a summary or a message.
  • Some work runs without approving each item first, under written rules. Our outreach agent runs email campaigns to new prospects within rules on what the copy may claim, opt-outs and spending, and any new spending needs an owner. Our content agent publishes on this blog and our company social accounts with every claim sourced, no invented statistics and a check of the live page. Paid advertising still needs an owner.

If you are drawing the same lines for your own first agent, two posts are worth reading: What Access Should an AI Agent Have to Your Business Systems? and Human in the Loop for AI Agents, which goes action by action through what to gate and what to let run.

How do the agents hand work to each other?

They use three paths, chosen by how much of a record the handoff needs to leave.

  1. A task board. Since October 15, work that one agent hands another goes on a shared board by default, where each task lists the tasks it depends on. A step that pulls the research together waits for the research steps to finish instead of guessing.
  2. A ticket system. Customer setups and engineering work that was planned ahead go in our ticket system. Six of the agents check their own tickets there twice an hour.
  3. A direct question. For a quick factual question or a request to stop, one agent messages another and waits for the answer. We never use this path to hand off work, because a conversation is not a record.

Here is a concrete handoff. Every Monday morning, Rafa pulls together the companies that recently won federal research awards and may need a software subcontractor, and hands the list to Kyle through the shared board for his email outreach. Rafa knows government contracting and Kyle runs the outreach, so neither needs to learn the other's job. People tend to underestimate this part of running a team of agents, so we wrote the rest of it up separately in how our agents hand off work, what each handoff path costs, and the four that broke.

What does a customer's first agent look like?

Our 17 agents are where months of trial and error landed, and they were not the starting point. Our customers start with one or two. In their own words, the pattern is a recurring report that used to mean chasing someone.

Two public reviews of our Agent Service describe it better than we can. Michelle wrote:

One of the biggest wins has been our agentic Finance Director. Having an AI agent prepare and send me a 13-week cash flow report every Monday gives me greater visibility and confidence in where my business stands financially.

Max wrote:

We started with just one AI agent, and now we're planning to build at least 10 because we can already see how much it can improve our efficiency and customer service.

Both are 5/5 Google reviews, quoted verbatim. The first one has the shape of a good first agent: a named role, a specific artifact and a fixed day. A request like "help with finance" does not have that shape.

What broke, and what we changed

These three failures are more useful to you than the roster, because you are likely to run into them too. Five more, with the dates and what each one cost, are in what went wrong when we gave AI agents real work. The jobs we ended up taking away from agents altogether, and the five questions we now ask before assigning one, are in when to use AI agents and when not to.

An agent is only as good as the data you point it at

Our content agent chose article topics partly by how popular a phrase looked in search-box suggestions. On October 5 it scored one candidate at 826 that turned out to have 10 searches a month, while a candidate scoring 76 had 1,300. Its instructions were fine. The information it was given was the problem. We re-ranked the entire topic plan against real monthly search numbers and made that check mandatory before any article can take a slot. The same lesson applies elsewhere: when an agent keeps making the same bad call, check the information it was given before you rewrite its instructions.

Unreviewed output is worse than no output

Early on, every post got an AI-generated header image. Some were irrelevant, several repeated each other and a few had visible defects. Instead of hunting for better instructions, we added a scored review with minimum passing marks and a limit on retries, and we changed the default to no image unless a diagram, a chart of real data or a real screenshot genuinely helps the reader. Most posts now carry none, including this one.

Written instructions go stale

A stale instruction is worse than a missing one, because an agent trusts its own notes instead of checking how things work today. Our standing rule now is that when an agent finds written instructions that no longer match reality, it corrects them right away, without being asked. Since November 7 it has also been part of one agent's job. Walt reads what the owners tell the other agents each day and writes every standing instruction into the place that agent reads it, so an owner doesn't have to flag a correction for it to stick. What those written instructions add up to for each agent is in how to train an AI agent for your business.

Frequently asked questions

What is the best first AI agent example to copy?

Copy a recurring report with a named owner and a fixed day. It has repeatable inputs, a verifiable output and an obvious failure mode, so it is the easiest kind of agent to judge honestly after two weeks. Michelle's Monday cash flow report is the pattern to follow.

Is ChatGPT an AI agent?

A ChatGPT conversation on its own is an assistant: it works when you ask it something. OpenAI now also offers agents inside ChatGPT. Its workspace agents run on a schedule, use the tools a team connects and can be set to wait for a person's approval before they send a message or change a record, which is the same shape our agents have. The earlier ChatGPT agent, launched in July 2025, is no longer available, and OpenAI's help page points people to ChatGPT Work instead. Each of our 17 agents has a named job, logins to the systems that job needs, a schedule or trigger, and a person who approves the steps that matter.

What are the five types of AI agents?

Most lists of five types follow Stuart Russell and Peter Norvig's textbook, Artificial Intelligence: A Modern Approach. It describes four basic kinds of agent program (simple reflex, model-based reflex, goal-based and utility-based) and then shows how any of them can become a learning agent. Those types describe how an agent decides. For a business agent like ours, the job it owns and the point where a person approves tell you more.

How many systems should a first agent connect to?

Connect as few as the job needs, usually one or two. Each connection adds permission scope, failure modes and more output to review. AI Agent Integration walks through which of your systems are ready to connect and which will stall a build.

Do these agents replace employees?

No, and we do not use them that way. Every agent above has a human owner who directs it, reviews its consequential output and makes the judgment calls. The work that moved to agents was low-judgment, recurring and previously dependent on someone remembering.

Can one agent do everything instead of 17?

In our experience, one agent cannot hold those boundaries. Broad agents drop the work that falls between their responsibilities, and they make access scoping impossible, because an agent that does everything needs permission to everything.

What do these agents run on?

They run on Hermes Agent, free open-source agent software, on our own hardware. We explain what it is and why it suits business agents in What Is Hermes Agent?, and the project's own documentation is at hermes-agent.nousresearch.com/docs. How the software has held up for these agents is scored in our Hermes Agent review after running our own team on it.

Where to start with your own agent

Pick one recurring job that someone is tired of remembering. Name the owner, the trigger, the systems it needs, the output and the one action that must stay human. That five-line description is enough to build an agent from, and it covers most of what we ask for in a discovery call.

If you would rather not put together the software, hosting, connections and upkeep yourself, we can do that for you. We build the agent around your workflow, connect it to your systems, and host and maintain it from there. The build starts at $1,000 one time, and hosting and maintenance start at $475 a month, as listed on our pricing page on November 19, 2026. We compare doing it yourself with having it built in Build Your Own AI Agents or Buy a Managed Service?. When you are ready to scope one, you can book a 30-minute call about how your company runs.

Five quick questions about where your team's time goes. You'll get the one agent we'd start with, and what it would take off your plate.

Take the quiz

Put your first agentto work.

Agents designed around your tools, your access rules and your procedures, starting from the ones that run VantaSoft. It starts with 30 minutes on how your company runs.