VanillaSoft

The routing engine ranks continuously and does so against rules the customer wrote.

That distinction is the whole answer. The proprietary engine evaluates every record in real time and pushes the next best one to an agent, which sounds like scoring and is described consistently as operating against criteria set by the customer and against defined business rules. Assignment runs on ownership, team membership, availability, call outcome codes and custom logic. All of that is deterministic.

One third party summary describes the company as positioning itself as an automation and intelligence enabled engagement layer, and two passes located no generative capability, no assistant, no model provider and no feature described as model driven anywhere on the vendor's own surfaces.

For this product that is the correct architecture rather than a shortfall. A dialer operating in regulated verticals under telephone consumer legislation needs behaviour that is explicable and reproducible, because a customer may have to demonstrate why a particular number was called at a particular time. An inferred ranking would make that harder, not easier.

Twenty years of operation predates the current generation of tooling entirely.

Ask whether the routing engine uses any learned scoring or purely defined rules.

The control is architectural: the representative does not choose which lead to work, and cannot skip one.

The vendor states the failure it addresses without softening it. List based systems let salespeople hunt through a list and cherry pick the records they judge valuable, with the result that a large percentage of leads are never contacted at all. A queue removes the decision entirely.

That is oversight built into the workflow rather than reported afterwards. A manager does not need to audit whether leads were worked in priority order, because no other order is possible. Unanswered leads return to the queue under cadence rules rather than falling out of the process. Records re rank automatically as data changes and prospects engage. Workflows define every step from first contact to final follow up, so consistency is enforced rather than encouraged.

Call outcome codes feed directly back into routing, which closes the loop between what an agent did and what happens next.

The sharpest evidence that the design works is a complaint about it. A published review objects that the platform allows working only one lead at a time. That is the mechanism operating exactly as intended and being disliked by someone who wanted the discretion it removes.

Ask what a manager can override in the queue and who holds that permission.

A positioning claim from a third party summary, and nothing behind it on the vendor's own surfaces.

One independent write up describes the company as positioning itself as an automation and intelligence enabled engagement layer. Two passes across the vendor's platform pages, its lead management and routing pages, its buyers' guide and its blog located no model provider, no model name, no version, no data flow statement, no accuracy figure and no evaluation.

The proprietary routing engine is named and its behaviour is described in rule terms throughout: it evaluates records against priorities the customer sets, applies defined business rules, and re ranks as data changes. Nothing indicates inference.

So the honest reading is an empty surface rather than a concealed one, and the grade reflects that.

Where a buyer should press is the boundary. If any part of the ranking is learned rather than configured, that becomes material in the regulated verticals this vendor serves, because an insurance or mortgage operation may need to explain why a particular consumer was contacted when they were.

Ask whether any ranking component is learned rather than configured.

Roughly six hundred reviews at four and a half, with the praise themes quantified by mention count.

That review base is among the largest in this index and the pattern within it is consistent rather than scattered. Ease of use dominates with sixty three mentions, intuitiveness and simplicity draw twenty three each, time saving automation twenty two and lead management twenty one. Five themes clustering that tightly across six hundred reviews describes a product that does one thing recognisably well.

Two case studies are named and published: an outsourced sales firm using it for appointment setting, and a named public university's fundraising operation reporting a donation increase. The second is checkable and the sector is unusual enough to be informative.

Vendor figures: a thirty five percent increase in call connections, three times more actions per hour, and teams connected with more than fifteen million new prospects monthly.

Twenty years of continuous operation is itself a form of evidence in a category where most vendors in this index are under three years old.

Deductions: no methodology accompanies the vendor figures, neither case study was opened, and no customer logo set was retrieved.

Ask how the thirty five percent connection increase was measured.

Litigator scrubbing before dialling, which almost nothing else in this index offers.

