# The email infrastructure for autonomous meeting scheduling.

Developers building scheduling agents need primitives to read availability requests, negotiate times across threads, and send confirmations. Loomal provides the email API so your agent can handle the entire back-and-forth of meeting scheduling without any human coordination.

## API Primitives used

### `mail_list_messages`

**Detect scheduling requests**  
Monitor the inbox for meeting requests, reschedule asks, cancellation notices, and availability checks from participants.

### `mail_get_thread`

**Load conversation context**  
Pull the full thread to understand who is involved, what times were proposed, what constraints exist, and what has been agreed so far.

### `mail_reply`

**Propose and confirm**  
Reply in-thread with available time slots, confirmations, or reschedule options. Keeps the entire negotiation clean and organized.

### `mail_send`

**Send invites**  
Send calendar invites, meeting confirmations, and agenda details to all participants once a time is locked in.

## Scheduling meetings is a tax on everyone's time.

The average professional spends 4-5 emails negotiating a single meeting time. Multiply that across a week of scheduling and you lose hours to logistical back-and-forth that produces zero value. Scheduling tools help but still require manual setup, link sharing, and follow-up when participants do not respond.

Developers building scheduling agents need email primitives that can read requests, reply with proposals, and send confirmations. Loomal provides `mail.list_messages` to detect requests, `mail.get_thread` for context, `mail.reply` to negotiate, and `mail.send` to confirm.

## How to build it.

### 01 `mail_list_messages`

**Detect scheduling requests**  
Your agent monitors the inbox with `mail.list_messages`, identifying emails that request meetings. It parses proposed times, participants, and constraints.

### 02 `mail_reply`

**Negotiate the time**  
The agent replies in-thread with available slots using `mail.reply`. It handles counter-proposals and resolves conflicts across multiple participants.

### 03 `mail_send`

**Confirm and notify**  
Once a time is agreed, the agent sends confirmations to all participants via `mail.send` with meeting details, agenda, and any prep materials.

### Example prompt

> "Check my inbox for any meeting requests from this week. Propose available slots from my calendar, confirm any that have been accepted, and send reminders for tomorrow's meetings."

## What developers build.

- **Sales demo scheduling**  
Build agents that receive inbound demo requests, propose available slots from your team's calendar, and confirm bookings — all via email, no scheduling link required.

- **Interview coordination**  
Build agents that coordinate multi-round interviews across candidates, hiring managers, and panel members via threaded email conversations.

- **Cross-timezone scheduling**  
Build agents that parse timezone information from email signatures and propose meeting times that work well for globally distributed teams.

- **Recurring meeting management**  
Build agents that send agendas before recurring meetings, collect discussion topics via reply, and distribute meeting notes and action items afterward.

## Why not use Calendly or Cal.com?

Scheduling tools require the other party to click a link and pick from a grid. That works for simple inbound booking, but not for the messy reality of business scheduling — where meetings are negotiated over email threads with multiple stakeholders, competing priorities, and constantly changing constraints.

Loomal gives you email primitives. Your agent reads the thread with `mail.get_thread`, understands the context, and replies naturally with `mail.reply`. No links to share, no portals to visit. The scheduling happens where the conversation already lives.

## Private by default

Meeting details stay in email threads. No third-party scheduling platform stores your calendar data.

## Scoped identity

The scheduling agent has its own mailbox. It cannot access unrelated conversations or sensitive threads.

## Logged interactions

Every proposal sent and confirmation made is logged. Clear audit trail for who agreed to what.