PhoneBurner

The entry tier contains no model at all and it is the product most customers buy. Everything at the base level is deterministic: single line dialing, a contact record system, workflow automation, cadences, dispositions, one click voicemail drops, email sending, lead distribution and session reporting. Model driven capability appears twice and both times outside the core.

Noise cancellation is supplied by a named third party from the second tier, transcription with an automated note taker is reserved to the top tier, and the scoring layer that predicts which numbers will connect is an unpriced add on rather than a plan feature. Strip all of it and the dialer is unchanged. That is the established platform pattern this index grades in the middle of the band, and here the tier structure states it plainly rather than leaving it to be inferred. Ask what the top tier delivers beyond transcription, and whether the scoring add on is worth its unpublished price against your own list quality.

A person drives every call and the automation sits either side of the conversation. The dialing model requires a representative in an active session, so nothing places calls unattended, and there is no conversational agent, no autonomous outbound and no scheduled campaign running without someone present. What does run on its own is the surrounding workflow: cadences advancing, emails and messages dispatching on rules, leads distributing across a team and dispositions triggering follow up.

Oversight is published as named features rather than promises, covering permission control, an administrative portal for seats and configuration, smart lead distribution, live call monitoring and live coaching from the second tier, real time leaderboards and a live dashboard. Graded in the middle of the band because the automation is real but bounded and the controls over it are ordinary rather than distinctive. Ask what an administrator can prevent a representative from doing, and whether workflow sends can be paused centrally.

One supplier named outright, the rest unstated. The noise cancellation layer is attributed to a named third party product in the plan comparison rather than presented as the vendor's own capability, which is a small but genuine disclosure and rarer in this index than it should be, since most vendors present bought in components as their own. Beyond that nothing is named.

No provider, model family or version appears for the transcription and automated note taking on the top tier, nor for the scoring layer that decides which numbers a representative never dials, and that second one carries consequence: a filter that removes contacts from a list before anyone calls them is making a decision about who gets contacted, with no published account of what it reads or how often it is wrong. An open interface and a developer section exist for building around the platform. Ask what the connect scoring model uses as inputs, and what its false negative rate is on numbers it filters out.

A quantified headline claim with nothing behind it, and testimony that carries names but no numbers. The product navigation states that the dialer increases answer rates by up to four times, which is the central purchase argument, and no sample, period, baseline, comparison or method accompanies it anywhere reached. Two testimonials on the pricing page name the individual and their company and are qualitative, describing improved outbound volume and connection rates without a figure.

Scale is given as more than three thousand customers and millions of monthly conversations, neither dated nor defined. A customer stories section and a reviews section exist and were not reached on this pass. The gap is conspicuous because the vendor sells an add on whose stated purpose is answer rate analytics, which means it measures the very number its headline claim rests on. Ask for measured answer rates before and after, over a stated period, and the definition of the baseline behind the fourfold claim.

The strongest compliance posture graded in this batch, and most of it is architectural rather than advisory. The product will not place a call after nine in the evening local to the area code being dialed, and the vendor states the limitation and its one exception for toll free numbers rather than leaving it to be discovered. A customer's own do not call list is honoured at the dialing layer, so a suppressed number is not dialed regardless of what a representative does.

Real time screening against the national register and against known litigants and serial plaintiffs runs through a named compliance vendor with a prebuilt interface. Most tellingly, the vendor refuses to build multi line and predictive dialing at all, on the published ground that dropped calls expose customers to telephone consumer and telemarketing sales rule penalties, which is a revenue generating capability declined and the regulation named as the reason.

Supporting material cites the governing statute, the telemarketing rule, the federal trade commission guide and the specific code section, and a separate acceptable use policy covers messaging. Held short of nothing: national register screening requires a separate paid subscription with the third party rather than being included, so the strongest single control is an extra purchase.

One retention figure published as a number, and the instruments behind it unread. The plan comparison states call recording storage as thirty days, ninety days and unlimited across the three tiers, which is a rare thing to find on a pricing page: most vendors describe retention in the abstract or not at all, and this gives a buyer an actual period for the most sensitive material the platform holds. Contact import ceilings are similarly given as monthly figures per tier.