The integration screens records against a named third party service that tracks serial plaintiffs in telephone consumer litigation. Calling one of those people is how a high volume operation acquires a lawsuit, and screening them out before the dialer reaches them is a specific operational control rather than a policy statement. Across two hundred and forty records this is the only instance found.

Around it: the dialer is described as compliant with United States telephone consumer legislation, which for a platform offering parallel dialing is the load bearing claim, and caller identity features work to keep numbers from being displayed as spam.

Four dialing modes let a customer choose their own posture deliberately. Single line and preview are conservative, progressive sits between, and parallel is the aggressive option. An independent reviewer states the trade plainly, observing that parallel is where answer rates and compliance collide.

The vertical concentration explains the investment. Insurance, mortgage, merchant services and fundraising are all sectors with specific calling rules and active litigation, and customers there buy the compliance apparatus as much as the dialer.

Deductions: no do not call register screening named explicitly, and no calling hours restriction described.

Ask whether do not call screening runs alongside litigator scrubbing.

Two data categories here are more sensitive than the product's positioning suggests.

The first is consumer lead data across insurance, mortgage, automotive, home repair and merchant services. Those are individuals whose financial and personal circumstances are the reason they became a lead, and the records arrive from third party lead providers and purchased lists as well as the customer's own web forms.

The second is donor data. The fundraising business serves universities and nonprofits, with payment gateway integrations meaning donations are taken during the call, so the platform touches contribution records and payment flows for named institutions.

Call recording sits across both.

What two passes could not locate on the surfaces examined: any processing agreement, subprocessor list, retention schedule, deletion commitment, residency statement or rights request route.

The corporate footprint adds a dimension. Operations span the United States and Quebec, and the Canadian presence is relevant given that country's own anti spam legislation and its application to fundraising communications.

Ask how long call recordings are retained and where donor data resides.

The vendor supplies no contact data and says so, which correctly leaves provenance with the customer.

Independent analysis confirms that no contact data is included and that a customer needs a separate source. The platform's role is to route, prioritise and work records the customer brings, not to supply them.

The intake routes are named openly and one of them deserves credit for candour. Leads enter through web forms in three published formats, through third party lead providers, through record system synchronisation, through interfaces, and through purchased lists. Naming purchased lists explicitly as an intake path is honest, and it places the consent question exactly where it belongs, with whoever bought the list.

That matters in the verticals served. Insurance and mortgage lead flow runs through specialist providers, and two of those providers appear among the named integrations, so the customer's supplier relationships are visible rather than behind the platform.

A consumer data enrichment platform appears among the referenced integrations.

The deduction: nothing describes what the vendor does to validate or screen incoming lead quality beyond the litigator screening.

Ask what screening applies to leads arriving from third party providers.

Every channel and every integration runs through infrastructure the vendor operates or has a commercial agreement for.

Voice runs on the vendor's own internet telephony. Record system synchronisation is bidirectional with a named enterprise platform. The remaining integrations are named vertical partners with commercial arrangements: a messaging provider, two insurance lead flow platforms, a lead distribution service, a litigator screening service and payment gateways.

Two passes across the platform pages, the lead management pages and independent analyses located no scraping, no social network automation, no browser extension operating a third party property, no account renting, no undetectability marketing and no capability whose viability depends on another platform failing to notice it.

That position follows from what the product is and how long it has existed. A queue and dialer operating in regulated verticals since 2005 has no route to market that involves working around anybody's terms, and its customers are precisely the buyers who could not accept that risk.

Caller identity management works with the carrier ecosystem rather than against it.

Ask which telephony carriers underlie the dialer.

Almost no model surface, and a compliance apparatus doing the work stewardship usually describes.

There is little to assess on safety. Nothing generates content, holds conversations or acts autonomously; the routing engine ranks records against customer defined rules and a human agent has every conversation.

Stewardship shows up instead as operational controls with legal consequence: a dialer described as compliant with telephone consumer legislation, screening against a register of serial litigants before dialling, caller identity management, and call recording for review. Those are the controls this vendor's customers are audited on.

