Skip to content

About

One booking layer for your team and its AI agents

Some of the meetings your team takes are now arranged by software: an assistant answering an inbound lead, an agent working through a list. We built rdv.dev so your people and your agents book through the same rules, the same fairness and the same calendars.

Start freeTalk to us
People and AI agents both book through rdv.dev, which applies the same rules, round robin and routing before writing to your team's Google and Outlook calendars.

People

A guest on your booking page

Agents

An AI agent, through the API or MCP server

rdv.dev

One booking layer

  • Same rules
  • Round robin
  • Routing
  • Never double-books
Your team's calendars

Google Calendar and Outlook, read live

  • SDR
  • AE
  • CSM

Our story

We sold B2B software, and lived with the tools

rdv.dev is built in Lyon by a small team that sold software to other businesses before building any. We booked demos, shared inbound leads between reps and handed new customers to customer success, on the same scheduling tools you probably use today.

Three things kept getting in the way.

  1. Round robin, priced per seat

    Sharing meetings fairly across the team meant paying for every rep in the rotation, often on a higher plan than the one we needed.

  2. Routing behind an enterprise plan

    Sending each lead to the right person took a sales call, an annual contract and a minimum number of seats.

  3. Agents that could not book

    Our AI assistants could research a lead and draft the reply, then stopped at the calendar and waited for a person.

So we built the booking layer we wanted: round robin and routing for the whole team at a solo price, an API, MCP server and webhooks that follow the same rules as rdv.dev itself, and every price on the pricing page.

See pricing

Principles

Five rules that settle every decision

Written down so that every “should we add…?” has an answer before anyone asks. They hold on every plan of rdv.dev, and nothing we ship may break them.

  • Scheduling and routing, nothing else

    No notetaker, no payments platform, no polls, no voice agents. One job, done properly.

  • Agents are first-class users

    The public API, MCP server and webhooks run the same rules as the app, on every plan. Nothing an agent can do is a paid upgrade.

  • Fail closed, never double-book

    If a calendar cannot be read, no times are offered. Overlapping bookings are refused by the database itself, not only by the code that checks for them.

  • Same features in every Team band

    Team plans differ by how many hosts they hold, never by what the product can do. A team of three gets the same routing as a team of fifty.

  • Every price is public

    No “contact sales”, no minimums, no SSO tax, no onboarding fee. A feature in your plan stays in your plan, and your price does not go up while you stay subscribed.

The company

Who answers for rdv.dev

rdv.dev is built and run by OPALITH SAS, a company registered in Lyon, France. The legal notice lists its registration numbers, the publisher and the host.

Read the legal noticeContact the team
Company
OPALITH SAS
Registered office
254 rue Vendôme, 69003 Lyon, France
Email
hello@rdv.dev

Questions

Questions about us

Another question? Write to us

Start with your own booking page

Connect Google Calendar or Outlook, set your weekly hours and share a page that never double-books. Add your team when you are ready.

Start freeSee pricing

Free for one host, no card needed. Team plans from €29 a month, VAT excluded.