Terms, a privacy policy and an acceptable use policy are published in the footer alongside a trust report on its own subdomain, and none was retrievable on this pass, so lawful bases, the rights exercise route and the treatment of recorded parties are unestablished and nothing here asserts they are absent. The material at stake is recorded telephone conversations with people who are not customers. Ask what the rights exercise route is for a person recorded on a call, and whether recordings are deleted or merely at the end of the stated storage period.

No purchased corpus behind the product, and one add on that depends on data the vendor does not describe. There is no contact database, no enrichment and nothing brokered: contacts arrive from the customer's own record system or by import under published monthly ceilings, so the usual chain of sources, licences and resale permissions does not apply and most of the axis sits out of scope.

What does sit in scope is the connect scoring add on, which filters out numbers described as disconnected or unlikely to answer before a representative sees them. Determining that a number is disconnected or low probability requires either carrier level data, aggregate outcome data across the vendor's customer base, or a third party source, and nothing published states which. If it is aggregated outcomes, one customer's dialing results are shaping another's list. Ask what data the connect scoring add on draws on, whether it aggregates results across customers, and whether a customer can decline to contribute.

The telephony is the vendor's own and every software connection runs a sanctioned route. Calls originate on carrier infrastructure the vendor contracts for, described in the plan comparison as a first tier carrier, and dedicated numbers are provisioned by the vendor as a purchasable add on, so a customer is not borrowing access to a platform that another company could withdraw.

On the software side more than a hundred integrations are claimed with four named individually and given their own pages, covering three customer record platforms and a marketing automation suite, each reached through that product's documented route, and an open interface with a developer section handles anything custom from the second tier upward. That architecture is what this axis rewards.

It stops below the top band because the governing regime for a dialer is carrier and messaging registry rules rather than software platform terms, and while messaging registration is stated as a precondition on the pricing page, no conformance position of the vendor's own is published against carrier requirements.

The training question is not addressed where a buyer would look. This platform records telephone calls on every tier and, at the top tier, transcribes them and generates notes, which makes the commitment direct: are customer recordings used to train or tune models, and does a third party transcription provider retain them.

Nothing on the pricing page, in the questions section or in the product navigation states a position either way, and the trust report on its own subdomain was not retrievable on this pass, so nothing here asserts the commitment is absent, only that it was not found. Two adjacent facts are worth crediting. Recording retention is published as a stated period per tier rather than left open, which bounds how long material exists to be used.

And a named third party supplies the noise cancellation layer, which at least identifies one processor in the chain. Ask for a written statement that recordings and transcripts do not train any model, and which processors receive call audio.

The strongest set of recipient protections in this lane, and two published features pointing the other way. The protections are architectural and unusual. There is no dropped call, because the vendor refuses multi line dialing outright. There is no dead air, with delay free connection stated as a design property, so the recipient does not get the pause that signals an automated dialer. No call arrives after nine in the evening local to the area code. A suppressed number is not dialed.

Every conversation is with an actual person, since there is no synthetic voice and no agent. Against that sit two things the recipient is not told. A local presence capability displays a caller identity matching the recipient's area code rather than the representative's actual location, which is deliberate manipulation of the one signal a recipient uses to decide whether to answer.

And one click voicemail drops leave a prerecorded message in the representative's voice without them being present. Both are published plainly. Ask what caller identity is displayed under local presence and whether recipients can reach that number back.

A stated count with named destinations behind it and an interface a buyer can build against. More than a hundred integrations are claimed and four are named individually with their own pages, covering three customer record platforms and a marketing automation suite, and the questions section adds a video conferencing product and a general automation connector by name, so the claim is partly checkable rather than a bare number.

An open interface is a published tier feature from the second level upward and a developer section exists on the vendor's own domain. A system status page operates on its own subdomain, which is a real operational artifact and one many vendors in this lane do not publish. A separate publicly usable tool for testing whether a telephone number carries a spam flag is published free of charge, which extends the surface beyond customers. It stops below the top band because the interface is withheld from the entry tier, no reference documentation was retrieved on this pass, and no marketplace listing was established.

Operational geography is implied and data geography is unaddressed. What the pages establish is that support is delivered from within the United States, that a dial in connection method is offered for long distance calling within North America, and that the named industry pages and compliance material are oriented entirely to United States regulation, so the operating market is clear even though it is never stated as a coverage claim. What is absent is every question this axis asks.

