VICIfast
All lead platforms

Phonexa + VICIdial

Phonexa + VICIdial: leads and calls

Phonexa spans web leads and calls, so it is two integrations on one account. How each reaches VICIdial, and why the field mapping is the work.

Platforms in this category

  • Phonexa

When teams ask us for this

You buy both leads and calls from one account

Two separate mechanisms into one dialer. The lead path posts to an endpoint; the call path routes to an in-group.

You need per-buyer field mapping honoured

Phonexa's Integration Builder maps fields per buyer, so the spec is yours and the dialer end is built to match it.

You want calls to carry context

Route calls over SIP rather than a DID and the values travel as headers for the dialplan to read.

You need one reconciliation key

Phonexa's own lead identifier is written to vendor_lead_code so dispositions tie back to invoices.

Phonexa is a suite rather than a single product. LMS Sync distributes web leads, Call Logic routes calls. If you buy both, you are wiring two mechanisms into one dialer, and they have almost nothing in common beyond the account they bill from.

Integrations on demand. We are not a Phonexa partner and there is no connector to enable. Our team wires your account to your server as scoped work, quoted per setup.

The lead path

Phonexa's Integration Builder does direct-post and ping-post to a buyer URL with per-buyer field mapping. The delivery lands on an endpoint you nominate, which calls VICIdial's non-agent API:

non_agent_api.php?function=add_lead
  &phone_number=&phone_code=1&list_id=
  &vendor_lead_code=<phonexa lead id>
  &dnc_check=Y&campaign_dnc_check=Y

As with any ping-post source, only the post reaches the dialer. The ping is a bid and carries nothing dialable.

The call path

Calls route to a destination on your box - a SIP address or a DID terminating on your carrier - and land in a VICIdial in-group. If Phonexa is carrying data you want on the agent screen, take the SIP route so the values can travel as headers and be read with PJSIP_HEADER(read,...).

Why this one takes longer than it looks

Because the mapping is per-buyer and configured in their Integration Builder, the integration is not "connect Phonexa". It is "agree the field list, build the delivery, confirm the response format, then map it at the dialer end". Two accounts buying the same vertical from the same platform can have completely different specs.

That is also why it is quoted per setup rather than priced from a list.

Setup

  1. Decide which side you are wiring - leads, calls, or both. They are separate pieces of work.
  2. For leads: agree the field list and the acknowledgement format your endpoint must return.
  3. For calls: provision the in-group and the SIP endpoint or DID.
  4. Build the delivery in Phonexa's Integration Builder against that spec.
  5. Map fields to VICIdial, including vendor_lead_code for reconciliation.
  6. Test with live traffic on both paths before switching volume on.

It also runs the other way

Everything above is traffic arriving. The dialer can call Phonexa as well: VICIdial fires their API mid-call with the lead substituted into the URL, and the caller is transferred live if Phonexa accepts. Phonexa sits on both sides of the trade, so the same account can be a source of calls and a destination for transfers.

A transfer accepted during the conversation is worth considerably more than a record posted after it, and it is a separate piece of work from the inbound path. See live transfer on a buyer API response for the hooks and the failure modes.

Gotchas

Two products, two failure modes. A working lead delivery tells you nothing about whether calls route. Test them independently.

Reconciliation needs their ID. Without Phonexa's own lead identifier written to vendor_lead_code, matching a disposition to an invoice line is manual.

Duplicate protection is yours. Deduplicate at your endpoint. Do not assume the platform will not re-send.

Related: ping-post and lead distribution and pay-per-call routing.

Questions we get asked

Are you a Phonexa partner?
No. There is no certified connector. We wire your account to your server as scoped work, quoted per setup.
Is this one integration or two?
Two. The lead path and the call path share only the account they bill from. A working lead delivery tells you nothing about whether calls route.
Why is this quoted per setup rather than priced from a list?
Because the mapping is per-buyer. Two accounts buying the same vertical from Phonexa can have completely different field specs.
Does the ping reach my dialer?
No. Only the post is routed to add_lead. The ping is a bid request and carries nothing dialable.
How long does it take?
Agreeing the field list sets the timeline. Once the spec is settled, building and testing each path is usually a few days.

Phonexa is a trademark of its respective owner. VICIfast is not affiliated with, endorsed by or a partner of Phonexa. The name is used here only to describe how their platform can be connected to VICIdial, which we do as scoped work on request. See all ping-post and lead distribution platforms.

Try VICIfast free for 7 days.

One click to provision. Cancel any time before day 7 - we don’t charge until then.

See pricing