Skip to content
All guides

How to onboard an AI agent like a new employee

An agent that books meetings and sends email needs a first day too: its own address, its own calendar, a job description and clear limits.

AgentMail says its in-house sales agent, Jordan, books demos and sends each prospect a custom quote 30 minutes before the call. In its newsletter, the company says that last Wednesday one prospect moved a call to Friday, and Jordan sent the quote 30 minutes before the previous time. With a calendar, AgentMail says, Jordan "would have probably not done that".

What AgentMail published

On Oct 15, 2026, AgentMail announced that every AgentMail inbox now includes a calendar. Its calendar webhook docs list the notices an agent gets as meetings are created, moved, started and ended. Its Agent News newsletter of Oct 29, 2026 (email only) explains why agents need one.

AgentMail's FAQ calls the calendar a beta in AgentMail Labs that an organization admin switches on, and it is live in the US only, with EU to follow.

Why a reminder is not a meeting

The newsletter puts the problem this way: "a reminder is often a timer the agent sets for itself, while something like a meeting belongs to other people too, and they can move it without the reminder being notified."

That matters because, in AgentMail's words, "Most of what an agent agrees to, like a demo or a renewal call, gets agreed in email." Once an agent agrees to something, it needs to know when that thing changes.

Per AgentMail's docs, when a meeting is rescheduled before it starts, the start notice moves to the new time and is "never sent early". Cancelled events do not fire at all.

You already know how to onboard someone

AgentMail's newsletter starts from a familiar scene: "When a new employee joins a company, the first thing that happens is that IT gives them a new email address and the rest of the Google Suite products, including a calendar and a drive folder." It argues agents should start the same way.

Microsoft's 2025 Work Trend Index uses the same frame: "Hire your first digital employees ... onboard them, assign ownership responsibilities, and measure their performance."

The analogy brings the rest of onboarding with it: a manager, a job description and limits. Our Oct 9 post on Google's Gemini agent covers one vendor's version.

The first-day kit for an agent

  1. 01

    Its own email address.

    Its mail stays separate from yours.

  2. 02

    Its own calendar.

    It books into its own space and invites you, so you accept or decline.

  3. 03

    A job title and a written role.

    Write a short paragraph on what it does and what it does not do.

  4. 04

    A named human owner.

    One person reviews its work.

  5. 05

    The least access that does the job.

    Start small and add permissions only when the role needs them.

  6. 06

    An approval rule.

    Anything risky, such as prices, offers or advice, waits for a person.

  7. 07

    A log you can read.

    It shows what the agent sent, booked and changed.

Access: let it see what it needs and nothing more

Start with your own calendar. Google offers "See only free/busy (hide details)" and Outlook offers "Can view when I'm busy". Either way, the agent sees that a slot is taken but not what it is. The newsletter's reason is that full access shows the agent your calls with lawyers and your one-on-ones about letting someone go. On a work calendar, Google notes that your administrator decides whether you can share it, so this may be your admin's call.

Next, keys and tools. Where a tool offers scoped API keys, start at read-only. AgentMail says its calendar keys can be scoped anywhere from read-only up to deleting events.

Then, who it talks to. AgentMail's newsletter describes an allow list and a block list that set whose invites the agent accepts and whom it sends invites to.

The catch: anyone can write to its inbox

The newsletter is candid about the weak spot: "Anyone with your agent's address can send it an invite, and the title and description go straight into its context."

OWASP calls this indirect prompt injection, where instructions arrive inside outside content such as websites or files. Its mitigations include least privilege access, human approval for high-risk actions, and keeping untrusted content separate and clearly marked. OWASP also says it is unclear whether prompt injection can be fully prevented. That is why the approval rule stays.

Give it a name tag and a paper trail

Microsoft's Entra Agent ID treats agents as "nonhuman identities" that need to be authenticated, authorized, governed and protected. Microsoft says "All agent authentication and activity is logged for compliance and audit."