What two passes could not locate on the surfaces examined: any dedicated security page, any certification, any audit report, any encryption statement, any access control description, any incident response process, any breach notification commitment, any named security contact, any vulnerability disclosure route and any status page.

Payment gateway integrations imply payment card handling standards somewhere in the chain and nothing states where.

A twenty year old vendor serving named universities and insurance operations will have assurance material; it was not reachable here.

Ask for the security documentation and any payment card compliance attestation.

A real agent has every conversation, and one control protects the recipient more directly than anything else in this index.

That control is litigator screening. The people it filters out are those who have previously sued over unwanted telephone contact, which is the clearest available proxy for people who very much do not want to be called. Screening them before dialling protects the customer from litigation and, incidentally, protects those individuals from the call. Both outcomes are real.

Caller identity management works in the same direction: the number displayed is managed for trust rather than masked or rotated to disguise the caller.

Two passes located no synthetic voice, no persona, no automated messaging presented as human and no generated content of any kind. Agents speak, using scripts they can see.

Three deductions. Parallel dialing places simultaneous calls and drops those where no agent is free, which is the abandoned call problem and is inherent to the mode rather than to this vendor. Call recording carries no described notification. And text messaging is a supported channel with no opt out mechanism described.

Ask what a called party hears when a recorded call connects.

Deliberately vertical rather than broad, and an independent reviewer names the trade precisely.

That reviewer observes that integration breadth is narrower than a general purpose engagement suite, with one enterprise record system receiving bidirectional synchronisation and the rest of the ecosystem leaning vertical. The named partners bear that out: a messaging provider, two insurance lead flow platforms, a lead distribution service, a litigator screening service and payment gateways.

Read as a strategy rather than a gap, it is coherent. An insurance operation needs lead flow from its own sources, screening before dialling and a way to take payment, and this vendor has built exactly those. A fundraising operation needs payment gateways more than it needs a marketing automation connector.

Read as a constraint, it is real. A buyer outside those verticals finds one record system connector and a set of partners irrelevant to them.

Intake is well served: web capture in three published formats, third party providers, record systems and interfaces, with no manual uploading.

The same reviewer names as a poor fit any organisation needing this to sit invisibly behind a record system.

Ask which integrations exist outside the named verticals.

A stated two country corporate footprint and nothing about where data sits.

The company operates from Texas with additional operations in Quebec, which is more corporate transparency than most records in this index provide and establishes an accountable presence in two jurisdictions.

The vendor operates its own internet telephony infrastructure for the dialer, which is a real architectural fact and the reason the compliance claims are the vendor's to make rather than a carrier's.

What two passes could not locate on the surfaces examined: any hosting provider, any region, any data centre, any residency commitment, any tenancy or isolation model, any encryption statement, any backup position, any continuity plan, any uptime commitment and any status page.

The Canadian operation makes residency worth asking about specifically. Canadian anti spam legislation applies to commercial electronic messages including fundraising communications in some circumstances, and a customer operating across the border would want to know where records and recordings are held.

Call recordings and donor payment flows are the holdings that matter.

Ask where data and call recordings are stored for United States and Canadian customers.

The compliance claims imply documented controls and none of the documentation was reachable.

What the vendor asserts requires evidence behind it. A dialer described as compliant with telephone consumer legislation, an integration screening against a litigation register, and payment gateway connections handling donations all rest on controls that would ordinarily be documented and, in the payment case, independently assessed.

What two passes could not locate on the surfaces examined: any certification, any audit report, any examination, any penetration test, any trust portal, any dedicated security page, any encryption or access control statement, any subprocessor list, any vulnerability disclosure route, any named security contact and any status page.

An absence is improbable rather than proven. A company operating since 2005 whose named customers include a public university's advancement office and whose verticals include insurance and mortgage will have completed supplier assurance many times over. The material exists somewhere and is not published where a prospective buyer can reach it.