No hosting provider, region, processing location, residency election or cross border transfer mechanism appears anywhere reached, and the trust report was not retrievable on this pass so nothing here asserts it is silent on the point. The stored material is recorded telephone conversations, held for periods the vendor publishes, which makes the location of that storage a first order question for any buyer with obligations outside the United States. Ask where recordings and contact data are stored, and whether any region can be elected.

A real certification of the stronger type, displayed on the vendor's own pages, with a trust report and a status page behind it. The attestation badge in the site footer is the period type rather than the point in time type, which is the distinction that matters and which a comparable vendor graded this same session fails to state consistently about itself.

A trust report operates on its own subdomain and a system status page on another, both linked from the footer, alongside published terms, a privacy policy and an acceptable use policy. A dedicated trust address is published in the support material for compliance and security questions, which is a named route rather than a general contact form.

Held below the top band because the trust report was not retrievable on this pass, so no auditor, audit period, report request process or enumerated control set was established, and no examination report or public artifact was located. Ask for the current report, its audit period and the auditor, and what the trust report contains.

Three tiers fully priced at both billing frequencies with a detailed comparison behind them, undercut by three unpriced add ons. The published side is solid: per user rates at every tier on both monthly and annual billing, a comparison table running to roughly fifty rows, usage ceilings given as actual numbers covering call recording storage in days and contact imports per month at each level, a messaging overage rate stated per thousand outbound messages, an explicit statement that no setup fees apply, and a free trial with dialing minutes included.

Against that, three add ons carry no price at all, and they are not peripheral. Dedicated numbers are required for inbound handling below the top tier, the number reputation and spam remediation service is the mechanism protecting the answer rates the product is sold on, and the connect scoring layer determines list efficiency. The convention withholds the top band precisely where load bearing add ons are unpriced, and all three qualify. Ask the monthly rate for each add on at your seat count before comparing this to anything else.

One retrieval route exists and the retention position works against a departing customer. An open interface is available from the second tier upward and would provide a programmatic path to extract contacts, activity and call records, though it is not documented as an export mechanism and is withheld from the entry tier entirely.

What is published and unusual is the storage position, and it cuts both ways: call recordings are retained for thirty days on the entry tier and ninety on the second, which means that during ordinary use the recordings a customer might want to take with them have already been deleted, and only the top tier keeps them indefinitely.

Nothing published describes a bulk export of contacts, dispositions, activity history or recordings, and nothing states what happens to any of it after cancellation or how long a departing customer has to act. Ask for a documented export of contacts, call history and recordings, and the retention window after an account closes.

A genuine apparatus for the voice equivalent of deliverability, with the two mechanisms that matter most sold separately. The architecture contributes first: delay free connection is stated as a design property so no dead air precedes the greeting, and the refusal to run multi line dialing means no dropped calls, both of which affect whether a recipient stays on the line and whether carriers learn to distrust the number. Carrier quality is stated as a first tier route on every plan.

Beyond that, a number reputation service monitors caller identity for spam flags and performs remediation, a scoring layer filters disconnected and low probability numbers before dialing, a local presence capability matches caller identity to the recipient's area code, and a dedicated call deliverability section and a free public spam flag testing tool both exist.

It stops below the top band because the reputation and scoring services are unpriced add ons rather than included capability, and because no answer rate, connect rate or spam flag incidence is published despite the reputation product being sold on answer rate analytics.

Five industries addressed with their own pages and a size range stated plainly. The verticals are financial services, mortgage, insurance, political campaigning and solar, and the questions section adds technology and software to the list of sectors served, while stating the customer base spans small businesses through to enterprise, so both the sector and the size dimension are described rather than implied.

Support is stated as delivered from within the United States and a dial in method is provided for long distance calling within North America, which locates the operating market concretely. Three tiers with published rates give every size a costed path. Two limits hold it below the top band.

Several of the named verticals sell to consumers rather than to businesses, which a buyer sharing carrier reputation on the same platform should weigh, and no coverage outside North America is described anywhere, with no international calling position, no market list and no support hours stated for any region. Ask which countries can be dialed and what support hours apply outside North America.