Does this work with every Dialpad account?

Compatibility must be confirmed. Dialpad supports generic SIP devices, but plan, account, feature and calling restrictions may apply.

Do I need to replace Dialpad?

No. Where supported, VoxLink can work alongside Dialpad for selected AI call workflows.

Can VoxLink use my Dialpad SIP credentials?

Potentially, where the customer's Dialpad account permits the required generic SIP endpoint use. We validate the setup before deployment.

How is compatibility checked?

We review your plan, administrative permissions, generic SIP device availability and calling restrictions, then test registration, audio, DTMF, transfers, caller ID and failover before go-live.

Could I use AI only after hours?

Where a compatible path is confirmed, an after-hours route is usually the least disruptive place to start.

Can I keep my existing Dialpad numbers?

The intention is that Dialpad continues to own the numbers and only selected calls are routed to VoxLink where supported.

What happens if the AI path is unavailable?

Failover behaviour is agreed and tested during validation so calls fall back to a defined destination rather than failing silently.

DIALPAD + VOXLINK

Add VoxLink AI Voice Agents to Your Dialpad Environment

Q: Can the AI make outbound calls?

Only where the account, SIP endpoint permissions and Dialpad calling restrictions support the required outbound workflow.

Dialpad stays your business communications platform.

Generic SIP devices in Dialpad come with their own entitlements and calling restrictions, so what works on one account is not automatically available on another.

Where your plan and account permit the required SIP device provisioning, selected customer conversations could be handled by a VoxLink AI agent.

We validate the account, device entitlement and calling restrictions before anything is configured - and we do not promise features a generic SIP device may not support.

Answer calls, book appointments, qualify leads, handle enquiries and connect customers with your team - 24/7.

Check Dialpad Compatibility See Pricing

Connection

Dialpad + VoxLink

Compatibility check

Connection type: SIP
Routing: Selected call flows
Direction: Inbound + outbound
Validation: Tested before go-live

Keep your phone system. Keep your numbers. Add AI to the conversations you choose.

Compatibility

Could VoxLink Work With My Dialpad Environment?

Dialpad supports generic SIP device registration and can generate SIP credentials for supported scenarios. That is the mechanism this model depends on - but availability is governed by your plan, your administrative permissions and the calling restrictions applied to generic SIP devices on your account.

Those restrictions matter more than the connection itself. A generic SIP device is not a full Dialpad app, and we will not describe emergency calling, international calling or other behaviours as available when the device class or account may not support them. The assessment establishes what your environment actually permits.

Plan and admin access decide first

Generic SIP provisioning has to be available and permitted on your Dialpad plan, with an administrator able to enable it.

Device-class limits are real

Generic SIP devices carry calling restrictions of their own. Those limits apply to the AI endpoint too and are confirmed up front.

Validated, not assumed

Every setup is subject to technical validation and account policy. This is not a native or certified Dialpad integration.

What VoxLink adds

What You Can Automate With Dialpad

Answering selected calls

Could take a chosen call path once eligible SIP provisioning is confirmed on your account.

Overflow and after-hours

Could pick up conversations your team cannot reach, where routing to the endpoint is supported.

Lead qualification

Could qualify enquiries and capture details before handover on compatible paths.

Appointment booking

Could book or reschedule during the call subject to the validated call flow.

Transfer to your team

Could transfer back where the transfer method is supported by the endpoint and tested.

Outbound workflows

Only where account, SIP endpoint permissions and Dialpad calling restrictions support the required workflow.

In practice

Example Workflow

An illustration of the intended journey where a compatible Dialpad SIP path is confirmed.

01
A customer calls your existing Dialpad number.
02
Your Dialpad call flow handles the call as it does today.
03
If compatible, a selected path reaches VoxLink through an eligible SIP endpoint.
04
The AI answers, handles the enquiry and captures the outcome.
05
The call completes, or transfers back to your team where that is supported.

Example - after-hours enquiry (illustration only)

CallerHi - I placed an order earlier and need to change the delivery address.

VoxLink AII can take that now. Can I get the order number and the new address?

CallerSure, one moment.

VoxLink AIThanks. I've recorded the change request and the team will confirm it when they're back online.

Outcome: request captured out of hours. Shown as an illustration - subject to the compatibility assessment.

Positioning

Keep Dialpad. Add More AI Automation.

For eligible Dialpad environments, VoxLink can use compatible SIP connectivity to add AI call handling to selected workflows while Dialpad remains the customer's primary cloud phone service.

Nothing changes in your Dialpad billing. VoxLink is priced separately on its own usage, and the compatibility check comes before any commitment.

See VoxLink pricing and plans →

Dialpad as your primary cloud phone service.
Your existing Dialpad numbers and call routing.
Your users, apps and existing workflows.
Control over which calls, if any, are routed to AI.

Use cases

Conditional Use Cases

Possible only after your Dialpad account and device entitlements are confirmed.

If compatible, route selected after-hours calls to AI.
If compatible, cover overflow when your team is unavailable.
If compatible, qualify inbound enquiries and capture the details.
If compatible, book or reschedule appointments on the call.
If supported and tested, transfer callers back to your Dialpad users.
Outbound only where account and generic SIP device restrictions allow it.

Technical model

How the Connection Works

Dialpad supports generic SIP device registration and can generate SIP credentials for supported scenarios. VoxLink's SIP connection requires server/domain and authentication details. Confirm the account, device entitlement and calling restrictions before using those credentials for an AI endpoint.

Dialpad Call Flow

Eligible SIP Endpoint

VoxLink AI Agent

Customer / Team

Selected calls are routed to a VoxLink AI Agent over SIP. Your team keeps everything else.

Generic SIP devices carry their own limitations and calling restrictions, so every setup is subject to technical validation and account policy. We do not promise emergency calling, international calling or other features a generic SIP device may not support.

Requirements

Compatibility Requirements

Checked before any configuration. SIP credentials and gateway details are handled privately and never published.

Confirmation that generic SIP provisioning is available and permitted on your Dialpad plan.
Administrative access to your Dialpad account.
Confirmation of the calling restrictions that apply to generic SIP devices on your account.
Agreement on the specific call flow that would reach the AI endpoint.
Appropriate network and firewall conditions for SIP signalling and audio.
A VoxLink account and an administrator available for validation testing.