Dialpad is a phone and messaging provider your brokerage may already use, and connecting it lets BrokerPlus receive its calls and texts. It lives on the Integrations settings page, in the card titled Dialpad, and only a brokerage admin can connect or repair it.
What the Dialpad Connection Does
Dialpad is a separate provider from BrokerPlus's own native phone system. Numbers claimed through BrokerPlus are set up in claim a phone number and used directly from BrokerPlus in make calls and send texts; nothing about connecting Dialpad changes either of those. Connecting Dialpad does not move a number here or replace a native line: it pipes the calls and texts your team already makes in Dialpad into BrokerPlus, so they show up alongside the rest of a client's activity. A brokerage running both sees a client's history carry activity from either.
The connection is company-wide: one API key connects your whole Dialpad company, not one broker's extension, and only one connection can exist for the brokerage at a time.
Connect With an API Key
Create an API key in Dialpad using a company-admin account with API access. Your Dialpad plan needs call transcription for calls to arrive with useful content, and the key needs an added permission for text messages to arrive with their body rather than as an empty event.
- Open Integrations in settings and find the Dialpad card.
- Paste the API key.
- Choose Connect.
BrokerPlus verifies the key, then registers a webhook and separate subscriptions for calls and texts.
Reading the Connection's Health
The status chip reads Connected when both subscriptions registered cleanly. Setting Up means registration is still running. Needs Attention covers a connection missing a call or text subscription, or carrying a problem Dialpad reported, such as a rejected scope; the card lists the exact reason underneath. If the card is connected but a full day passes with zero calls or texts, a hint appears, since that combination usually means nothing has come through yet rather than that the connection is broken.
Repair a Connection That Needs Attention
Retry Setup on a degraded connection re-registers the webhook and subscriptions using the key already on file, without asking you to paste it again. Two problems it cannot fix on its own: a conflict means an existing Dialpad subscription already overlaps this one, and needs a Dialpad admin or Dialpad support to clear it before you retry; a rejected key means it has lost access to manage webhooks or subscriptions and needs its permissions restored in Dialpad first.
Disconnect and Clean Up
Disconnecting removes only the webhook and subscriptions this connection owns, matched against the endpoint Dialpad shows for them, so another integration's hooks are never touched. If Dialpad's side does not confirm the removal, the card shows Cleanup Pending instead of clearing outright, and a fresh key cannot be connected until that cleanup succeeds through Retry Cleanup.
What to Do Next
- Claim a phone number for BrokerPlus's own native phone system.
- Make calls and send texts from BrokerPlus directly.
- Manage every connection from Connect and Manage Integrations, the settings page this card lives on.