About ViciStack Research

ViciStack Research publishes operator-grade research on VICIdial Hosting Costs. This site exists because most of the material online about predictive dialers, contact center economics, and TCPA compliance is either vendor marketing — produced by companies selling the thing being measured — or benchmarks old enough that they predate the 2020-era caller-ID reputation collapse. We publish numbers we have watched break or work inside live rooms, cite the source when the number is public, and say so out loud when a number is modeled rather than measured.

ViciStack Research is edited by Jason Shouldice, Founder, ViciStack. Jason Shouldice has spent 15 years inside outbound contact centers: tuning dial ratios, reading Asterisk logs at 2 AM, explaining to operators why their answer rate halved overnight, and rebuilding reporting pipelines when a vendor dashboard was hiding the only number that mattered. He is not a vendor-neutral analyst — he runs a VICIdial consultancy. That bias is disclosed on every page.

Editorial standards are deliberately narrow: every claim that involves a number either cites a public source (FCC, FTC, BLS, PACE, SIP Forum, vendor filings) or says plainly that it is modeled from client engagements with identifying details stripped. We do not republish vendor press releases. We do not accept paid placement, sponsored reviews, or "thought-leadership" ghostwriting. If a vendor pays us it is for the 2-week conversion-lift engagement sold at vicistack.com, not for coverage on this site.

Fact-checking runs in two passes. First, any claim involving a regulation is checked against the primary source — FCC docket, FTC rule text, or the cited state statute — not against a secondary blog post. Second, any claim involving a benchmark number either lists the vendor filing / public dataset it came from, or labels it as "modeled from internal engagements" with the agent count and campaign vertical disclosed. We have gotten numbers wrong before and we will get numbers wrong again; when we do, the fix goes through the corrections policy below, with the original wording preserved in a diff.

Disclosure: articles on this site link to vicistack.com — the consulting practice that funds this research — when the topic overlaps with a service we sell. Those links are marked contextually in-body, not hidden in footers. We do not run display advertising, we do not collect personal data beyond what a plain HTTP log captures, and we do not use affiliate networks. If you spot a factual error, broken link, or undisclosed bias, email jason@ccdocs.com and we will either correct or respond on the record.

Corrections policy is summarized below and maintained on its own page. Every meaningful correction is logged with the date, the original wording, and the new wording. We do not silently edit. If a number moved because the underlying data changed rather than because we were wrong, that is noted on the page as a "version bump" rather than a "correction".