Let an agent propose times and chase the replies
Agent proposes meeting times, sends follow-ups, and confirms bookings while you focus on the actual meetings.
How it works today.
You send an email asking when someone is free. They reply with three options that don't work. You counter with two more. They pick one but ask to move it an hour later. You confirm, add it to your calendar, then remember to send a reminder the day before.
Each booking takes four to six emails over two days. You're managing this dance for client calls, vendor meetings, team check-ins, and interviews. The coordination work crowds out the preparation work that actually matters for those conversations.
Before you start.
All of it has to be true, or step one fails in a way that is annoying to debug.
- Email platform with API access or integration capability
- Calendar system the agent can read your availability from
- List of your standard meeting types with typical durations
- Email templates for your common booking scenarios
- Clear rules about your availability windows and buffer times
The steps.
Connect your calendar and email to the agent platform
Set up read access to your calendar so the agent can see your availability. Configure email integration so it can send and receive messages on your behalf. Test that it can see your existing appointments and free time blocks.
Define your availability rules and meeting types
Specify your working hours, buffer times between meetings, and blackout periods. Create templates for different meeting types with standard durations. Include your preferences for morning versus afternoon slots and maximum meetings per day.
Paste thisMy availability rules: [working hours], [buffer time between meetings], [maximum meetings per day]. Meeting types: [type 1 - duration], [type 2 - duration]. I prefer [morning/afternoon/no preference] for [specific meeting types]. Block out [recurring commitments] as unavailable.
Create email templates for proposing times
Write templates for initial outreach, follow-up messages, and confirmations. Include your standard language for proposing multiple time slots and asking for preferences. The agent will customize these with specific times and recipient details.
Paste thisEmail templates needed: Initial meeting request with 3 time options, follow-up when original times don't work, confirmation once time is agreed, reminder 24 hours before meeting. Use this tone: [your communication style]. Always include [standard meeting details like location/link].
Set up the booking workflow trigger
Configure when the agent starts the booking process. This could be when you forward an email asking to schedule, when someone fills out a booking form, or when you send a message with a specific tag. Test the trigger with a sample booking request.
Program the time proposal logic
Tell the agent how to select time slots from your available windows. Include rules about spreading options across different days, avoiding back-to-back external meetings, and considering time zones for remote participants.
Paste thisWhen proposing times: Offer 3 options spread across [time period]. Check for time zone differences and propose times that work for [your timezone] and theirs. Avoid proposing slots that would create back-to-back external meetings. If it's a [specific meeting type], prioritize [morning/afternoon] slots.
Configure the follow-up sequence
Set up automatic responses for common scenarios: when someone picks a time, requests changes, or doesn't respond. Include escalation rules for when the agent should loop you in instead of continuing the back-and-forth.
Paste thisFollow-up rules: If they pick one of the proposed times, confirm and add to calendar. If they request different times, propose 3 new options from available slots. If no response after [timeframe], send one follow-up then notify me. Escalate to me if more than [number] rounds of scheduling or if they request [specific scenarios that need your input].
Test the end-to-end booking flow
Send yourself a test booking request and watch the agent handle the full sequence. Verify it proposes appropriate times, responds to your replies correctly, adds confirmed meetings to your calendar, and sends reminders. Check that calendar invites include the right details and location information.
Set up monitoring and approval gates
Configure notifications so you see booking confirmations and can catch any issues. Set up approval requirements for sensitive meetings or external clients if needed. Create a dashboard where you can see upcoming bookings the agent has scheduled.
Paste thisNotification settings: Alert me when meetings are confirmed, when someone requests unusual times outside normal parameters, and daily summary of bookings made. Require my approval before confirming meetings with [VIP contacts] or meetings longer than [duration]. Send me weekly report of all scheduled meetings.
What you keep.
Automating the typing does not move the accountability. These stay with a person.
- Approving meetings with key clients or sensitive topics before confirmation
- Deciding whether to take a meeting when someone requests time outside your normal availability
- Updating your availability rules when your schedule or priorities change
- Handling complex scheduling requests that involve multiple people or special requirements
Once it works.
The first run is the demo. These are where the time actually comes back.
Connect booking requests from your website contact form directly to the scheduling agent.
Agent automatically sends calendar invites with video links and agenda templates based on meeting type.
Handle booking requests for your team members by connecting their calendars to the same workflow.
Agent escalates complex multi-person scheduling to a human coordinator while handling simple 1:1 bookings independently.
Run this next.
One workflow is a tip. Chained, they are how a week actually changes shape.
The work this replaces.
These are the O*NET work activities this workflow covers, and the categories of tool that address them.