Extending Entra security features to agents requires Microsoft Agent 365, which is included with Microsoft 365 E7 and sold as an add-on to Business Premium, among other plans. Read that as a sign of where large platforms are heading, not as something you need.

A small team can do the same at its own scale: one identity per agent, a named owner, and a weekly read of its log.

Seven ways an owner-led business could use an agent with its own seat

These are our own illustrative examples, built from the capabilities above, not results anyone has reported.

  1. 01

    Dental practice: scheduling coordinator.

    It books appointment requests into its own calendar, invites the front desk, and sees only free/busy on each dentist's calendar. Invite titles carry no patient details, and anything clinical waits for staff. The front desk gets less back-and-forth email.

  2. 02

    HVAC or home services: service scheduling coordinator.

    It books service calls and invites the assigned technician. When a customer reschedules, the update carries the previous time, so it confirms the new slot. Prices wait for the owner, and customers hear about the right appointment.

  3. 03

    Accounting or bookkeeping firm: client intake coordinator.

    It books onboarding calls for the accountant to accept and emails each client a Monday status update on missing documents. Anything financial waits for an accountant, who reviews instead of chasing.

  4. 04

    Law firm: intake scheduler.

    It accepts invites only from its allow list and proposes consultation times with free/busy only on attorneys' calendars. Invite titles carry no client or matter details, and anything legal waits for an attorney. Attorneys' calendars stay private.

  5. 05

    Real estate brokerage: showing coordinator.

    It books buyer calls and showings for the listing agent to accept, and sends the meeting link when an event starts, even if it moved twice. Offers and terms wait for the listing agent's approval, so a person still decides what gets confirmed.

  6. 06

    Property management: maintenance coordinator.

    It schedules allow-listed vendors and follows up when a visit ends to ask whether the job is done. Spend and new vendors wait for the property manager. Visits stay on schedule without the manager watching every thread.

  7. 07

    Marketing agency: account coordinator.

    It emails each client a weekly Monday status update, and when a client call ends it drafts a recap for the account lead to approve. It sees only free/busy on the team's calendars. Clients get regular updates, and the team spends less time on scheduling email.

This week

  1. 01

    1.

    Write a one-paragraph role for the agent you run or plan to run, and name its owner.

  2. 02

    2.

    Switch its access to your calendar to free/busy only, checking with your admin first if it is a work account.

  3. 03

    3.

    List every key it holds, and drop each one to read-only unless the role needs more.

  4. 04

    4.

    Set an allow list for who it accepts invites from and who it emails.

  5. 05

    5.

    Write down which actions wait for your approval, and pick a time each week to read its log.

Our take

Agent tools are starting to give agents their own addresses, calendars and identities, and the onboarding habits you already use for people carry over well. A short written role, a named owner, narrow access and a weekly look at the log matter more to us than any single feature.

No partnership with AgentMail or Microsoft is implied here.

Sources

AgentMail: Agents should have their own calendar, Agent News #035 (Oct 29, 2026), email newsletter with no public web version

AgentMail Blog: Your agent has an inbox. Now it has a calendar. (Oct 15, 2026)

AgentMail Docs: Calendar Webhooks (undated page, checked Oct 30, 2026)

Google Calendar Help: Share your calendar (undated page, checked Oct 30, 2026)

Microsoft Support: Calendar sharing in Microsoft 365 (undated page, checked Oct 30, 2026)

Microsoft Learn: What is Microsoft Entra Agent ID? (undated page, checked Oct 30, 2026)

OWASP Gen AI Security Project: LLM01:2025 Prompt Injection (undated page, checked Oct 30, 2026)

Microsoft WorkLab: 2025: The year the Frontier Firm is born (Apr 23, 2025)

Consultiply: Google's new Gemini agent can get its own work account. Treat it like a new hire. (Oct 9, 2026)

Know someone who should read this?

Send it to a colleague, or hand it to your AI assistant and let it tailor the advice to your business.

Send to a personHand it to your AI

Want this working in your business?

Tell us what you are trying to fix and we will point you at the smallest useful next step.

Talk to us