SDRx by Klenty

Models run the core of the job: learning the customer's business, choosing ideal accounts, researching each one into a business case, writing one to one emails from 25 frameworks, checking drafts for hallucinations and adapting follow ups to each prospect's stage. Beneath that sit conventional parts that work on their own, a 600 million contact prospecting database, sending infrastructure and CRM sync from Klenty's engagement platform.

Two modes set the boundary. On autopilot SDRx handles outbound end to end, from list building to the booked meeting; as a copilot it researches accounts, finds contact data and drafts emails that reps send. Every email passes an automated review for hallucinations, errors and value proposition mismatches before sending. Human approval steps inside autopilot, and how a running campaign is halted, are not described.

The work SDRx does is described step by step, but the language models and providers behind it are unnamed, and the logic for picking ideal accounts and adjusting follow ups is explained only by its goal. Emails are written to read as personal one to one messages from the seller, and whether recipients learn that software wrote them is not addressed.

SDRx is sold on outcomes, promising a day and night difference in outbound activity and results from day one. The case for it leans on an industry figure of 1,440 emails and calls to create one opportunity, and no customer, measured result or case exists for SDRx itself. Results attributed to Klenty's wider platform are not tied to the AI SDR.

Klenty's terms forbid using the service to send unsolicited email in violation of applicable law, which places compliance on the customer. SDRx sends cold email at volume, reaches prospects on LinkedIn and pairs with an AI calling agent, yet unsubscribe handling, CAN SPAM and GDPR marketing rules, and consent for calls are not addressed within the product.

SDRx runs under Klenty's privacy policy, last revised in May 2018, and its GDPR page. A data processing agreement with standard contractual clauses is available by email request, and Google Workspace data is held to Google's Limited Use rules. Lawful basis for the prospects drawn from the 600 million contact database, a subprocessor list and rights handling for those prospects are not addressed.

List building draws on a prospecting database of 600 million contacts with pre validated details, and email personalization uses CRM data, LinkedIn data and other external sources. Where the database comes from, under what licenses, and how LinkedIn data is obtained are not explained.

Outreach runs on LinkedIn as well as email, and LinkedIn data feeds the research behind each message, while nothing explains how the product reaches LinkedIn or how that fits a platform that prohibits automated activity. CRM connections to Salesforce, HubSpot, Pipedrive and Zoho run through standard integrations, and Google Workspace access follows Google's Limited Use rules.

Each customer's material, its customers, solutions and value proposition, is what the agent learns from, yet whether that material or CRM data also improves models used for other customers is not addressed. Google Workspace data is never used to train generalized AI models. Retention of research, drafts and prospect data follows Klenty's account based retention terms.

Prospects receive personal looking one to one emails and LinkedIn messages written by SDRx under the seller's name, and sending patterns are randomized and varied. Whether any message identifies itself as machine written is not stated, and Klenty takes no position on Article 50 of the EU AI Act. The marketing does not claim that recipients cannot tell.

Dedicated integrations with Salesforce, HubSpot, Pipedrive and Zoho CRM import contacts and keep them updated in real time in both systems, and SDRx reads CRM data to personalize outreach. It inherits Klenty's wider connector set for engagement. Field mapping, sync direction per object and an API for SDRx are not described.

As a hosted service under Klenty's privacy policy, data may be stored and processed in the United States or other countries Klenty chooses, with standard contractual clauses available through its data processing agreement. Hosting providers, regions and residency options are not named.

SDRx carries no certification of its own and no trust center, and security questions route to Klenty's responsible disclosure program. Klenty reports a SOC 2 Type II attestation for its engagement platform, and whether that report covers SDRx's research, drafting and sending components is not stated. SDRx holds connected mailboxes, purchased subdomains and LinkedIn activity for its customers.

Buying starts with a demo. SDRx has no public plans, prices, usage units or seat terms, and Klenty's own price list covers its engagement plans without the AI SDR. Costs for the 600 million contact database, purchased subdomains and the calling agent are likewise unpriced.

Contacts and activity sync continuously to the customer's CRM, and Klenty's GDPR page covers imported and exported CSV files, so a working copy of prospects sits outside the product. Ownership of the purchased sending subdomains, export of research and drafts, and deletion timelines after termination are not addressed.

Deliverability is run for the customer: SDRx buys sending subdomains, warms them up, rotates inboxes, configures DMARC, DKIM and SPF, controls volume, and varies and randomizes sending frequency, with the aim of landing emails in the primary tab. Daily caps, spam complaint thresholds and the response when a domain's reputation drops are not specified.

The pitch is any sales team's first AI SDR hire, working alone or alongside reps, with no stated company size, industry or region. No customers are named for the AI SDR, though Klenty itself serves more than 5,000 sales teams. Languages supported for research and writing are not given.