# Message test — https://www.klenty.com/feature/connect-ai/?ref=navbar After reading your page, only 7 of 15 personas could name a reason to pick you over a similar option. - **Page tested:** https://www.klenty.com/feature/connect-ai/?ref=navbar - **Audience tested against:** An SDR manager at a 200-500 employee company with a team of 5-10 SDRs who do cold calling into the US, where the team struggles to have conversations and sees low connect rates. They might already use tools like Outreach or Nooks or Orum for dialing. The presure theyre under is to hit quota, prove outbound can be a growth channel, and board asking for pipeline This is NOT for teams who do very low-volume calling or treat email as the primary outbound channel. - **Personas:** 15 simulated - **Report:** https://grader.wynter.com/r/connect-ai-maximize-call-connect-rates-2fKZEcY > These answers are generated by AI, scored on Wynter's B2B Message > Layers framework using behaviorally-diverse simulated personas. The > methodology is real and the critique is directional. What a simulated > persona cannot have is a live budget, a renewal coming up, or a boss > asking about this quarter. --- ## 01 · The scores Every persona answered all four questions. These are four independent proportions of the same panel, not stages of a funnel. | Layer | Question | Cleared the bar | Strength | Of those who passed | | --- | --- | --- | --- | --- | | 1. Clarity | Do they understand what you do? | 10/15 | 78% | all with reservations | | 2. Relevance | Can they tell what it solves, and who it's for? | 15/15 | 99% | 14 without hesitation, 1 with reservations | | 3. Value | Do they actually want it? | 12/15 | 67% | all with reservations | | 4. Differentiation | Is there a reason to pick you over the alternatives? | 7/15 | 50% | all with reservations | **Brand alignment** (a side metric, not one of the four layers) — 14/15, 74% strength (all with reservations). Does the page read like the company you actually are? **Fix first: Differentiation.** Earliest failing layer, walking the sequence in order — not simply the lowest score. ### What they thought you sell 1 of the personas who named a category got it wrong: - 1× “Number reputation management for sales dialers” --- ## 02 · What to change, layer by layer Ordered worst-first. Specific edits, not a restatement of the score. ### Differentiation **Add head-to-head data to the Orum/Nooks comparison table.** Naming competitors is read as a testable claim, but the table asserts differences without numbers. Add per-row evidence: number pool size, provider count, area code coverage. *effort high · impact high · tested against Proof next to the claim* **Name a customer who switched from a competing dialer.** The page gives no reason to pick Klenty over Nooks or Orum beyond feature lists either could claim. A named switcher with before/after connect rates does that work. *effort medium · impact high · tested against Give a reason to choose you* **Promote Number Remediation above the other reputation features.** The pause-and-ramp approach — restoring flagged numbers rather than discarding them — is the one mechanism read as genuinely distinct. It currently sits fourth in an undifferentiated list of five. *effort low · impact high · tested against Give a reason to choose you* ### Clarity **Replace "Connect Rate Infrastructure" with plain mechanism language in the H1.** The coined category reads as marketing jargon dressing up number rotation and reputation management. Say what it does — multiple carriers, local numbers, reputation repair on top of your dialer — instead of naming a category. *effort medium · impact high · tested against Plain language* **Move the "works on top of your dialer" line into the hero.** The positioning that respondents found clarifying — a layer over an existing dialer, not a replacement for Outreach or Salesloft — sits in the FAQ, far below the fold. Put it in the subhead. *effort low · impact high · tested against Show the product early* **Front-load the section heading about every dial.** "With Klenty's Connect Rate Infrastructure, Every Dial Has a Higher Chance of Turning Into a Conversation" buries the point behind the brand and the coined term. Lead with "More dials become conversations." *effort low · impact medium · tested against Front-load the meaning* ### Value **State the baseline and measurement window beside the 15%+ claim.** "Get a Connect Rate of 15%+" floats with no source, no before/after and no stated 1-3% industry baseline. Add the sample, the period and how connect rate is counted, directly under the headline. *effort medium · impact high · tested against Proof next to the claim* **Add a pilot offer that lets buyers verify on their own list.** Buyers said they would only believe the number after a two-to-four week test on their own data. Name the pilot — length, list size, what gets measured — next to "schedule a demo". *effort medium · impact high · tested against Answer the live objection* **Tie "Helping Over 5000+ Fast-Growing Sales Teams" to a connect-rate outcome.** A customer count and a logo wall prove adoption, not connect rates. Replace or supplement with one customer's before/after connect rate and team size. *effort medium · impact medium · tested against Proof next to the claim* ### Brand alignment (side metric) **Cut "Gain Unmatched Number Coverage, Worldwide".** "Unmatched" is a superlative sitting next to sections carried by checkable specifics like 335 area codes and STIR/SHAKEN Level A. State the provider count and countries covered instead. *effort low · impact medium · tested against Specifics beat superlatives* --- ## 03 · What is working ### The headline, subhead and FAQ state the problem and the buyer on the first screen Nine points credit the H1, subhead and FAQ with naming the connect-rate problem, the solution and the SDR/RevOps buyer without inference. Several noted the reader does not have to hunt for who the page is for. > The intended reader is also named explicitly, not inferred — "CONNECT AI FOR SDR TEAMS" up top, and the FAQ literally says "Who is Klenty's Connect Rate Infrastructure built for?" > > — Sales Development Manager, Technology, 501-1000 > the header "Get a Connect Rate of 15%+ With Klenty's Connect Rate Infrastructure" and the subhead about SDRs getting into more conversations told me the problem (low connect rates, calls flagged 'Scam Likely', wasted dials) within the first few lines. > > — SDR Manager, B2B Sales Services, 201-500 > The problem was clear within the first screen - "Low Connect Rates Are Costing You Pipeline. It's Not a Dialing Problem. It's an Infrastructure Problem." spells out exactly what's broken > > — Head of Sales Development, Technology, 201-500 > The audience is spelled out too, top of page: "CONNECT AI FOR SDR TEAMS" and later a FAQ literally titled "Who is Klenty's Connect Rate Infrastructure built for?" which names Orum, Nooks, Salesfinity, Outreach, Salesloft as the alternative > > — SDR Manager, SaaS, 201-500 > the H1 "Get a Connect Rate of 15%+" plus the subhead "Low Connect Rates Are Costing You Pipeline. It's Not a Dialing Problem. It's an Infrastructure Problem" tells me the problem in one screen > > — Sales Development Director, Technology, 501-1000 > the FAQ explicitly segments out who this isn't for ("if your dialing goals are more activity... any parallel dialer will suffice") — that's a sales director's mental model of the market, not generic marketing copy > > — Sales Development Director, B2B Sales Services, 501-1000 > the FAQ format (calculating dial-to-connect rate, defining STIR/SHAKEN, explicitly saying "if you just want dial volume, go use Orum") is exactly the level of category fluency I'd expect from someone who's demoed this to people like me a hundred times > > — Sales Development Director, Technology, 501-1000 ### Respondents read Klenty as an infrastructure add-on layer, not a dialer or platform… Five points restate the positioning back accurately: a layer that fixes connect rates on top of an existing dialer, explicitly not a replacement for Outreach or Salesloft. The FAQ was named as where this lands. > it's an add-on infrastructure layer specifically fixing the "why don't people pick up cold calls" problem. > > — Sales Development Director, B2B Sales Services, 501-1000 > It's a cold-calling infrastructure layer that sits under a dialer — basically a service that manages your pool of outbound phone numbers so they don't get flagged 'Scam Likely,' matching local area codes to prospects and rotating/repairing numbers when their reputation tanks. > > — SDR Manager, B2B Sales Services, 201-500 > The one thing that would actually move me is the FAQ line explicitly naming who this is against — "any parallel dialer like Orum, Nooks, Salesfinity, or sales engagement platforms like Outreach and Salesloft" — because it's honest about being a different layer, not a rip-and-replace, which lowers the switching cost argument > > — SDR Manager, B2B Sales Services, 201-500 > They're a phone dialer add-on for outbound sales — basically a "connect rate" layer that sits under your dialer, managing a big pool of local/international phone numbers > > — Sales Development Director, Technology, 501-1000 > I picture a mid-stage B2B SaaS vendor, probably 100-300 people, maybe Series B/C, that started as a sales-engagement or dialer tool and is now trying to carve out a defensible niche against Outreach, Salesloft, Orum, and Nooks rather than compete head-on with them > > — Sales Development Director, B2B Sales Services, 501-1000 ### If the 15%+ number holds, respondents said it changes SDR capacity math Three points treated the claim as a 5-10x improvement over a 1-3% baseline that would meaningfully alter pipeline and headcount math — conditional on verification in every case. > If it actually delivers a 15%+ connect rate against the industry's 1-3% baseline they cite in the FAQ, that's not incremental — that's a 5-10x improvement in live conversations per rep per day, which directly moves quota attainment without hiring more SDRs. > > — Sales Development Director, B2B Sales Services, 501-1000 > If the 15%+ connect rate claim actually held up, that's a real shift — industry is 1-3% per their own FAQ, so even getting to high single digits would change SDR capacity math > > — Head of Sales Development, SaaS, 201-500 ### The named comparison table against Orum, Nooks, Outreach and Salesloft signals category… Four points valued naming competitors directly, reading it as a testable claim and as evidence the vendor knows the competitive set and the buyer's language. One noted the table still lacks head-to-head data. > The "Klenty vs Other Dialers" comparison table naming Orum, Nooks, Outreach, and Salesloft directly is the one thing that would keep me reading rather than closing the tab > > — Sales Development Director, SaaS, 501-1000 > that's a specific, falsifiable claim I can test against my own Orum data rather than marketing fluff > > — Head of Sales Development, Technology, 201-500 > naming Orum/Nooks/Salesfinity/Outreach/Salesloft by name shows they know their competitive set cold, which only a company that's been selling into this exact buyer for a while would bother doing > > — Sales Development Director, Technology, 501-1000 > the FAQ literally names my stack ("Orum, Nooks, Salesfinity... Outreach and Salesloft") and talks in terms I use - dial-to-connect rate, scam likely, area codes - so whoever wrote this has sat through SDR ops conversations before > > — SDR Manager, Technology, 201-500 > "5 Reasons to Choose Klenty" is just their framing of Orum/Nooks with no head-to-head data, and "15%+" still has zero baseline attached anywhere on the page. > > — Sales Development Manager, Technology, 501-1000 ### Checkable mechanism specifics — 335 area codes, CNAM, STIR/SHAKEN Level A, Number… Four points named these details as testable in a demo rather than positioning fluff, singling out the pause-and-ramp Number Remediation approach as distinct from simply discarding flagged numbers. > The comparison table's "Number Remediation" — pausing a flagged number and gradually ramping it back up rather than just discarding it — is a specific mechanism I haven't seen described that clearly elsewhere > > — Sales Development Director, B2B Sales Services, 501-1000 > "335 area codes covered in the US," CNAM registration in your own company name, and STIR/SHAKEN Level A attestation are concrete, checkable claims that competitors like Orum or Nooks (which the FAQ explicitly names as volume-focused) don't spell out in this much operational detail. > > — Sales Development Director, B2B Sales Services, 501-1000 > The comparison table row "Typically offer a few numbers per region/area code" vs. "Offers the deepest number inventory for your market" combined with the concrete number "335 area codes covered in the US" is the kind of specific I'd actually weigh > > — Head of Sales Development, SaaS, 201-500 --- ## 04 · What the personas said ### 'Connect Rate Infrastructure' reads as jargon dressing up number rotation Three points pushed back on the category language, calling it marketing jargon that needs unpacking and describing the product as number rotation and reputation management rebranded as a new category. > It's the branding layer, not the mechanics — 'Connect AI,' 'Connect Rate Infrastructure,' 'infrastructure' get stacked on top of what's really number rotation and reputation management, and that made me re-read twice to confirm it wasn't some new dialing tech. > > — SDR Manager, SaaS, 201-500 > the term 'Connect Rate Infrastructure' itself is marketing-speak that took a beat to unpack since it's not an industry-standard term > > — Sales Development Director, Technology, 501-1000 ### A named customer with before/after connect-rate data is the missing proof asset Five points asked for the same thing: a named reference, ideally a similarly-sized B2B team or one switching off Nooks, with before/after numbers measured the same way. One read the absence as a sign the proof assets aren't built yet. > A named case study from a team that switched off Nooks specifically, with before/after connect rate numbers over a real time period and rep headcount — not a logo wall, an actual reference I could call > > — Sales Development Director, SaaS, 501-1000 > A named customer reference with before/after dial-to-connect numbers on a segment comparable to ours, measured their own suggested way (live conversations per 100 dials, same rep/list/timezone) — without that it's just a headline number I can't act on. > > — Head of Sales Development, SaaS, 201-500 > I'd take the meeting specifically to ask for named customers with before/after connect-rate data tied to their claim, because "15%+" with no source and no case study attached means right now I can't tell if this is a genuine 5-10x lift over our baseline or marketing math > > — SDR Manager, B2B Sales Services, 201-500 > What would push it from 'relevant' to 'this is for me specifically' is a named case study from a similarly-sized B2B sales services or SaaS team using Outreach today, showing they layered Klenty on top rather than ripped and replaced, since that's my exact situation. > > — Sales Development Director, B2B Sales Services, 501-1000 > the complete absence of a named case study or before/after chart for the headline "15%+" claim tells me they're still building out proof assets — a company with a mature enterprise motion would have a logo'd case study front and center. > > — Sales Development Director, B2B Sales Services, 501-1000 ### The 15%+ connect rate claim carries no source, methodology or baseline Six points flagged the headline number as unverified: no methodology, no before/after, no stated baseline against the 1-3% norm. Two said validation would require a 2-4 week pilot on their own list before they'd believe it. > I'd walk in skeptical of the headline number because there's no source or methodology behind "15%+" on the page itself — no case study, no logo with a before/after, no cohort size. > > — Sales Development Director, B2B Sales Services, 501-1000 > those read like marketing round numbers, not measured results > > — Head of Sales Development, Technology, 201-500 > the page never quantifies that gap — it just asserts "15%+" with zero baseline, sample size, or methodology > > — Sales Development Director, SaaS, 501-1000 > "5 Reasons to Choose Klenty" is just their framing of Orum/Nooks with no head-to-head data, and "15%+" still has zero baseline attached anywhere on the page. > > — Sales Development Manager, Technology, 501-1000 > I'd want them to run our own numbers (our current connect rate, our list volume, our markets) against their infrastructure for 2-4 weeks and show me the before/after > > — Sales Development Manager, Technology, 501-1000 > the unsourced "15%+" headline stat and the comparison table with no named case study feels like it's written by a marketing team who assumes I won't ask for proof > > — Sales Development Director, SaaS, 501-1000 --- ## 05 · The hardest read An adversarial pass over the findings. Every claim below was checked against the panel's own answers; unsupported ones were dropped. - **The page's entire value proposition is suspended pending evidence the page does not provide.** *(high)* Six points flagged the 15%+ claim as having no methodology, baseline or before/after, and the three points that called it a 5-10x capacity change made it conditional on verification in every case. - **The page converts interest into a pilot request rather than a buying decision, lengthening the sales cycle by weeks.** *(high)* Two points said validation would require a 2-4 week pilot on their own list before belief, and five asked for a named reference with before/after numbers measured the same way. - **The absence of a named customer reads as a signal the product isn't proven, not just that the page is incomplete.** *(high)* Five points asked for a named reference, ideally a similar B2B team or one switching off Nooks, and one read the absence as evidence the proof assets aren't built yet. - **The competitive table invites a comparison the page then loses, because it names rivals without producing head-to-head data.** *(medium)* Four points valued naming Orum, Nooks, Outreach and Salesloft as a testable claim, but one noted the table lacks head-to-head data — and five separately asked for a reference switching off Nooks. - **The invented category label undercuts the credibility the mechanism details earn.** *(medium)* Three points called 'Connect Rate Infrastructure' jargon rebranding number rotation and reputation management, while four cited 335 area codes, CNAM and STIR/SHAKEN as testable rather than fluff. - **Clarity is the page's only uncontested strength, and clarity alone closes nothing.** *(medium)* Nine points credit the H1, subhead and FAQ with naming problem, solution and buyer without inference, yet every value and proof theme is negative — the page is understood and disbelieved simultaneously. --- ## 06 · Who answered | # | Role | Industry | Company size | | --- | --- | --- | --- | | 1 | Sales Development Director | B2B Sales Services | 501-1000 | | 2 | Head of Sales Development | SaaS | 201-500 | | 3 | Sales Development Manager | Technology | 501-1000 | | 4 | SDR Manager | B2B Sales Services | 201-500 | | 5 | Sales Development Director | SaaS | 501-1000 | | 6 | Head of Sales Development | Technology | 201-500 | | 7 | Sales Development Manager | B2B Sales Services | 501-1000 | | 8 | SDR Manager | SaaS | 201-500 | | 9 | Sales Development Director | Technology | 501-1000 | | 10 | Head of Sales Development | B2B Sales Services | 201-500 | | 11 | Sales Development Manager | SaaS | 501-1000 | | 12 | SDR Manager | Technology | 201-500 | | 13 | Sales Development Director | B2B Sales Services | 501-1000 | | 14 | Head of Sales Development | SaaS | 201-500 | | 15 | Sales Development Manager | Technology | 501-1000 | --- ## 07 · Before you act on this The methodology is real, and the critique is directional. What a simulated persona cannot have is a live budget, a renewal coming up, or a boss asking about this quarter. **Validate anything you're betting on with real ICPs who are actually in-market.** Being wrong is more expensive than you think. Finding out is cheaper than you'd guess. Wynter runs message testing with verified B2B professionals — trusted by HubSpot, RingCentral, Shopify, Cognism, Paddle, Veeam, Rippling and Miro. This report is kept for 60 days from 2026-08-28, then deleted along with the personas and their answers.