Conquer
Conquer, which traded for years as DialSource and still runs its video channel under that name, sells sales engagement that lives inside the system of record rather than beside it. The distinction is the entire pitch: where competing platforms integrate with Salesforce, Conquer is a native application running within it, and within Microsoft Dynamics 365 as well, so activity stays attached to the pipeline it is meant to move and reps work without switching tools. The suite has five software components. Voice is a carrier grade power dialer with click to call, automatic logging and campaigns drawn from live records.
Voice Plus is a mobile first application launched for field representatives who need to call, log a meeting and capture notes from a phone in under a minute with everything syncing back. Cadence runs automated sequences across email, phone and professional network channels. Text handles messaging, multimedia messaging and business messaging natively. AI Insights supplies conversation intelligence in two directions, surfacing battle cards to the representative live during a call to handle objections and flag upsell moments, then producing transcripts and summaries afterwards so managers coach from real examples rather than from rep notes.
Two further products sit in the wider revenue suite: an outsourced sales development service, and a marketing attribution product connecting campaigns to revenue. Named customers include Paychex, Paycor, ADP, Optum, VSP and Hibu. The company is an official Salesforce partner with a reviewed marketplace listing, and operates from Fremont, California.
Capability Axes
Capability grades
17 of 17 axes rated · 8 graded A or B
The established platform pattern, and the vendor's own history settles it. Remove every model and what remains is a complete and mature product: a carrier grade power dialer running natively inside two major systems of record, click to call, automatic activity logging, campaign lists drawn from live records, multi step cadences across email, phone and social channels, native messaging including multimedia and business messaging, and a mobile application for field representatives.
That is a decade of engineering and it is what the company sold under its previous name before any of the intelligence layer existed. The models add conversation intelligence on top: live battle cards during a call, transcription, sentiment analysis, summaries and next best action prompts. Those are genuinely useful and they are an addition to a telephony and engagement platform rather than the reason it exists. The company's own video channel still carries the former brand name, which is a small but exact marker of the vintage this axis is measuring.
Earned architecturally on the ground that a product which cannot act on its own initiative is more constrained than one that promises not to. Nothing here contacts a prospect autonomously. The representative dials, the representative talks, and the intelligence layer sits behind them: battle cards surface during a live call to help handle an objection or flag an upsell, and the human decides in the moment whether to use them.
That is the strongest form of a human in the loop available, because the human is on the call while the model is advising. Post call transcripts and summaries are records for a manager rather than actions taken on anyone. Off the top of the band on three counts. Cadences do dispatch automated email and text on a schedule without a per message gate. Nothing describes what the live coaching is grounded in or what happens when a card is wrong mid conversation. And no audit trail of model suggestions is published, so a manager reviewing a call cannot see what the representative was being told at the time.
The intelligence layer is described entirely by what it does and never by what it is. Battle cards, transcription, sentiment analysis, call summaries and next best action prompts are all named as capabilities, and no model provider, family or version appears anywhere, no inference location is stated, and no retention position is published for transcripts, recordings or generated summaries.
The gap carries more weight here than for a lighter product because of what is being processed: live sales conversations at high volume for payroll, benefits and health services companies, which is material likely to contain sensitive employer and employee detail as a matter of routine. Nothing states whether a call is transcribed in the vendor's own environment or passed to a third party. Recorded as observed rather than concluded: a privacy policy is published and was not read this pass, and it is the most likely home for a processing description. Re verify there.
The customer evidence is the strongest asset here and it is specific rather than decorative. Six named enterprise logos appear on the homepage, including three of the largest payroll and human capital processors in the United States alongside a major health services organisation and a vision benefits company, which is a checkable and senior set that a vendor cannot display without those relationships being real. A testimonial carries a full name, a job title and a named institution.
Independent review standing is substantial at 4.3 from more than a hundred and twenty reviews, and the marketplace listing on the platform the product runs inside carries its own reviews, which is third party verification of a kind most vendors here cannot offer. A case study library, reports, webinars and a podcast sit behind it.
Off the top of the band for three reasons: the two headline percentages published on the marketplace listing, covering pipeline and deal size uplift, carry no method, sample or period; no analyst evaluation was located; and the homepage link to further client stories resolves to a dead anchor.
The regulated surface here is as heavy as any vendor graded and the published position is absent from every page read. This is a high volume power dialer with call recording, plus messaging across text, multimedia and business messaging channels, plus automated email cadences, sold to enterprises in payroll, benefits and health services.
That combination engages telemarketing rules, abandoned call rate limits for automated dialing, do not call screening, carrier registration for business texting, caller authentication, call recording consent across two party consent states, and messaging opt out handling. None of it is named.
Recorded as observed rather than concluded, and this reading is more likely than most to be a false negative: a vendor selling recorded telephony to buyers of that size does not clear their procurement without documented positions, so the material probably exists and is supplied during a sales process rather than published. A privacy policy exists and was not read this pass. Re verify there.
A privacy policy is published and its own summary states that information may be stored and processed in the United States and in Europe, which is a scope statement of some substance. It was not read this pass. What is striking about the surrounding presentation is that the site footer carries no legal section at all: the four footer columns cover product, solutions, resources and company, and no privacy, terms or security link appears among them, so the policy exists without being reachable from the pages a buyer actually reads.
Beyond it, no processing addendum, data protection contact, sub processor list or jurisdiction specific page was located. The stakes are set by what the platform holds, namely recordings, transcripts and sentiment analysis of conversations between an enterprise and its own customers and prospects. Recorded as observed rather than concluded. Re verify by reading the published policy directly.
The lightest posture available on this axis, and it is architectural rather than promised. The vendor sells no data. It ships no contact database, offers no enrichment, claims no third party sourcing, and operates on records the customer already holds inside the customer's own system of record, with campaign lists drawn from live data the customer put there.
The provenance question that occupies most of this index simply does not arise, because nothing enters the pipeline that the buyer did not already own. Off the top of the band on two counts. Nothing is stated in writing about ownership of the records the platform processes, or about what the vendor may do with the conversation data it generates on top of them.
And the wider suite includes an outsourced sales development service, which by its nature places people outside the customer's own organisation in front of the customer's records, and no access, segregation or confidentiality position is published for that arrangement anywhere.
A stronger conformance position than most vendors here can claim, and it comes from the deployment model. The product is not integrated with the platform it depends on, it is a native application running inside it, listed and reviewed on that platform's own marketplace as an official partner, which means the platform owner has examined and admitted the application rather than merely tolerating it. The same native relationship exists with a second major system of record.
Telephony runs on infrastructure the vendor operates. Off the top of the band on two specific gaps. The cadence product lists a professional network among its channels and nothing states whether that step automates an action against the network or queues a manual task for the representative, and those are different bands on this axis. And business messaging appears as a native channel with the platform owner's own policy obligations nowhere addressed.
The training and tenancy questions go unaddressed on every surface read, and the material at issue is unusually sensitive. This platform records, transcribes and performs sentiment analysis on live sales and service conversations, at volume, for enterprises in payroll, employee benefits, health services and vision care.
Those calls will routinely contain employer detail, employee detail and in some cases health adjacent information, and the resulting corpus of transcripts and summaries is the asset the coaching layer is built on. Nothing published states whether that content is used to train or improve models, whether any learning is scoped to a single customer, how long recordings and transcripts are retained, or which sub processors see them. Recorded as observed rather than concluded: a privacy policy exists and was not read this pass. Re verify there, and treat this row as provisional until it has been.
A clean position that comes from product shape rather than policy, in the same way it has for the other vendors graded here on this ground. Nothing in this product contacts a person autonomously. There is no agent, no synthetic voice, no invented persona, no generated correspondent and no area code matched to the prospect. Every conversation is a real named representative speaking to a real person, and the intelligence layer sits entirely behind that representative, visible only to them.
A recipient is not being deceived about who or what they are dealing with, which is a low bar most of this index fails. Off the top of the band because two questions are left open on a product built for recorded calling at volume. Call recording notification is nowhere addressed, and the applicable rule differs by state.
And the live coaching layer means the person on the other end is speaking to someone being prompted in real time by a system they cannot see, which is recorded here as an observation rather than a deception, since a human sales coach has always been able to do the same thing.
Depth rather than breadth, and the depth is unusual. The product does not connect to a system of record, it runs inside one, natively, for two of the major platforms, which is a materially different kind of integration from a connector count: activity is written to native objects, campaigns read live records, and there is no synchronisation layer to drift. Official partner status with a reviewed marketplace listing means the platform owner has examined the application.
A support knowledge base is published on its own subdomain, and the wider suite adds a marketing attribution product connecting campaigns back to revenue. Off the top of the band because the ecosystem is exactly two platforms wide and stops there. No published programmatic interface, developer portal, webhook documentation, connector catalogue or agent facing endpoint was located on any page read, which for an enterprise platform in 2026 is the notable absence.
One statement exists and it is a scope rather than a choice. The published privacy policy's own summary states that information may be stored and processed in the United States of America and in Europe, which tells a buyer the footprint spans two regions and nothing more.
No customer selectable residency is offered, no data centre is named, no sub processor list is published, and no location is stated for the telephony infrastructure, which for a carrier grade dialing product is a separate question from where the application runs. The policy was not read this pass, so the two region statement is taken from its own description rather than from the document. Recorded as observed rather than concluded. Re verify by reading the policy, which is the only located home for anything further on this axis.
No certification, trust centre, security page, audit report, penetration test, vulnerability disclosure policy or enumerated control set was located on any page read, and the site footer carries no security or legal section at all. Recorded as observed rather than concluded, and this reading is very likely a false negative, which the note should say plainly.
The named customer set includes three of the largest payroll and human capital processors in the United States alongside a major health services organisation, and those procurement functions do not approve a vendor that records and transcribes their sales calls without documented attestations. The material therefore almost certainly exists and is supplied under a sales process rather than published. That is itself the finding for this axis: the distance between what this vendor demonstrably satisfies for its buyers and what it makes available to anyone evaluating it from outside.
The site publishes no pricing page of any kind. The navigation offers reasons to choose the product, a product menu, solutions by team, resources and company information, and every call to action on every page leads to the same demo request form. There is no figure, no tier, no unit, no range, no floor and no worked example anywhere on the vendor's own surfaces.
A third party listing records two plans both marked contact us, with a note that telephony usage is billed separately, and that note is the single most useful piece of commercial information available about this product because usage billing on a high volume dialer is a real and variable cost driver, and it comes from a directory rather than from the vendor. The same listing records its pricing information as last updated in October 2024. A buyer evaluating this product cannot form any estimate of what it costs without entering a sales process, and cannot compare it to the alternatives it names in its own comparison pages.
Architecturally one of the strongest positions in the index, and entirely uncommitted in writing. Because the application runs natively inside the customer's own system of record rather than beside it, the operating record it produces is written into objects the customer already owns in a platform they already control: call logs, activity, notes, cadence history and pipeline movement all sit in the customer's own instance.
A customer who removes this product keeps that record without needing an export, a migration or a vendor's cooperation, which is a materially better position than any integration based competitor can offer. What is not covered is the part that matters most and does not live there.
Call recordings, transcripts, sentiment analysis and generated summaries are produced by the vendor's own systems, and nothing published states a retention period, a deletion timeline, an export route or a post termination position for any of them. No terms of service were located on the site.
The cadence product sends email as one of its channels and no sending control is published anywhere. There is no warmup, no guidance on sender authentication, no bounce or complaint threshold, no blocklist monitoring, no inbox placement testing, no suppression mechanics and no volume governor described, and the sending architecture itself is unstated, so a buyer cannot tell whether messages leave from their own connected mailbox carrying their own reputation or from vendor infrastructure.
The one delivery claim the vendor does make belongs to the other channel: telephony is described as carrier grade with an emphasis on call quality and dropped call avoidance, which is delivery in a real sense and not the sense this axis measures. Recorded as observed rather than concluded, and there is no public evidence of a delivery problem in either direction.
Segmented by role with real specificity and silent about its most visible characteristic. Four solution pages address distinct buyers by name, covering sales leadership, inside sales, field sales and customer success, and the product line maps onto them rather than merely pointing at them, with a mobile first application built specifically for the field case. The positioning is stated as enterprise sales and service teams.
What the vendor does not say, and what its own logo strip says loudly, is that the customer base clusters hard into two verticals: payroll and human capital services, and health and vision benefits. A named testimonial adds a third and quite different pocket in collegiate athletics revenue generation. That concentration is almost certainly a strength and it is never named, explained or turned into a vertical page.
Off the top of the band for that, for the absence of any published headcount, revenue or geographic band, and because independent review data places the reviewer base at mid market rather than at the enterprise the positioning claims.
Pricing
What this vendor charges, what it commits to in writing, and where the bill can move. Figures the vendor publishes itself are labeled Vendor Published. Figures labeled Estimated come from other sources and the vendor has not confirmed them.
- ›There is no price published and no pricing page. The address returns an error and the only routes are a demo request and a contact form.
- ›Nothing says how you would be charged either, which matters more here than usual. This is a dialler, and every other dialler in this index publishes at least part of its calling costs. This one publishes neither the seat price nor the per minute or per number costs.
- ›The most important thing to understand is that this product lives inside another company's record system rather than working alongside it. So you must already pay for that platform, and this sits on top of it rather than replacing anything.
- ›That means when you compare it against a standalone dialler you are comparing an addition against a substitute, and the comparison only works if you count the platform underneath.
- ›Ask for the quote split three ways: the license, the calling and messaging usage, and the setup work inside your record system.
How the price works
What you are charged for, and what makes the bill go up.
Not published, and no pricing surface exists. The dedicated pricing address returns not found, the homepage carries no pricing route, and the only commercial paths published are a demonstration request and a contact page.
No tier name, band, starting point, seat minimum, contract length, trial term or free tier appears anywhere.
The metering basis is unpublished. Nothing indicates whether charging is per seat, per dialler license, per connected minute, per message, per recorded conversation, or as a platform license banded by the customer's record system footprint.
No element of the telephony usage layer is published: no per minute rate, no number rental rate, no messaging rate and no registration fee, which distinguishes this vendor from every other telephony product recorded in this index.
One structural fact is published and bears directly on total cost: the platform operates natively inside a specific named record system rather than integrating with it, so the buyer must separately hold licenses for that platform. Published capabilities include a carrier grade dialler, automated sequences across email, telephone and a professional network, native messaging across short message service, multimedia messaging and a consumer messaging platform, real time coaching and conversation intelligence, and a recently launched mobile application for field representatives.
Outsourced sales and marketing teams are named among intended users, indicating some arrangements may involve services alongside licenses, with neither priced.
No credible third party estimate was located, so none is recorded.
What the contract says about your data
What the vendor commits to in writing once your data is in the product.
Not established. The dedicated pricing address returns not found and the homepage served no legal or security links in the retrieved markup. No processing agreement, sub processor listing, certification claim, retention period or residency statement was located.
The custody question is shaped by the platform's architecture, which is unusual in this index and reduces one category of exposure while concentrating another.
The product is described as living inside a named record system rather than alongside it, with a carrier grade dialler, messaging across several channels and conversation intelligence all operating natively within that platform. Where that is genuinely the case, much of the customer's data remains inside a system they already contracted for rather than being copied into a separate vendor's estate, which is a materially better position than the typical integration pattern.
What it concentrates instead is telephony and communications content. A carrier grade dialler with messaging across two consumer channels means the vendor holds call detail records, recordings and transcripts where enabled, message content across those channels, and the numbering registrations behind them. Recording consent obligations vary by jurisdiction and party and sit with the customer, and messaging through consumer platforms carries the sending brand's own registration obligations.
A buyer should establish where call recordings and transcripts are stored, whether inside the record system or in the vendor's own estate, since that single answer determines which of the two custody positions actually applies.
Getting started
What it costs and what is included before the product is running.
Not published. No setup fee, onboarding charge, migration rate, professional services rate, seat minimum, contract length, trial term or free tier was located, and no pricing surface exists on which any would appear. The only published routes are a demonstration request and a contact page.
For this product two implementation costs are near certain and neither is addressed.
The first is record system configuration. A platform operating natively inside another vendor's record system must be installed into that environment and configured against the buyer's existing objects, page layouts, permissions and automation. That is administrator work in a system where changes are typically controlled, and it exists whether or not it appears on an invoice.
The second is telephony provisioning. A carrier grade dialler requires numbers, and messaging across consumer channels requires sender registration with the platforms concerned. Vendors elsewhere in this index publish those costs at roughly $1 to $5 per number monthly with registration fees in the hundreds, and this vendor publishes none of it.
The cost that dominates everything and is entirely outside this vendor is the underlying record system license. Because the product lives inside that platform rather than integrating with it, a buyer without those licenses cannot use this product at all, and one with them is adding to a bill rather than consolidating it.
A buyer should require the quote broken into license, telephony usage and implementation, and should establish whether the field application carries its own charge.
What to watch for
Where this pricing can surprise a buyer who has not read it closely.
No price, no pricing page, and a product architecture that makes the absence more consequential than usual.
The dedicated pricing address returns not found. The homepage carries no pricing route, and the only commercial paths published are a demonstration request and a contact page.
The metering basis is unpublished alongside the rate, and for this product the range is wider than for most. The platform is a dialler with messaging, sequences and conversation intelligence operating inside a named record system, so charging could plausibly be per seat, per dialler license, per connected minute, per message, per recorded conversation, or as a platform license banded by the customer's existing record system footprint. Those produce very different bills for identical usage.
The telephony dimension makes the absence sharper than a bare seat rate would.
Every telephony vendor recorded in this index publishes at least part of its usage layer:
- ›Aloware publishes minute bundles, message rates and number costs
- ›Kixie publishes usage rates while withholding seat rates
- ›Ringover publishes international per minute rates.
This vendor publishes neither the seat rate nor the usage layer, which means a buyer cannot estimate any component of a dialling operation's cost.
One structural fact is published and it bears on total cost more than any rate would. The product operates natively inside a specific record system rather than integrating with it, which means the buyer must already hold licenses for that platform, and the eventual quote sits on top of a substantial existing subscription rather than replacing anything. A buyer comparing this against a standalone dialler is comparing a supplement against a substitute.
A mobile application for field representatives is published as recently launched, and outsourced sales and marketing teams are named among the intended users, which suggests some arrangements involve services alongside licenses. Nothing published prices either.
No credible third party estimate with sufficient corroboration was located, so none is recorded.
No dollar figure is recorded in the numeric field and no estimate is recorded in the display field.