Go back to dialerseat.comsales@dialerseat.com
Guide

A click-to-call button in your CRM

There are three ways to put a click-to-call button in a CRM with DialerSeat for Developers. Add a data-dialerseat-call attribute to any link and it dials in the page's dialer. Call dialer.dial() from your own code. Or let your server send a dial command to the user's open dialer. Each call goes through the same checks: campaign access, do-not-call and the lead's calling hours.

Checked 2026-11-15 against the sources linked at the end.

1. An attribute on any link

Any element with data-dialerseat-call dials its number in the page's dialer when clicked, including rows your CRM renders later. Add the name, your contact id and the campaign if you have them, and the call lands on the right record in your webhooks.

html
<a href="#" data-dialerseat-call="+15125550142" data-dialerseat-name="Dana Ruiz" data-dialerseat-id="c_5501">Call</a>

2. From your own code

dialer.dial(lead) or dialer.dial('+15125550142') dials one lead now, adding it to the queue if it is not there. Use it when the button is yours to draw.

js
const dialer = DialerSeat.mount('#dialer', { session, leads })
callButton.onclick = () => dialer.dial({ phone: '+15125550142', external_id: 'c_5501', first_name: 'Dana' })

3. From your server

When the decision is made on your server, such as a booked callback or a workflow step, POST /v1/seats/{id}/commands with action dial places the call on that user's open dialer. It answers 202 when sent, and 409 seat_offline when the user has no dialer open.

Which to use

  • The attribute: a Call link next to every phone number, with no JavaScript of your own.
  • dialer.dial(): your own button, or a call started by something on the page.
  • The server command: automations and workflows, when the user may be on another page.
  • A whole list: don't click through it. Let the dialer run the queue in progressive, power or predictive mode.

Related: components and headless, drive the dialer from your server, your own UI on the dialer and E.164 format checker.

Sources


More: the developer FAQ, the comparisons, Answering machine detection (AMD), explained for developers, Salesforce Open CTI retirement: what it means, Webhook signature verification failed? Find the cause, Do-not-call API: what the national registry offers, Moving from VICIdial's API to an embedded dialer, Your own UI on the dialer, with DialerSeat.connect, A live status board for managers, or the quickstart, free in sandbox mode.