Fix "Allow Sites to Ask to Become Default Handlers for Protocols" for Click-to-Dial

Why This Is Happening

You're staring at a phone number on a webpage. You click it. Nothing happens. Or worse , Chrome throws up a wall of confusion, asking you something about "allow sites to ask to become default handlers for protocols," and you have no idea what that means or how to get past it. I've seen this exact scenario on dozens of machines, and I completely understand the frustration , especially when you're mid-workday and need to dial a client right now.

Here's what's actually going on under the hood. When you click a phone number on a website, say, a contact page or a CRM entry, your browser encounters a special link that starts with tel: or sometimes callto:. These are called protocol handlers. Think of them like routing instructions: the browser sees tel:+18005551234 and needs to know which application should take over and make that call. On your phone, this is automatic, the dialer app just opens. On a desktop browser, the browser needs explicit permission to hand off to an app like Nextiva.

The "allow sites to ask to become default handlers for protocols" setting is your browser's gating mechanism. When it's disabled, or when your IT department has locked it down, two things break simultaneously. First, Nextiva (or any web-based softphone) can never register itself as the app responsible for tel: links. Second, even if Nextiva was previously registered, Windows itself may not know that Nextiva should receive those calls instead of Skype, Teams, or your default phone app.

There are three separate layers where this breaks, and that's why this is so confusing:

• Browser layer, Chrome or Edge blocks the protocol handler registration entirely
• Windows layer, The OS doesn't know which app handles tel: links
• Nextiva layer, The Nextiva extension or web app hasn't been granted permission to register

Who runs into this? Primarily people using VoIP softphones in a browser context, Nextiva users are the most common case I handle, but RingCentral, Dialpad, Zoom Phone, and 8x8 users hit the exact same wall. It also affects anyone on a domain-joined machine where Group Policy has disabled protocol handler prompts (IT teams often do this for security reasons, not knowing it kills click-to-dial functionality entirely).

Microsoft's error messages here are genuinely unhelpful. Chrome will just silently do nothing when you click a tel: link, or it'll show a vague "protocol not supported" notice without telling you what to actually fix. Edge is slightly better, it'll sometimes say "No app is set up to open this link", but even that doesn't point you toward the browser's own settings as the root cause.

Browse all Microsoft fix guides →

The Quick Fix, Try This First

Before we go deep, try this one fix. It resolves about 60% of Nextiva click-to-dial failures by itself, and it takes under two minutes.

Open Chrome and go directly to the protocol handlers settings page. You can paste this into your address bar:

chrome://settings/handlers

You'll land on a page titled Protocol handlers. Look for the toggle at the very top that reads "Sites can ask to handle protocols". If it's off (gray), flip it on. That's the "allow sites to ask to become default handlers for protocols" setting, and it's the master switch everything else depends on.

Now scroll down on that same page. You may already see Nextiva listed under Allowed, something like app.nextiva.com set to handle tel links. If it's listed under Blocked, click the three-dot menu next to it and choose Allow.

If Nextiva isn't listed at all, here's what to do next: navigate to app.nextiva.com (or your specific Nextiva One URL). Log in. In your browser's address bar, look for a small icon that looks like a diamond or a small app icon, Chrome shows it when a site wants to register as a protocol handler. Click it and choose Allow. The prompt only appears when the site is actively trying to register, so you may need to go to your Nextiva settings or click a phone number within the app to trigger it.

For Microsoft Edge users, the equivalent path is:

edge://settings/content/protocolHandlers

Same deal, make sure the toggle is enabled and Nextiva is listed as allowed.

After enabling this, close and reopen your browser completely. Don't just close the tab, close Chrome or Edge entirely and relaunch it. Then test by clicking any phone number. If Nextiva opens automatically and starts dialing, you're done.

Advanced Troubleshooting

If you've gone through all five steps and still can't get Nextiva click-to-dial working, you're likely dealing with one of three advanced scenarios: a Group Policy lockdown, an enterprise browser management conflict, or a corrupted handler registration. Let me walk you through each.

Group Policy Is Blocking Protocol Handler Registration

This is by far the most common enterprise scenario. IT teams sometimes push a Chrome or Edge policy that disables the "allow sites to ask to become default handlers for protocols" setting entirely. When this is active, the toggle in Chrome's settings is grayed out and you can't change it, even as a local admin on your machine.

To verify this is happening, run this in PowerShell:

Get-ItemProperty "HKLM:\SOFTWARE\Policies\Google\Chrome" | Select-Object RegisteredProtocolHandlers, ExternalProtocolDialogShowAlwaysOpenCheckbox

Or for Edge:

Get-ItemProperty "HKLM:\SOFTWARE\Policies\Microsoft\Edge" | Select-Object RegisteredProtocolHandlers

If you see values here, your IT team has pushed managed browser policies. The fix requires your IT admin to either:

• Add Nextiva to the RegisteredProtocolHandlers Chrome/Edge policy (this whitelists it without requiring user interaction)
• Set ExternalProtocolDialogShowAlwaysOpenCheckbox to true so users can approve handlers themselves

The Chrome policy to push Nextiva click-to-dial organization-wide looks like this in Group Policy or Intune:

Policy: RegisteredProtocolHandlers
Value:
[
  {
    "default": true,
    "protocol": "tel",
    "url": "https://app.nextiva.com/call?number=%s"
  }
]

Event Viewer Analysis

When a protocol handler call silently fails, Windows logs it. Open Event Viewer (Win + R → eventvwr.msc), navigate to Windows Logs → Application, and filter by Event ID 1000 or 1001. Look for entries from Chrome, Edge, or any process that was active when you clicked the phone number. You may see an application crash or a "no handler found" error that points you to the exact failure point.

Resetting the Chrome Handler Database

In rare cases, Chrome's internal handler database gets corrupted and won't accept new registrations. To reset it:

1. Close Chrome completely
2. Navigate to your Chrome profile folder: %LOCALAPPDATA%\Google\Chrome\User Data\Default\
3. Find the file named Preferences (no extension)
4. Open it in Notepad and search for "protocol_handler"
5. Delete the entire protocol_handler block and save
6. Reopen Chrome, you'll start with a clean handler slate and can re-register Nextiva

Prevention & Best Practices

Once you've got Nextiva click-to-dial working, the last thing you want is for it to silently break again two weeks from now. Here's how to keep it stable.

The most common reason a working click-to-dial setup breaks is a browser update that resets permission states, or another application (Teams updates are a notorious offender) re-registering itself as the default tel: handler without asking. Microsoft Teams in particular has a habit of claiming the tel: protocol for itself whenever it updates, even if you didn't choose it.

Keep your Nextiva extension pinned and visible in your toolbar. When the extension icon turns gray or shows an error badge, that's your early warning that something broke the connection. A gray icon almost always means either the extension lost its authenticated session or the protocol handler registration was revoked.

For enterprise environments, the most reliable long-term solution is having IT push the Nextiva handler via Group Policy or Intune as a managed RegisteredProtocolHandlers policy rather than relying on per-user browser settings. Managed policies survive browser updates and user profile resets. They also mean new employees get click-to-dial out of the box without any manual configuration steps.

Finally, if your organization uses Microsoft Teams alongside Nextiva, you need to explicitly tell Teams not to grab the tel: protocol. In Teams Desktop app: go to Settings → General → uncheck "Register Teams as the chat app for Office (requires restarting Office applications)" and also look for any call handling defaults that reference phone links. Some versions of Teams have a specific "Open links in Teams" setting that should be turned off when you're using Nextiva for calls.

Frequently Asked Questions