Integrations

A new piece.
Not a new silo.

Build Dialfyne into HubSpot, Salesforce, Close, Zoho, or the CRM you already run. Connect Claude, ChatGPT, Codex, or Cursor over MCP when you want the assistant to operate the workspace.
Built around your stackHubSpotSalesforceCloseZohoPipedriveAttioClaudeChatGPTCodexCursor

Built to sit in your stack

The layer you add.
Not a new system of record.

Build calling, email, and practice into HubSpot, Salesforce, Close, Zoho, or the CRM you already run. Connect Claude, ChatGPT, or Codex over MCP when you want the assistant to operate the workspace.

01

Keep the CRM you already run

HubSpot, Salesforce, Close, Zoho, Pipedrive, Attio, or whatever holds the account. Dialfyne sits on top. The system of record stays yours.

02

Keep the rest of the work where it is

Call outcomes, scores, and next steps can land in Slack, Sheets, Notion, calendar, or the tracker the team already opens.

Google CalendarSlackGoogle SheetsNotionAirtableMicrosoft Teams

03

Run it from the assistant you already use

Claude, ChatGPT, Codex, and Cursor connect over MCP. The assistant prepares lists, campaigns, coaching, and callbacks. A rep still takes the call.

Workspace-scoped credentials. Rep tokens are default-deny. Billing, number buys, and infrastructure stay out of MCP.

See the MCP connection

Remote MCP

The assistant you already use.
The workspace it could not reach.

Connect the Dialfyne MCP server in Claude, ChatGPT, Codex, or Cursor. Scoped credentials decide what the assistant can do. A human still takes every connected cold call.

01

Prepare the list and campaign

Import or select leads, scrub numbers against DNC, and prepare a team campaign. The assistant sets the work up. The team still runs the floor.

02

Hand the call to a rep

Click-to-dial opens the browser softphone. A human completes the conversation. The assistant supplies the handoff, not the voice on the line.

03

Coach from the transcript

Score a live call or a roleplay session, pull scorecards, and see rep progress. Practice rooms, skills, and knowledge stay in the same workspace.

04

See what needs a callback

Ask for open callbacks, session state, and coaching notes without exporting a spreadsheet.

05

Check the calendar

When Google Calendar is connected, the assistant can read availability and book. Confirm the workspace still has that connector enabled.

06

Watch usage and webhooks

Read wallet and usage status. Register or inspect signed webhooks. Billing changes, number buys, and infrastructure stay out of MCP.

Works with

ClaudeChatGPTCodexCursor

Each connection is scoped to one workspace. Admin credentials and default-deny rep tokens expose different catalogs. Credentials, billing mutations, phone provisioning, and infrastructure controls are excluded on purpose.

Connector library

The tools around the conversation.

Start with the supported CRM and calendar workflows, or use webhooks and APIs when the team already lives in another system.

Your stack, connected

Do not see your tool? Bring it anyway.

If the team already works in a CRM, a sheet, a channel, or an AI client, Dialfyne can sit next to it. We will map the objects, events, and MCP scope you actually need.