Vela - AI Scheduling Agent for Multi-Party Coordination

TL;DR

TL;DR: Vela is an AI scheduling agent that handles multi-party, multi-channel coordination — loop it into email, SMS, WhatsApp, or Slack and it books, confirms, and updates meetings automatically without any back-and-forth.

Source and Accuracy Notes

• Product: https://tryvela.ai
• HN Launch: Launch HN: Vela (YC W26)
• Category: AI agent for scheduling and calendar management

What Is Vela?

Vela is a YC W26 startup building AI agents that handle the chaos of real-world scheduling. It plugs into your existing communication channels — email, SMS, WhatsApp, Slack, phone — and autonomously coordinates meetings across multiple parties, time zones, and calendar systems.

The core insight: scheduling is a constraint satisfaction problem. It starts simple with two people in one time zone, but explodes in complexity when you have five candidates, three hiring managers, and interviews scattered across multiple platforms with no direct communication between parties.

A staffing firm using Vela onboarded in 10 minutes and replaced hours of daily coordination work. Their coordinators previously managed hundreds of candidate-client interviews where each side needs separate email threads, separate Zoom links to avoid double-booking, and calendar invites connecting parties who never directly communicate. One interview reschedule cascades into four others. Candidates respond on SMS to threads that started on email.

Vela handles all of it: reads context, checks calendars, proposes times, follows up when people ghost, and rebooks automatically when schedules shift.

How Vela Works

The Integration Pattern

Vela acts as an intelligent participant in your existing workflows. You do not migrate to a new platform — you loop Vela into the tools you already use.

Communication channels Vela connects to:

• Email (Gmail, Outlook)
• SMS (via Twilio or integrated providers)
• WhatsApp Business
• Slack
• Phone (for voice-based confirmation)

Calendar integrations:

• Google Calendar
• Microsoft Outlook
• Apple Calendar

The Scheduling Flow

Vela follows a loop pattern for every scheduling request:

1. Recruiter sends one message to Vela
2. Vela reads context: role, candidates, requirements
3. Checks calendars across all parties
4. Proposes optimal times across time zones
5. Sends confirmations via preferred channel per person
6. If someone ghosts, Vela follows up
7. If something shifts, Vela rebooks and notifies all parties

What Vela Actually Handles

Vela’s agent reasoning handles the messy reality of scheduling:

• Unstructured natural language across multiple channels (email reply that contradicts SMS thread)
• Mid-solve constraint changes (a hiring manager cancels, cascading reschedules begin)
• Social dynamics that do not exist formally anywhere (a C-suite prefers formal 3-option proposals; a truck driver responds to WhatsApp voice messages)
• Channel switching mid-conversation (candidate responds on SMS to a thread that started on email)
• Calendar conflicts that are not visible until proposals are made

Setup Workflow

Getting Started

1. Request access at https://tryvela.ai — Vela is currently in early access mode
2. Connect your channels — grant Vela access to the communication platforms your team uses
3. Define your scheduling rules — constraints like working hours, buffer times between meetings, preferred meeting duration, and escalation paths
4. Loop Vela into your existing threads — forward or CC Vela on scheduling requests and let it take over from there

Configuration Parameters

Vela’s scheduling behavior is configured through a set of parameters:

• working_hours: Array of time windows like "9:00-18:00"
• timezone_aware: Boolean to enable cross-timezone coordination
• buffer_minutes: Gap required between consecutive meetings
• max_meetings_per_day: Upper limit on daily bookings per coordinator
• follow_up_delay_hours: How long to wait before sending a follow-up
• preferred_channels: Per-party channel preferences (candidates, hiring managers, coordinators)
• escalation: What happens if someone does not respond (e.g., notify coordinator after 48 hours)

Testing the Loop

Start with a low-stakes scheduling task — a single interview with two parties. Loop Vela in, let it propose times, confirm it handles the back-and-forth correctly. Scale up once the coordination pattern is solid.

Deeper Analysis

Why Scheduling Is Genuinely Hard

Most scheduling tools (Calendly, Cal.com, x.ai) solve the simple case: one person sharing their availability, another picking a slot. This works for two-party, single-channel scheduling.

