A handful of native integrations for the tools we use ourselves, plus a Zapier bridge and a generic webhook for everything else. If we don't list it, the webhook path is probably the answer.
Bring your own carrier. Point any standards-based phone provider at MyDaddy.io for inbound numbers and outbound calls. Per-provider profiles in the admin portal handle sign-in credentials, audio quality preferences, and cost-based routing across multiple carriers.
Global phone coverage. Use Twilio numbers for inbound calls and route outbound calls through Twilio. Includes SMS via Twilio's Messaging API.
LiveDrop-in Twilio-compatible APIs at lower per-minute rates. SignalWire Spaces back our SMS gateway out of the box — set signalwire-space-url + project credentials and outbound SMS just works.
Direct carrier with strong international coverage and caller-ID name lookups. Configure a Telnyx connection (credentials or IP-based auth) and assign numbers to your workspace inbound profile.
LiveTier-1 US carrier favored for E911 and toll-free numbers. Add a Bandwidth voice subaccount; the auto-attendant honors caller-ID names the carrier provides.
LiveAny standards-based carrier works — your on-prem phone system, a regional carrier, a wholesale provider. Configure host, port, transport, credentials or IP-based auth, audio preferences, and phone-number list under Providers & Terminations.
LiveYour AI agents (web + caller) pull lead lists from your CRM and write back every interaction — ticket created, lead created, call logged, intent classified. Switch the active CRM per workspace under Settings → Integrations; the same agent flows pivot to whichever provider is configured.
Direct integration. The AI caller agent pulls lead lists by status / activity / cadence rules, the web agent creates Leads on session finalize with full visitor context, and post-call updates the Lead with the intent classification and chat transcript.
Live · DirectWire up lead_requested events through Zapier to any of 6,000+ Zaps. We POST a structured envelope; you map fields in Zapier without writing code. Same path covers Copper, Close, Freshsales, ActiveCampaign, etc.
If neither direct nor Zapier fits, point us at any HTTPS endpoint and we'll POST the same JSON envelope. Includes a signed header so you can verify it's really us.
GenericEvery web AI session and every escalated voice call lands as a ticket in your helpdesk of choice, complete with the request-context block (browser, page URL, UTM, referrer), the full chat transcript, and the agent's resolution status. When the AI hands off to a human, the agent picks up the same ticket — no re-keying.
Direct integration. Tickets created on every session start (routed by per-workspace department), updated on resolve with the full transcript, intent classification, and any visitor email submitted via the summary form.
Live · DirectNative API integration (REST v2). Same lifecycle as Zoho Desk: create-on-start, patch-on-resolve, status-sync from the agent UI. Per-workspace API key + subdomain configured under Settings → Integrations.
Liveticket_requested + session_finalized events flow through Zapier to whichever ticketing system you use. Field mapping happens in the Zap editor — no code, no waiting for us to ship a native connector.
Beyond CRM and helpdesk, MyDaddy.io publishes structured events you can pipe anywhere — Slack, Teams, Notion, internal data warehouses. The same event envelope drives our native integrations and the Zapier bridge, so adding a destination is a config change, not a deploy.
The catch-all bridge. Set crm-provider=zapier or desk-provider=zapier, paste in your Zap webhook URLs, and every lead_requested / ticket_requested / session_finalized event fires through Zapier.
Plain HTTPS POST with a signed header you can verify. Use it to fan events to Slack via incoming webhooks, to a cloud function, or to an internal queue. Same JSON shape as the Zapier bridge.
GenericSign in with Google Workspace or Microsoft Entra ID. Per-workspace single sign-on under Settings → SSO. Automatic user provisioning on first sign-in, group-to-role mapping, and optional domain lock.
LiveAI plumbing under the hood. OpenAI for language responses, Deepgram for speech-to-text, ElevenLabs for cloned-voice speech (with OpenAI as a fallback). Per-workspace voice choices and instructions; bring-your-own keys supported.
LiveBacking store for the AI agent's answers. The agent reads your website on a schedule, builds a per-workspace knowledge base, and cites the page each answer came from.
LiveIf there's no native integration and Zapier won't cover it, the custom-webhook path usually will. Drop us a note about what you're trying to wire up and we'll see what we can do.