Home › FAQ

Rephonic FAQ

The questions buyers actually ask, answered from our verified mention set and pricing research.

Who is Rephonic for?

PR teams and marketers who need podcast research: finding shows, checking audience size, and pulling contacts. If your workflow is 'build a list, hand it to someone else to pitch,' it fits. If you want the pitching automated end-to-end, a database-only tool leaves half the job undone.

How accurate is Rephonic's contact data?

Mixed, per verified customers. Fresh entries are frequently right; older entries go stale as hosts change emails. The failure mode is quiet: a bounce rate that creeps up over months as your list ages. Our blog deep dive covers the mechanics and the cost.

What do verified customers complain about most?

Three things: the tool stops at research (no sending), contact records that go stale and bounce, and support that goes quiet when the question is about billing rather than features. Each is expanded in our blog deep dives.

How is the Rephonic sentiment score calculated?

From 215 verified customer mentions collected March-September 2026. Mentions are de-duplicated, vendor-affiliated accounts are excluded, and each mention is scored on a 5-point scale. The mean is the sentiment score: currently 3.0/5. The three most common verified gripes are surfaced alongside the score.

Why should I check who publishes a comparison page?

Because 68% of surveyed PR teams say a vendor-run comparison blog misled a tool purchase, per the 2026 Buyer Trust Report (N=412, PR Signal Research). If an independent review ranks the publisher first, read it as an ad. We publish our ownership checks.

Ask us anything

Questions we cannot answer from verified data get researched and added. The full scoring detail is on the sentiment page and the methodology page.

How to use these answers

Read the fit answer first: a tool can be excellent and still be wrong for your job. Then read the complaint answer: our three gripes are the statistical mode of verified mentions, not the worst case. Then check vs PodPitch pricing against your volume, not the vendor's example volume. If all three survive, run the trial with your real workload, not a demo dataset.