For the curious

What actually happens when you talk to a RubyVox agent

You speak. We listen, think against what you taught the agent, remember you next time, and can pass what you meant to the other tools you already use. Here is the whole picture, without the jargon.

The stack

Four parts, working together in real time

Every RubyVox agent is a loop of these four. Under a second, end to end.

Ears

Your voice is transcribed the moment you speak, so the agent can start thinking before you finish your sentence.

Brain

A language model reasons over what you said plus the knowledge you gave the agent (docs, FAQs, prices, policies).

Voice

A studio-grade voice replies out loud. You can pick a stock voice or clone your own from a short recording.

Memory

The agent quietly remembers returning callers, so the second conversation picks up where the first left off.

The map

Where RubyVox fits in your world

You are still the business. RubyVox is the layer that talks to your people and hands the work to the tools you already trust.

Your customer
phone · web link · QR
RubyVox
Agent + memory
earsbrainvoicememoryknowledge
Booking
Cal.com
SMS + leads
text back · log
Your tools
via MCP
Your CRM · calendar · inbox
the systems you already run on
Your customer — phone, web link, or QR code
RubyVox — the agent, its brain, and its memory
Actions — booking, SMS, lead capture, analytics
Your tools — Cal.com, your CRM, or anything MCP-speaking
Live today

What your agent can already do for you

Not a roadmap. This is what ships the moment you sign up.

Share a link or QR

Anyone can tap and talk in the browser. No install.

Real phone number

A toll-free number rings straight into your agent.

SMS follow-up

Agent can text a link, a confirmation, or a next step.

Books appointments

Cal.com booking mid-conversation, straight into your calendar.

Knowledge base

Upload docs. The agent answers from them, not made-up stuff.

Voice cloning

Record a short clip and the agent speaks in your voice.

Per-caller memory

Returning callers are recognized and greeted in context.

Templates by industry

Start from a real, working agent for your kind of business.

Usage caps

Per-call and per-day limits so nothing runs away from you.

Integrations

What RubyVox plugs into right now

Each one is on by default. You do not have to wire anything.

Cal.com

Books meetings straight into your calendar, mid-call.

Telnyx

Powers the phone number and SMS your agent uses.

ElevenLabs

The voice you hear, the ears that hear you.

Stripe

Handles your plan, overage, and receipts.

Supabase

Where your agent, its knowledge, and its memory live.

MCP (any tool)

Any tool that speaks MCP can drive your agent. See below.

The superpower

Let ChatGPT or Claude drive your agent for you

RubyVox speaks a shared language called MCP. That means you can point ChatGPT, Claude, or Cursor at RubyVox and ask them to do things: "pull last week's leads", "text the person who called at 4pm", "book Dr. Kim for Tuesday". Your AI assistant becomes your operator.

In the wild

What a full turn actually looks like

Three real shapes of conversation, start to finish.

A clinic, 9:47pm

A new patient calls, panicky. The agent listens, checks the intake questions the clinic set up, then offers the earliest available slot.

What Ruby did
  • Heard the caller's symptoms and insurance
  • Checked the clinic's intake knowledge base
  • Booked Tuesday 10am and texted the confirmation
A coach, 2:14am

A cold lead lands on the coach's site and taps the RubyVox link. The agent qualifies them without a form.

What Ruby did
  • Asked three qualifying questions in a warm voice
  • Logged a lead with name, goal, and budget
  • Sent a booking link by SMS
A dealership, Sunday

Showroom is closed. The phone still rings. The agent picks up in the dealer's brand voice.

What Ruby did
  • Answered stock and financing questions from the knowledge base
  • Captured the caller's number and the vehicle they wanted
  • Booked a Monday test drive on the sales manager's calendar
Guardrails

Where your data lives, and what keeps it safe

  • Every secret you paste in (API keys, calendar tokens) is encrypted before it ever hits the database.
  • Each agent is walled off from every other agent. Nothing crosses accounts.
  • Per-call and per-day caps mean a bad actor cannot burn through your minutes.
  • You can wipe an agent, its knowledge, or its memory in one click, anytime.
  • Sensitive fields (emails, phone numbers) are redacted from the audit log.

Now go build one.

Ten minutes from empty to a working agent with your voice, your knowledge, and a phone number that actually rings.