Vela
Also known as: Vela (tryvela.ai), try_vela_ai
AI scheduling assistant you CC or text that books, reminds and reschedules meetings across email, SMS, WhatsApp, Slack, Teams and phone, and can run recruiting interview scheduling from a pipeline.
Vela is an AI scheduling assistant for professional services and high-volume recruiting teams. Users copy vela@yourdomain.com onto an email, SMS or WhatsApp thread, or text or message Vela directly, and it takes over the coordination. It reads the thread and the connected calendars, pulls availability from every participant, proposes times in each person's time zone, follows up when people go quiet, books the meeting, sends reminders and reschedules when plans change. It works across email, SMS, WhatsApp, Slack, Microsoft Teams and phone.
For recruiting operations, Vela can watch a pipeline and act on its own. In one staffing deployment it detects when a candidate moves to the interview stage on a Monday.com board, reads interviewer availability from a Google Sheet, calls the candidate and falls back to email, sends separate calendar invites to candidate and interviewer, and reschedules cancellations by phone, email or SMS, escalating to a person after repeated failed attempts. Teams configure it with plain-language instructions, including which follow-ups Vela may take without asking.
Vela is delivered as a cloud service and sold through demos. Its privacy notice commits to encryption in transit and at rest and bars its AI model providers from training on customer content.
Vendor details
Canonical URL
https://tryvela.ai
Category
Enterprise operations agent
Funding status
Pre-seed, Y Combinator (W26 batch). Investor lists differ by source: Crunchbase lists Y Combinator, CRV and Rebel Fund, while Vela's own materials cite Y Combinator, Pareto Holdings, Z Fellows and Cory Levy; the round amount is not disclosed. Based in San Francisco, founded by brothers Gobhanu and Saatvik Korisepati, with prior experience at Perplexity, AWS ML and BCG AI.
Company status
independent
Use cases & customers
Primary use cases
Target customers
Deployment options
Integrations
Works over email (Gmail and Outlook), SMS, WhatsApp, Slack, Microsoft Teams and phone; connects Google and Microsoft calendars, and in customer deployments reads and updates Google Sheets and Monday.com boards.
In practice
Your recruiters spend hours chasing candidates and interviewers for open slots. Vela watches the Monday.com board, reads interviewer availability from your Google Sheet, calls the candidate and falls back to email, then books the interview and sends reminders.
Your consultants lose time to back and forth emails just to book a client meeting. You CC Vela on the thread, and it reads the thread and the connected calendars, follows up when someone does not respond and books the meeting.
Your candidates cancel interviews at short notice. Vela attempts to reschedule by phone, email or SMS, carries on in whichever channel the candidate replies and escalates to a person on your team after repeated failed attempts.
Sources & related URLs
Agentic Index coverage score
6.0 / 14 capabilities · 43%
| Integrations & Tool Calling | Full |
|---|---|
|
The assistant acts in connected calendars, sheets, boards and messaging channels. In the staffing deployment, Vela connects to the client's Google Sheet, where interviewers post availability, and to the Monday.com board, where candidates move through the pipeline. It calls candidates by phone, emails and texts them, creates calendar invites and takes Slack instructions. Vela reaches Google Calendar and Gmail data through the Google API Services and connects Google or Microsoft calendars, with access the user can revoke. It works over email (Gmail and Outlook), SMS, WhatsApp, Slack, Teams and phone, and it reads and updates connected boards. Vela publishes no integrations directory, and the only credential scoping it describes is revocable calendar access. Sourcetryvela.ai/case-studies/scaling-interview-ops, /privacy, home; readread 2026-09-16 |
|
| Workflow Orchestration | Full |
|
Scheduling runs as a branching workflow with retries across channels, configured in natural language. In one staffing deployment, a pipeline change sets Vela to work. It pulls interviewer availability from the connected Google Sheet and calls the candidate by phone first, following up by email if they do not answer. It then books a slot, sends double blind calendar invites and sends reminders 24 and 2 hours before. On a cancellation it automatically attempts to reschedule by phone, email or SMS, continuing on whichever channel the candidate replies. The customer sets rules in natural language, such as first round interviews lasting 30 minutes and in person interviews 60, and a new client or role takes about 15 minutes to set up. The workflow falls back from phone to email, routes by channel and repeats reschedule attempts, and one system runs across clients. Vela names no versioning or debugging tools. Sourcetryvela.ai/case-studies/scaling-interview-ops, home; readread 2026-09-16 |
|
| Knowledge Grounding & RAG | Partial |
|
Scheduling decisions draw on the thread, calendars and sheets Vela is connected to, assembled at run time. Vela reads context from the thread it is copied on and reads the user's calendar. In the staffing deployment it reads interviewer availability directly from a connected Google Sheet, the source of truth, and matches candidates to open slots by time zone, duration and location. It sees only the conversations and calendars a user brings it into. Vela names no maintained index, knowledge base or citations for its answers. Sourcetryvela.ai/case-studies/scaling-interview-ops, home, /privacy; readread 2026-09-16 |
|
| Human Oversight & Guardrails | Full |
|
After multiple failed attempts, Vela escalates to a person on the team. It holds a permission step by default, and the customer can lift that step for a named type of action through natural language instructions. One customer told it, on rejection, to call the candidate back immediately to reschedule without asking permission. Autonomy is set per action this way. Vela's terms warn that AI generated suggestions can be wrong and leave the user responsible for reviewing outputs and final decisions, such as sending a message or confirming a time. Vela does not say whether approvals can be routed to other channels. Sourcetryvela.ai/case-studies/scaling-interview-ops, /terms; readread 2026-09-16 |
|
| Security, Identity & Governance | Partial |
|
Administrative, technical and organizational safeguards protect customer data, including encryption in transit and at rest. Vela's AI providers are contractually prohibited from training their models on customer content. Google user data follows the Google API Services Limited Use requirements, and people read it only in listed cases. Calendar access can be revoked at any time, and integration data travels over encrypted channels, with encryption at rest required of providers. Vela names no certification or attestation report and no customer facing access model, such as roles, SSO or SAML. Sourcetryvela.ai/privacy, /terms, /trust (404); readread 2026-09-16 |
|
| Observability & Auditability | Partial |
|
Operations teams get one dashboard over the scheduling work and a measure of time saved. In the staffing deployment, the operations team went from monitoring 17 systems multiple times a day to checking one dashboard. Once deployed, Vela measures the actual time it saves, and reminders and confirmations go to all parties. Vela names no step by step view of what it did, no activity history per meeting and no audit log of what it sent and changed. Sourcetryvela.ai/case-studies/scaling-interview-ops, home; readread 2026-09-16 |
|
| Memory & State Persistence | Partial |
|
A scheduling conversation carries across channels. In the staffing deployment, if a candidate replies to a confirmation email or calls back the number that contacted them, Vela continues the conversation across channels. Customers write standing natural language instructions for each workflow, and scheduling preferences are among the information Vela collects. Vela names no memory layer and no way to review, edit or delete what it remembers. Sourcetryvela.ai/case-studies/scaling-interview-ops, /privacy; readread 2026-09-16 |
|
| Deployment & Data Residency | Not documented |
|
This is a cloud service, run by a company headquartered in the United States that may process personal information in the United States and other countries, with Standard Contractual Clauses where required. No hosting region is published, and Vela names no residency choice or customer hosted option. Sourcetryvela.ai/privacy, /terms; readread 2026-09-16 |
|
| Prebuilt Agents / Templates / Packs | Not documented |
|
One scheduling assistant, configured per client, is the whole offer, sold as one assistant for all your meetings from end to end. In the staffing deployment, the customer sets up each client's workflow in natural language instructions in about 15 minutes. Vela publishes no catalog, template library or set of agents to adopt separately, and the site has only three case studies. Sourcetryvela.ai home, /case-studies/scaling-interview-ops, /sitemap.xml; readread 2026-09-16 |
|
| Triggers & Channel Coverage | Full |
|
Pipeline changes and calendar conflicts start Vela's work on their own, and people can also reach it through the channels they already use. In the staffing deployment, when a candidate moves to the interview stage on Monday.com, Vela detects the change automatically with no manual trigger. When a candidate cancels, it attempts to reschedule without human intervention. Vela also monitors availability in real time, reschedules automatically if conflicts arise and follows up when someone does not respond. Users start work by CCing vela@yourdomain.com on email, SMS or WhatsApp, texting Vela or messaging it on Slack. Vela does not say how it handles duplicate triggers. Sourcetryvela.ai/case-studies/scaling-interview-ops, home; readread 2026-09-16 |
|
| Model Flexibility & Routing | Not documented |
|
The service runs on unnamed third party AI models. Vela uses third party AI model providers to power features of the service, under terms that bar them from training on customer data, and lists them among its service providers. It names no model or provider, describes no routing between models and mentions no model choice for the customer or an admin. Sourcetryvela.ai/privacy; readread 2026-09-16 |
|
| APIs / SDKs / MCP Extensibility | Not documented |
|
Whether Vela offers an API is not public. The site has only three case studies and links no developer, docs or API page. Sourcetryvela.ai home FAQ; triedread 2026-09-16 |
|
| Testing, Debugging & Optimization | Not documented |
|
What Vela measures is the customer's outcome after it goes live. It tracks the actual time saved once deployed, a measure of the customer's scheduling load. The Scheduling Benchmark is a published study of scheduling emails, not a tool customers run. Setup happens in natural language with no test step, and Vela names no simulation, test run or scored evaluation of its own behavior. Sourcetryvela.ai home, /case-studies/scaling-interview-ops; readread 2026-09-16 |
|
| Browser / Computer-use | Not documented |
|
The assistant works through email, SMS, WhatsApp, Slack, Teams and phone calls, connected calendars, and connected Google Sheets and Monday.com boards. Vela names no browser, desktop or screen operation. Sourcetryvela.ai home, /privacy, /case-studies/scaling-interview-ops; readread 2026-09-16 |
|
The Agentic Index coverage score grades every vendor Full, Partial or Not documented against the same 14 buyer facing capabilities, from public evidence only. Each capability links to how all vendors in the index score on it. How this evidence is graded
Pricing
Not public; demo-led
Cost watchouts
Cost drivers would include seats and messaging or call volume across email, SMS, WhatsApp, and phone; the customer also carries SMS compliance obligations per the terms.
Variable cost rationale
Likely per seat plus messaging and call volume across channels; high volume interview scheduling would raise usage cost, though the unit was not retrieved this session.
Sales call required
Yes, required for paid access
Free / trial
No free tier or trial published; demo on request
Key ambiguities
Vela publishes no prices, so whether billing is per user, per meeting or by message and call volume is not disclosed. The home page's only commercial path is Book Demo.
Related vendors
- 11th Estate — Agentic platform whose AI engine scans markets, matches an…
- Abacum — FP&A platform for growing companies whose AI Modeler builds, edits…
- Adopt AI — AI native accounting and bookkeeping firm whose agents run…
- Aera Technology — Decision intelligence platform where an always on agent executes…
- Akro AI — On premise operational intelligence that automates document heavy…
- alfred_ — AI executive assistant that triages the inbox overnight and scores…
Alternatives to Vela
The closest documented capability profiles to Vela among enterprise operations agents tracked by Agentic Index, ordered by similarity on the same 14 point evidence the rankings use. No vendor pays for placement.
- ConverzAI5.0 / 14A lighter documented profile than Vela
- Idle Booking5.5 / 14Adds documented Prebuilt Agents, Templates & Packs
- Docyt7.0 / 14Adds documented Prebuilt Agents, Templates & Packs
- Kyrok6.0 / 14Adds documented Prebuilt Agents, Templates & Packs
- Mandel AI5.0 / 14Adds documented Prebuilt Agents, Templates & Packs
- Nominal7.0 / 14Adds documented Prebuilt Agents, Templates & Packs
Similarity is computed from each vendor's Agentic Index coverage score evidence, axis by axis, not from the totals. How this evidence is graded