That itself is the finding for a vendor of this age, since publishing a trust page is now the norm among competitors half its size.

Ask for the security documentation package and payment card attestation.

Twenty one years in operation and not one figure published anywhere.

An independent reviewer describes the experience directly: you go to the pricing page and find nothing, just a get pricing button and some marketing metrics, and calls hiding every dollar figure genuinely frustrating for a tool that has been around this long. That is the position.

Third party estimates put it between eighty and a hundred and seventy five dollars per user monthly depending on add ons, with one analysis narrowing the upper range to between a hundred and thirty and a hundred and seventy five.

Three structural terms matter more than the rate and none is discoverable without a sales conversation. Billing runs as an annual bundle rather than monthly. There is a five seat minimum, so a team of four pays for five. And contact data is not included at all, which for a dialing platform is a substantial separate cost the headline would never reveal.

A thirty day free trial is reported, which is generous and also unadvertised.

The five seat minimum is the term most likely to surprise, and an independent reviewer lists teams of one to four among those the product suits poorly precisely because of it.

Ask for the per seat rate, the minimum term and what the add ons cost.

Bidirectional synchronisation is the route out and it covers one system.

That synchronisation with a named enterprise record system runs in both directions, so for customers using it, lead and activity data accumulates in a platform they own as the work happens rather than only at exit. Interfaces exist for lead intake and presumably support extraction.

What two passes could not locate on the surfaces examined: any export mechanism described in product terms, any format, any deletion commitment, any retention position after cancellation and any account closure process.

Two asset categories have no described route out and both matter. Call recordings accumulate across every conversation and are the material a customer may be obliged to retain or produce. And the routing configuration itself, the rules, priorities, cadences and assignment logic built over years, is the intellectual work of running the operation and is undescribed on exit.

The commercial position bounds when leaving is possible. Annual bundle billing with a five seat minimum means no mid term exit.

Ask whether call recordings and routing configuration can be exported.

On this channel the equivalent of deliverability is whether the phone is answered, and two mechanisms address it.

The first is caller identity management, which works to prevent a customer's numbers being displayed as spam on a recipient's handset. That is the same problem another dialer in this index solves by placing live test calls to carrier networks; this vendor approaches it through identity and trust features instead. Either way it is the failure that destroys a calling operation fastest.

The second is timing. Priority shifts by time of day in the prospect's own location, and web submitted leads are called immediately. Calling someone when they are likely to be available is both a connect rate optimisation and a courtesy, and speed to lead on a web form is the single largest determinant of whether a submitted enquiry converts.

Four dialing modes let a customer balance agent pace against customer experience, which the vendor frames in exactly those terms.

The claimed result is a thirty five percent increase in call connections.

Deductions: no per number daily ceiling published, no carrier level display testing described, and on the email channel no warm up, authentication guidance, rotation or placement testing.

Ask what caller identity management actually does and how it is monitored.

Seven industries named, all sharing one characteristic, and an independent reviewer supplies the exclusions precisely.

The named industries are insurance, outsourced sales, fundraising, automotive, mortgage, home repair and merchant services. What unites them is stated by the vendor: high value leads meeting high agent activity, where a lead going uncontacted is an expensive loss. That is a coherent definition rather than a list, and it explains every design decision in the product.

Fundraising is a genuine second business rather than an adjacent claim, with dedicated bundles and workflows, higher education advancement named specifically, and a public university case study published.

The floor is stated openly: teams of five or more agents.

The exclusions come from outside and are unusually useful. An independent reviewer names as poor fits teams of one to four who pay for five seats regardless, email first teams whose bottleneck is inbox capacity rather than dial volume, organisations needing the platform to sit invisibly behind a record system, field representatives needing a real mobile experience, and buyers unwilling to sign an annual contract behind a demonstration gate.

A reader can place themselves on one side or the other in a sentence.

Ask how the fundraising bundles differ from the commercial product.