Two updates for one call
Dialpad can report a call and its outcome at different moments. Left alone, that creates two activities in Bitrix24. We combine them into one clean record.
Integration · Dialpad to Bitrix24
Bitrix24 and Dialpad integration
We connect Dialpad to Bitrix24 so every call, outcome and follow-up lands on the right lead. It is a one-time setup by our team, not a monthly middleware subscription.
- From $100, one-time setup
- No monthly fees from us
- Tested on your own calls before go-live
Dialpad
Bitrix24
One call ends in Dialpad. In Bitrix24:
- Call logged on the leadLength, direction and the rep who took it
- Recording attachedLinked from the call activity
- Outcome moves the dealThe stage or field you choose
- One-time setup
- From $100
- Monthly fee from us
- $0
- Working days to a written scope
- 2
- Working days to build and test
- 5–10
What we connect between Dialpad and Bitrix24
A typical setup. We adjust each line to how your team uses Dialpad and Bitrix24.
When this happensThis is what you get
A call endsA call activity on the matching lead, owned by the right Bitrix24 user
The call recordingAttached to that call activity
The transcript and summaryA comment on the lead
A caller who is not in Bitrix24 yetA new lead, checked against existing records first
Field mapping, event by event
Each Dialpad event and exactly what it writes in Bitrix24. Pick an event to see its fields.
1. Trigger · Dialpad
When a call ends
Every call made or received in Dialpad
2. Action · Bitrix24
Log the call activity
In Bitrix24, on the lead — Where your team already works
Bitrix24 field
Mapped from
What happens
Activity date
Date started15 Sep, 4:00 pm
Shown in your time zone
Date started15 Sep, 4:00 pm
Shown in your time zone
Call length
Call length3 min 04 s
Stored the way Bitrix24 expects
Call length3 min 04 s
Stored the way Bitrix24 expects
Direction
Call directionInbound
Inbound or outbound
Call directionInbound
Inbound or outbound
Recording
Call recordingPlayable audio
Added once the file is ready
Call recordingPlayable audio
Added once the file is ready
Call notes
Ai summaryAsked for pricing
Saved as comment text
Ai summaryAsked for pricing
Saved as comment text
Lead
Matched by phone number+1 415 555 0142
A new lead is created only if none match
Sample values are made up. The exact fields are agreed with you in your scope.
A one-time setup, not a monthly middleware bill
We are not a middleware. We plan the connection, set it up, test it on your calls and hand it over.
Web Repay integration setup
Middleware subscription
What you pay
One-time setup, from $100 (one-off)
A monthly plan, often priced by tasks or operations
As call volume grows
The same price, no per-task charges
Costs rise with every call that syncs
Who builds and tests it
We do, on your own Dialpad calls
Your team builds and maintains every step
Where it runs
In your own Dialpad and Bitrix24 accounts, documented
Inside the middleware vendor’s platform
When something changes
Additional support as needed, when you request it
Your team fixes the broken steps
Where a small connector layer is the most reliable route, we say so in your written scope, set it up in your own account and choose the option with the lowest running cost.
Where Dialpad and Bitrix24 setups usually go wrong
Phone numbers written two ways
Dialpad and Bitrix24 often store numbers in different formats. Left alone, a caller who already exists becomes a second lead. We match on a cleaned-up number before anything is created.
Reps matched to Bitrix24 users
If a Dialpad user is not matched to a Bitrix24 user, calls log without an owner. We match every rep before go-live.
Updating the right deal
An outcome has to change one deal, not every deal on the record. We agree the rule with you before we build.
How we set it up
- 1
Tell us what should connect
Which calls, outcomes and follow-ups should reach Bitrix24. You get a written scope with a fixed one-time price.
- 2
Give us access
Admin access to Dialpad and Bitrix24 for the setup. Nothing for you to install, and no new subscription to start.
- 3
We build and test
We connect the two tools, map every detail and test it with real calls before your team relies on it.
- 4
Handover
You get a short document of what is connected and how it behaves. It runs in your own accounts, with no monthly fee from us.
Test call passedEvery field in the table checked
LiveWatched for the first week
What it costs
From
$100 one-time setup
Starting price for connecting Dialpad and Bitrix24, built and tested. Larger mappings get a fixed quote in writing before we start.
No monthly fee from us. Additional support is available as needed, whenever you request it.
Questions about Dialpad and Bitrix24
Is there a monthly fee?
No. You pay once for the setup. Unlike Zapier, Make and similar middleware subscriptions, there is no monthly or per-task charge from us, so the cost does not grow as your team makes more calls.
Is Web Repay a middleware?
No. We are an integration team: we plan the connection between Dialpad and Bitrix24, set it up, test it on your calls and hand it over. Where a small connector layer is the most reliable route, we say so in your written scope and choose the option with the lowest running cost.
What can you connect between Dialpad and Bitrix24?
A call ends, the call recording, the transcript and summary, a caller who is not in bitrix24 yet, each mapped to the right lead and deal in Bitrix24. We confirm the exact list in your scope.
How long does it take?
You get a written scope and a fixed price within 2 working days. Most setups are built and tested within 5 to 10 working days of getting access.
What do you need from us?
Admin access to Dialpad and Bitrix24 during the setup, and a short call to agree what should happen. You can remove our access once it is handed over.
Rather talk it through?
Thirty minutes on how your team uses Dialpad and Bitrix24. You leave knowing what we would build and what it would cost.
Call ended03:04 · inbound
Deal updatedStage set from the call outcome
Call-back taskAssigned to the contact owner