For developers with an approved workspace

Connect your tools to Dialfyne workflows.

Use the remote MCP server, live-call scoring endpoint, and signed webhooks to connect a workspace to the tools you already run. The Developers page is the source of truth for your credential and its permissions.

Dialer

Run 1, 2, or 3 human-led lines per rep. The workflow keeps account ownership, call context, and outcomes together.

Platform Email

Guided setup covers your offer, prospect list, review settings, and sending infrastructure. Connected Email and Dialer workflows share suppression so an opt-out can stop later outreach across both channels.

CRM connections

Import records on demand and write matched outcomes back. Your CRM remains the source of truth. Import and writeback are explicit workflows, not blanket two-way sync.

Roleplay

Roleplay provides browser practice and coaching. The exact workspace catalog determines whether any scoped practice actions are available to your credential.

One connection, scoped to one workspace

Add the remote MCP endpoint to an MCP-capable client, then use the workspace credentials shown in Dialfyne. The server exposes approved workflows according to the credential scope. It does not grant access to another workspace or silently expand permissions.

Remote MCP
# Workspace-scoped remote MCP connection
claude mcp add --transport http dialfyne \
  "https://voice.dialfyne.com/mcp?clientId=<workspace>&apiKey=<key>"

# Or use the URL and credentials from your Developers page

Score live-call evidence from your own recorder

Send a transcript from a connected dialer or recorder to the live-call endpoint. Dialfyne can store the scorecard and compare the call with the rep's practice history when the workspace has that context.

  • Accept a transcript or an existing Dialfyne call reference.
  • Keep the result in the workspace call history.
  • Emit signed events your system can verify and handle.
Live-call scoring endpoint
curl -X POST https://voice.dialfyne.com/webhooks/live-call \
  -H "Authorization: Bearer <workspace-key>" \
  -H "Content-Type: application/json" \
  -d '{
    "transcript": "<call transcript>",
    "repEmail": "[email protected]",
    "source": "dialer"
  }'

Build around events you can verify

Register a webhook from the workspace tool catalog. Dialfyne sends signed JSON for supported call, score, Roleplay, and lead events. Verify the signature before your system acts on a delivery, and use the delivery log when you need to inspect a retry.

Builder questions

What is available to builders?

Dialfyne provides a workspace-scoped remote MCP server, a live-call scoring endpoint, and signed outbound webhooks. The MCP catalog and the Developers page show the actions available to your credential. There is no promise here of an unrestricted agent control plane.

What does the Dialer expose?

Dialfyne Dial is a human-led workflow with 1/2/3 configured lines per rep. Usage is measured in occupied line-minutes, including ringing, answering machine detection, live talk, and voicemail activity. An assistant can prepare approved work and read workspace data, but a person remains on every connected line.

How do Platform Email and CRM connections work?

Guided setup covers your offer, prospect list, review settings, and sending infrastructure. Connected Email and Dialer workflows share suppression so an opt-out can stop later outreach across both channels. Import records on demand and write matched outcomes back. Your CRM remains the source of truth. This is not blanket two-way CRM sync.

Is Roleplay a public MCP control surface?

Roleplay is a separate practice and coaching workflow. This page does not present it as an open public control surface. Check the exact tools and permissions shown for your workspace before designing around any Roleplay action.

How do I get the connection details?

Open the Developers page in your Dialfyne workspace. It provides the workspace-scoped MCP connection details, available tool catalog, live-call endpoint, and webhook reference for your credential.

Check the surface before you build against it

Open the Developers page to see the current MCP connection details, tool catalog, API references, and permissions for your workspace.

Open the Developers page