A business phone system
with AI agents bolted on

Calls in the browser, an embeddable chat/voice widget on your site, and a caller agent that can work a CRM list when no one's around to. We built it for our own use first; you're welcome to try it.

Sign in with Google or Microsoft · no credit card · takes about a minute

Agents on the website and on the phone

Two places callers and visitors actually show up — the website and your phone number. Both surfaces share one knowledge base, one transcript log, and the same hand-off path to a human when the model is out of its depth.

💬

Website agent

An embeddable chat + voice widget. Answers from a knowledge base it builds by reading your site, supports real-time voice right in the browser, and asks for a one-time SMS code before starting a session so you don't get hammered by bots.

📞

Phone agent

A speech-driven auto-attendant. Callers say a name or department instead of mashing keys; they're routed to the right extension or team. Workspaces can optionally turn on an AI support flow for inbound calls (similar smarts to the website agent). Falls back to voicemail with a transcript when no one picks up.

🤝

Human hand-off

When the AI is stuck — or the visitor just asks for a person — the conversation transfers to a human with the full transcript and ticket context attached. Voice calls bridge seamlessly, so the visitor doesn't have to repeat themselves.

📱

Guest QR room calls

Print a QR code for a room, lobby, desk, or location. Guests scan, start a browser voice call, and your logged-in agents see where the call came from. If nobody is online, the guest leaves a message and the transcript becomes a ticket/email for the workspace owner.

🔗

LLM configuration MCP

Generate a private MCP URL per workspace for trusted assistants. Claude, Gemini, ChatGPT, Cursor, Copilot, and other MCP clients can read redacted settings, dry-run changes, update supported features, manage stations, extensions, groups, and maintain room QR cards.

A phone system that runs in the browser

The basics, done: in-browser softphone, guest QR room calls, phone-provider trunks, ring groups, voicemail, SMS, transfer, hold, conference. Nothing flashy — just the things you actually need a phone for.

🌐

Calls in your browser

Calls run right in the browser tab. No plugin, no desktop install. Works on a laptop or a phone.

🔢

Speech auto-attendant

Listens instead of asking callers to press 4. Falls back to the keypad if the recognizer flubs it.

📧

Voicemail with transcripts

Voicemails get transcribed and emailed to the right person. Useful after hours, useful when you're in a meeting.

📱

SMS

Send and receive SMS from your business number. Threads sync across the devices signed in to the workspace.

👥

Ring groups

Simultaneous, round-robin, or sequential ring. Route to whichever team owns the line.

🕒

Business hours

After-hours routing to voicemail, forwarding, or a custom greeting. Holiday calendars supported.

🔁

Transfer & hold

Blind and attended transfer, hold with music, three-way conference. The usual.

📡

US local numbers (paid)

On a paid PSTN tier, search and buy US local numbers in your workspace — SignalWire or Twilio, depending on how your administrator configured providers. Numbers attach as terminations for inbound routing.

🏷

Room QR calling

Admins generate saved QR cards for rooms or locations. A scan routes to a logged-in browser phone agent first; if nobody is online, MyDaddy.io captures a message, transcript, and owner email.

A caller agent that works your CRM list

If you have a stack of leads no one has time to call, this is what it's for. The agent dials, qualifies, and tries to book a meeting — or hands the call to a human if the prospect's actually ready.

How it works

It pulls leads from your CRM under filters you set — lead status, days since last touch, time windows, cooldown — runs the conversation, classifies intent, and writes the result back. It is not a replacement for a good rep; it's something to do the awkward first call.

  • Pulls from Zoho CRM (Leads or Contacts)
  • Call windows, max calls/hour, cooldown periods
  • Intent classification: interested / book later / not now / wrong person
  • Calendar booking via Zoho Calendar
  • Live transfer to a human rep when the prospect's ready
caller_agent_config
crm_module: "Leads"
lead_statuses: "Not Contacted, Contacted"
days_since_activity: 7
max_calls_per_hour: 10
time_window: "9:00 - 17:00 EST"
cooldown_hours: 24

Answers grounded in your own site

Point it at your website or docs. It reads, breaks down, and indexes the content; the agent looks it up and cites the page it came from. The answers are only as good as what you've published — we're not pretending otherwise.

  • Reads your site at a depth you configure
  • Looks up the most relevant page to answer from
  • Answers with source citations so you can verify
  • Custom tone and instructions per workspace
  • Caches repeat questions for faster answers
🤖
"Based on your documentation, the API rate limit is 100 requests per minute per API key."
Source: docs/api-reference.html

What it connects to

A few native integrations where we use the product ourselves, plus a Zapier bridge and a generic webhook for everything else. Grouped here by what they connect — telephony, CRM, helpdesk, automation.

All integrations →

Phone Providers

CRM Providers

Helpdesk Providers

Automation & Other

One snippet, and that's it

Enable the widget in your workspace settings, copy the ready-made embed code, paste it before </body> on your site, done. Verification, voice, chat, and the hand-off path are handled inside the iframe.

How it works

The snippet drops a small chat bubble onto your page. Chat and voice happen in an isolated frame — nothing of ours runs alongside your own code.

  • One-time SMS code before a session starts (keeps bots out)
  • Answers come from a knowledge base built by reading your site
  • Real-time voice right in the browser, with a live transcript in the chat
  • Hands off to a human agent when asked, or when the model is stuck
  • Agent name, greeting, and tone are configurable per workspace
📋

Your ready-to-paste embed code — with your key already filled in — is waiting in your workspace settings.

Open Workspace Settings

Settings → Web AI Agent → copy "Embed Code"

The widget is running on this page right now — chat bubble in the bottom-right corner.

Try it out. Verify with your phone number if you'd like to start a session.

Three steps to a workspace

Self-serve through the admin portal. Sign in with your work account and the portal provisions a workspace, embed key, and a first agent station for you.

1

Sign in with Google or Microsoft

Hit Create a workspace to land on /portal/signup/ and authenticate with your work email. No new password, no credit card.

2

Name the workspace

Pick a name (we pre-fill it from your email domain). The portal isolates the workspace, generates an embed key, and makes you the first admin.

3

Try the phone, drop in the widget

Open the browser phone from the dashboard, paste the widget snippet on your site, and invite the rest of your team — all under the same workspace.

Create a workspace Sign in

Already have an embed key or extension? Open the phone directly.

Want to give it a try?

Start with the website widget, add a phone number when you need one, and turn the caller agent on if it makes sense for your team.