The failure modes appear when:

• Multiple parties with different constraints — a recruiter coordinating five candidates and three interviewers is not booking a meeting; they are solving a multi-dimensional constraint satisfaction problem
• Channel fragmentation — when a candidate responds on WhatsApp to a thread that started on email, most tools lose the context entirely
• Mid-solve changes — one cancellation cascades into four rescheduled interviews, each with their own confirmation overhead
• Social dynamics — a C-suite executive expects a formal three-option proposal in an email; a logistics truck driver responds better to a WhatsApp voice message; neither behavior is captured in any calendar system

Vela’s agent approach handles these cases by treating scheduling as an ongoing coordination task rather than a one-time slot booking.

The Data Problem

The founders noted that the hardest part was not the agent logic — it was the data problem. Scheduling behavior varies enormously across populations. This suggests Vela has invested significant effort in building a coordination dataset that captures these differences.

A staffing firm using Vela for high-volume candidate-client interviews represents the sweet spot use case: frequent, multi-party, cross-channel, high-frustration coordination where manual effort scales poorly.

Competitive Landscape

| Tool | Approach | Best For | |---|---|---| | Calendly / Cal.com | Slot-sharing, self-service | Simple two-party booking | | x.ai / Clara | Email-based scheduling assistants | Single-channel, professional context | | Clockwise | Calendar optimization | Internal meeting optimization | | Vela | Multi-channel AI coordination agent | Multi-party, cross-platform, high-frequency scheduling |

Vela is the only tool in this list that treats scheduling as an agent task rather than a booking utility. The agent reads context, decides on actions, executes across multiple channels, and handles edge cases autonomously.

Practical Evaluation Checklist

• Does your scheduling involve 3 or more parties across different time zones?
• Are you managing candidates, clients, or external stakeholders who use different communication channels?
• Do reschedules cascade into multiple downstream changes?
• Is your coordination team spending more time managing scheduling logistics than doing the actual recruiting or selling or delivering?
• Do you need follow-up automation when people do not respond?

If you answered yes to 3 or more of these, Vela is worth evaluating. If your scheduling is mostly two-party with consistent channels, a standard scheduling tool is probably sufficient.

Security Notes

• Vela reads from and writes to your communication channels — ensure you review what data it has access to before connecting enterprise accounts
• Calendar data contains sensitive meeting content — verify Vela’s data retention and access policies
• Multi-channel integration means Vela potentially sees communications across email, SMS, and chat platforms — assess your internal compliance requirements before connecting sensitive channels

FAQ

Q: How does Vela handle calendar conflicts across different platforms?

A: Vela reads from Google Calendar, Microsoft Outlook, and Apple Calendar via their APIs. When a proposed time conflicts with an existing commitment, Vela automatically proposes the next available slot and notifies all parties.

Q: What happens if someone responds outside Vela’s connected channels?

A: Vela can only act on what it sees. If a stakeholder replies from an unconnected channel, that response will not be captured. The most reliable setup is connecting Vela to the primary channels all parties actually use.

Q: Can Vela handle timezone-aware multi-party scheduling?

A: Yes. Vela reads timezone information from calendar events and proposes times that work for all parties’ local time zones simultaneously.

Q: How long does onboarding typically take?

A: According to the founders, one of their first customers — a staffing firm managing hundreds of interviews — onboarded in 10 minutes. The constraint definition (working hours, buffer times, preferred channels) is the main setup step.

Q: Does Vela support custom approval workflows?

A: Vela can be configured with escalation paths. If no response is received within a defined window, it can escalate to a coordinator or send reminder notifications.

Conclusion

Vela solves the scheduling problem that Calendly and standard booking tools were not designed for: multi-party, cross-channel, high-frequency coordination where each reschedule cascades into multiple downstream changes.

The agent approach — reading context, making proposals, handling follow-ups, and rebooking when things shift — is the right mental model for real-world scheduling complexity. If your team is spending significant time managing scheduling logistics rather than doing the actual work, Vela is worth evaluating.

URL: https://tryvela.ai

Points: 59 on HN (YC W26 Launch)