Only what exists, and how to use it.

No wall of logos. Leads come in by CSV, outcomes go out through a signed webhook your CRM can receive, and calls run on your own Telnyx account.

LiveCSV importLoad leads into named lists from a CSV file. Map the columns, check a small sample, then release the list to a session.LiveSigned webhooksEvery saved disposition can POST to your endpoint as a signed call.disposition event, for your CRM, a sheet or an automation tool.LiveCSV exportAdmins can export leads to CSV with contact, phone and address columns.LiveTelnyxCalls run on your own Telnyx account, numbers and caller ID.

PlannedTwilioBring your own Twilio account. Planned.

PlannedManaged callingCalling included in the plan. Planned.

Not availableNative CRM connectorsNot available. Use the signed webhook or CSV today.

The signed disposition webhook.

Set one endpoint and a shared secret in workspace settings. When an operator saves an outcome, DialBreeze POSTs the event, signs it with HMAC-SHA256 over the timestamp and body, and retries up to three times.

Signature header X-DialBreeze-Signature
Timestamp header to reject replays
Every delivery outcome kept in the audit log

import crypto from "node:crypto";

// rawBody: the exact request body string; secret: your webhook secret
export function verify(rawBody, timestamp, signatureHeader, secret) {
  const expected = crypto.createHmac("sha256", secret)
    .update(`${timestamp}|${rawBody}`).digest("hex");
  const given = signatureHeader.replace(/^sha256=/, "");
  return given.length === expected.length &&
    crypto.timingSafeEqual(Buffer.from(given), Buffer.from(expected));
}

POST https://your-endpoint.example/dialbreeze
Content-Type: application/json
X-DialBreeze-Event: call.disposition
X-DialBreeze-Timestamp: 1790000000
X-DialBreeze-Signature: sha256=<hex HMAC of "timestamp|body">

{
  "event": "call.disposition",
  "sentAt": "2026-09-28T15:04:05.000Z",
  "data": {
    "leadId": "…",
    "phone": "+12025550101",
    "disposition": "APPOINTMENT_SET",
    "status": "…",
    "notes": "Pricing review Thursday 4 PM",
    "callId": "…",
    "durationSeconds": 290,
    "agentName": "Jordan Vale"
  }
}

Lists in, dialing out.

The real lists screen with sample data: 150 fictional leads across three lists, and the CSV upload control.

Lists and import

Real product interface. Sample data, fictional people and numbers.

Integration questions.

Need a specific handoff? Email us before you buy.

Does DialBreeze integrate with my CRM?

Not through a native connector today. Two paths work now: the signed call.disposition webhook, which any CRM or automation tool that accepts webhooks can receive, and CSV import and export. Test the handoff you need in the sandbox trial before switching.

What happens if my endpoint is down?

Each delivery is attempted up to three times with a short backoff and a five-second timeout per attempt. The outcome of every delivery is written to the audit log, so a failed delivery can be found and replayed.

Which events are sent?

call.disposition, when an operator saves the outcome of a call. The payload carries the lead ID, phone, disposition, status, notes, call ID, duration and operator name.

Is there a Zapier or Make app?

No dedicated app. Both tools can receive a webhook, so you can point the signed webhook at them and verify the signature in a code step.

Test the handoff before you switch.

Point the webhook at your CRM in the sandbox trial and watch the events arrive.

Start a 14-day trial Security