Reply.io Review

Reply.io is worth shortlisting when your SDRs need email, LinkedIn and calls in one managed workflow. This Reply.io review puts the practical starting point at $99 per user/month for Multichannel, or $89 with annual billing; Jason AI SDR is a separate buying decision, starting at $800/month, or $500/month billed annually. Choose it for coordinated execution and supervised automation, with a named person still owning the offer, exceptions and sales conversations.

Verified on 19 October 2026 against Reply.io's live product pages, pricing and operating documentation. This is a documented product evaluation, not a campaign test. The judgment turns on channel coordination, control over AI messages, contact economics and the work left with your reps. Prices are in USD; Reply's pricing page supplies the figures above.

What Reply.io Is

Reply.io is a sales engagement platform: software that organizes who a salesperson contacts, through which channel, and what happens next. It combines prospect data, email and LinkedIn sequences, calling tasks, a shared inbox, reporting and meeting booking; Jason AI SDR adds generated outreach, continuing prospect discovery and automated reply handling. Its contact records support outbound work, while your customer relationship management system, or CRM, remains the place to own deals and the sales pipeline. For a founder managing SDRs, the useful distinction is between buying a coordinated workspace for people and delegating parts of their work to an agent. Reply sells both. Product scope.

Who Should Use Reply.io, and Who Should Skip It?

Reply.io fits a B2B team whose buyers need a coordinated sequence of email, LinkedIn contact and a rep's call. An SDR lead gains more from assigning that next action reliably than from collecting another writing assistant. It also merits consideration when sourcing contacts and responding to routine questions consume time that the team can identify and supervise.

Skip the broad platform if your only requirement is email sending. Instantly, an email outreach platform, is a narrower shortlist candidate. Consider lemlist, a sales engagement platform, when you want another direct option for rep-led email, LinkedIn and calls. Neither alternative removes the need for a defined audience or someone responsible for interested replies.

These are monthly-billed prices, not equivalent bundles. Reply and lemlist figures select the multichannel plans relevant to this reader; Instantly's row distinguishes basic sending from a shared reply workflow. Sources: Reply, Instantly pricing, Instantly plan permissions and lemlist.

Alternatives: Instantly and lemlist

Instantly AI Reviews: Check the Reply Workflow

Instantly fits when email is the primary channel and you already know who should receive it. Its sending and warm-up features can coordinate multiple mailboxes, but the Growth plan's inbox and team restrictions matter to an SDR lead. Start with our Instantly AI review, which examines that handoff, then use Smartlead vs Instantly if the choice is mainly about the email sending system. Data is separately sold, so the cheapest sending subscription is not the complete sourcing budget. Current plans.

lemlist Pricing: Compare the Multichannel Plan

lemlist is the closer alternative for a rep who wants email, LinkedIn automation and a built-in dialer in the same workflow. Its Multichannel plan includes five senders per user; lead data has separate add-ons. Choose between it and Reply by walking the same prospect through a connection request, call task and reply, then checking which setup your reps can maintain. Do not pay for both during production merely because their personalization demos look different. Plan details.

For a wider shortlist, see the best AI cold email tools. The decision here is narrower: whether Reply's combined workflow solves a daily coordination problem for your sales team.

Multichannel Sequences: Give Every Touch a Next Action

Reply.io's strongest conventional capability is putting different kinds of outreach into one sequence, a planned series of actions with delays and conditions. A contact can receive an email, move to a LinkedIn step, generate a call task and enter a different branch depending on available data or connection status. That is useful when a founder wants a consistent sales motion across reps without maintaining separate task lists. Multichannel documentation.

Email steps can send automatically or wait for a person. LinkedIn automation includes connection requests, messages and InMails, with other actions such as following profiles and sending voice messages. Calls use Cloud Calls, Reply's built-in calling feature, to place and record calls and log outcomes. SMS can run automatically or as a manual task; WhatsApp steps are semi-automated tasks. These distinctions decide staffing: a scheduled call task still needs a rep to have the conversation. Channel features.

Consider a logistics-software founder targeting operations directors. The opening email introduces a specific scheduling problem. A later LinkedIn step gives the director another way to recognize the sender. A call task gives the SDR the context to ask whether that problem exists, rather than repeating an unrelated pitch. The benefit is continuity across those touches, not permission to add every channel to every campaign.

Set branches around information you can act on. A contact with a valid email can take the email path; someone with a LinkedIn profile but no usable email can take a different route. A person without a phone number should not sit indefinitely in a call queue. Reply documents branches for email validation, LinkedIn connection status and phone data, among other criteria.

Task completion settings deserve a deliberate choice. In manual mode, a contact waits for the task to be completed. In automatic mode, the sequence can advance after its delay even if the task was never done. If a call is essential to your approach, the second setting can make a campaign look orderly while the promised conversation never happens. Reply also requires at least a two-hour delay for LinkedIn connection-status conditions, so an immediate check is not a reliable design. Execution rules.

Cloud Calls additionally needs an enabled calling feature, a rented number and a funded wallet. Included calling access therefore does not establish that all telephony usage is free. Channel Efficiency reporting lets the lead inspect activity and outcomes by channel, rep and sequence; use it to remove touches that create work without useful conversations.

Reply.io Integrations: Keep Deal Ownership in the CRM

Reply.io lists native connections with Salesforce, HubSpot, Pipedrive, Copper, Close and Zendesk Sell, plus Zapier, Make, an n8n node, API access, webhooks and MCP. Its structured feature listing describes bidirectional synchronization for Salesforce, HubSpot and Pipedrive, covering records and activities such as contacts, accounts, calls, tasks and statuses. These are the vendor's listed integrations, not a claim that every field and workflow synchronizes identically. Reply's integration specifications.

For the logistics campaign, decide which system owns each decision: Reply executes the sequence; the CRM owns the opportunity; the assigned rep owns the next sales conversation. Before importing a full list, check a representative contact, a call outcome and a changed status through the integration you intend to use. Confirm whether an existing customer or open opportunity can be kept out of new outbound.

Reply's homepage also lists Gmail, Microsoft Office and Exchange, ActiveCampaign, Albacross, Skyvia, Weezly and Vidyard. An email-provider connection, a native CRM integration and an automation connector solve different problems; a logo alone does not prove your required sync direction. Listed business tools.

MCP, a protocol through which AI clients call tools, and the API are relevant if your own systems will operate Reply. They are optional for an SDR using the interface. Check the exact operation before designing an integration around it: Reply's documentation distinguishes live functions from partial or forthcoming API coverage. Interface scope.

Contact Data and Credits: Budget for the Records You Need

Reply.io includes prospect discovery, but a large data source and a large included allowance are different things. Reply markets access to a source of 1 billion B2B contacts; the Email Volume and Multichannel plans include 50 Live Data credits per month. Neither statement establishes how many suitable people it can find in your particular market. Published allowance and database claim.

Live Data searches LinkedIn-based information using job title, department, industry, location, keywords and company criteria. You can restrict a search to uploaded company domains, preview matches, and save results into a list or sequence. It skips contacts already saved in the account. A pasted Sales Navigator search can supply filters, but unsupported filters are skipped with a notice; inspect the translated audience before accepting it. Prospect-search behavior.

The documented charges are one credit for a LinkedIn-only contact, two for a contact with email and three per phone number found. That makes the included allowance concrete: 50 credits cover 25 email-bearing records, assuming those are the only charged actions. A list of 1,000 such records would require 2,000 credits, leaving 1,950 beyond the included allowance. This is allowance arithmetic, not a claim that every search succeeds. Credit rules.

For a founder who already owns a vetted list, imports can avoid buying the same records again. For an SDR lead starting with company names, budget for the fields the sequence actually needs. Buying phone data for a campaign with no calling step adds spend without changing execution. Conversely, building a call-first campaign from email-only records creates manual work before the first call.

Separate Finding Data From Validating It

Reply.io uses separate balances for data enrichment and email validation. Enrichment fills missing fields; validation checks whether an address appears usable. Validation returns Valid, Risky or Invalid, and Reply will not send sequence emails to an address classified Invalid. Extra data credits do not replenish the validation balance. Enrichment and validation documentation.

A sensible workflow is to preview the target audience, save a limited batch, find the missing contact information, validate the emails and then enroll the records that meet your rule. Preserve a path for incomplete records: review, another source, or exclusion. Do not let “no phone found” quietly become “SDR will research it later” without assigning that work.

AI custom-field enrichment also consumes Reply credits. The documentation says a processed request returning “No results found” can still be charged, while a system failure is not. For a campaign requiring a custom research field on every prospect, inspect the useful-output rate before scaling the spend. A successful API request or completed enrichment job is not necessarily a usable opening line.

Deliverability: Useful Controls Still Need an Owner

Reply.io brings the principal sending controls into the same workspace as the campaign: MailToaster warm-up, gradual increases in live sending, domain health checks, spam monitoring, tracking controls and template checks. For an SDR lead responsible for multiple mailboxes, that makes problems easier to find and assign. It does not establish an inbox-placement result. Deliverability documentation.

The features do different jobs:

• MailToaster warm-up exchanges simulated engagement with peer mailboxes. This is separate from a prospect campaign.
• Ramp-up increases the permitted volume of real outreach gradually. Reply documents a configurable default starting at 10 emails a day and adding three daily until 100; these are software defaults, not a safe-volume guarantee for your domain.
• Email Health Checker checks domain records including SPF, DKIM and DMARC, the records used to authenticate sending. With an externally managed domain, the administrator still applies the required DNS fixes.
• Google Postmaster integration supplies spam-rate monitoring after the domain's Postmaster account is connected.
• Custom tracking domains, tracking switches and template checks give the operator control over tracking links and message construction. How the controls work.

Reply also lists inbox rotation, provider matching and a global block list. Rotation distributes sending across connected accounts; provider matching pairs a sender and recipient using the same email provider. Those controls manage how the system sends. They cannot make a poorly selected audience relevant. Feature specifications.

For the logistics example, connect the intended mailboxes and inspect their health before scheduling outreach. Resolve authentication errors, turn on the appropriate warm-up profile, confirm the real sending cap and check the sequence schedule. Validate the imported list, exclude unwanted recipients and decide whether tracking is useful enough to keep. Once sending starts, assign someone to review delivery errors and complaints alongside genuine sales replies.

Keep the distinction between warm-up activity and campaign evidence. A mailbox receiving positive simulated exchanges has not demonstrated that your offer reaches, interests or converts operations directors. Reply itself says its deliverability score does not guarantee inbox delivery. The practical benefit is a set of controls and diagnostics; the ongoing judgment remains yours.

Jason AI SDR: Automation With Explicit Human Controls

Reply.io calls its AI sales development representative Jason AI SDR. Its documented scope goes beyond generating an email draft: it can turn your business material into offers, build sequences, source contacts continuously, research and personalize messages, handle replies, re-engage silent leads and schedule meetings. Whether it sends without intervention depends on the modes you configure. Jason product page and operating documentation.

Reply AI Means Jason AI SDR, With Inputs You Still Own

Reply.io separates the material guiding Jason into objects with different jobs. An offer describes the audience, problem, value and evidence. A playbook tells it how to write, including tone, instructions and subject-line rules. A knowledge base supplies the product information used to answer replies. Putting all three into a vague prompt leaves the most consequential decisions underspecified. Jason setup guide.

For the logistics founder, the offer might concern scheduling work for operations teams. The knowledge base should say which integrations exist and which do not. The playbook can require a brief, direct message and prohibit unsupported savings claims. A human has to verify those inputs. Jason can reuse a proof point at scale; it cannot turn an unsubstantiated assertion into evidence.

The contact-source automation is meaningful. Autopilot can keep a sequence supplied using audience filters and configured daily and per-company caps. Other documented sources include hiring signals, technology use, LinkedIn engagement and manual imports. Per-contact research can draw on company information and professional activity, with a template fallback when relevant research is unavailable. That removes repeatable work only when the resulting prospects and messages remain suitable. AI SDR capabilities.

Approval mode creates a concrete stopping point. Generated messages wait in Pending approvals, where a person can edit, regenerate or approve them. Automatic mode sends without that review. Start with approval when you are still learning the audience, then consider automation for a stable segment whose messages repeatedly meet your standard. Review capacity becomes a campaign constraint: an unattended approval queue means nothing leaves it.

Reply Handling: Automate Routine Answers, Escalate Commitments

Reply.io's reply handlers make a more useful distinction than a single “AI on” switch. For each question type, you can choose Auto, Draft, or Stop and notify. Auto sends the answer; Draft leaves it for review; Stop and notify pauses the contact and alerts the assigned rep. Threads classified Do not contact do not receive an AI-generated response. Reply-management rules.

For a founder, a request for an approved product overview may eventually be suitable for Auto. A question about an unusual integration belongs in Draft while the answer is checked. A request for a contractual commitment belongs with a person. Those are proposed operating rules, not defaults imposed by Reply. Configure the knowledge base, example answers and handler instructions to match your own authority limits.

Meeting-intent replies can lead to scheduling against a connected calendar or booking tool. Still give the prospect an owner. Someone must prepare for the conversation, decide whether the opportunity is qualified and maintain the CRM record. Booking is an administrative step in a sale, not evidence that the sale is qualified.

Also configure what a reply does to the original sequence. Reply documents stopping or continuing follow-ups as a per-sequence choice. Merely receiving a reply is not a substitute for checking that setting. SMS responses use a separate inbox, so a lead covering several channels should know which queues need attention.

Worked Example: One Outbound Campaign From Setup to Handoff

Reply.io can support the following campaign through its documented setup flow. This is an illustrative configuration, not a campaign run for this review. Assume a logistics-software founder and two SDRs want to contact operations directors at US firms with 50 to 200 employees. Begin with 100 vetted contacts and a single, defensible reason to talk.

1. 1

   Connect the channels and assign responsibility

   Connect the sending email accounts and the LinkedIn account intended for the campaign. If calling is part of the sequence, enable Cloud Calls and arrange its number and wallet. Name the SDR who owns replies and the person who fixes mailbox problems. The founder approves the offer; the reps handle conversations. This ownership is your process, not something an account connection supplies.

2. 2

   Create Jason's business context

   Open AI SDR → Jason AI SDR, or New sequence → Jason AI SDR. Supply the website and accurate product material. Review the generated audience, pain points, value propositions and proof before continuing. Remove claims about integrations or outcomes that the product material cannot support. If editing an offer shared with other sequences, use the separate-offer option when the change should apply only to this campaign.

3. 3

   Choose the audience before enabling continuous sourcing

   For the initial batch, use vetted existing contacts or a manual import. For continued sourcing, define the operations role, industry, geography and company criteria, then inspect the matches. A conservative illustrative starting rule is 10 added contacts per day and one person per company. These are chosen guardrails, not an optimal volume claim. If all 100 initial email-bearing records come from Live Data instead, the documented two-credit charge means 200 data credits before phone or AI enrichment.

4. 4

   Build the knowledge base and writing instructions

   Put approved product facts, supported integrations and relevant answers in the knowledge base. Give the playbook an explicit subject-line instruction and prohibit invented familiarity or unverified results. Ask personalization to connect the prospect's role to the scheduling problem. A generic compliment about the company is not a reason to buy. The person reviewing messages checks both accuracy and relevance.

5. 5

   Review every outreach step and its timing

   Inspect the generated sequence and edit its structure. One illustrative cadence is an email on day 1, a LinkedIn connection step on day 3, a human call task on day 6 and a final email on day 9. Treat those days as a starting hypothesis, not Reply's recommendation. Make the call step wait if completion is essential, and define how replies stop later touches. A call step assigns work to the rep; it does not establish an autonomous voice conversation.

6. 6

   Validate, schedule and keep approval on

   Validate the relevant email records using the separate validation balance and route unsuitable records out of the email path. Confirm mailbox health, daily caps, the sending window and the channels available on the purchased plan. Select Approval mode. At AI SDR → Pending approvals, read the generated messages before approving them. Regenerate an unsuitable draft if you want to keep the contact; deletion removes the prospect from the sequence.

7. 7

   Set reply handlers and the meeting handoff

   Begin with Draft for substantive product questions and Stop and notify for commitments a rep must make. Connect the intended calendar under Settings → Meetings if Jason will handle scheduling, or keep scheduling manual. Confirm the rule for opt-outs and the sequence's reply-stopping behavior. An interested reply goes to the named SDR, who checks fit and creates or updates the opportunity in the CRM.

8. 8

   Review the work before expanding the audience

   Inspect pending approvals, delivery problems, incomplete tasks and reply categories. Use source tags and channel reporting to see which contacts and touches deserve further effort. If sourced prospects are drifting, pause Autopilot; if the messages need review again, retain or restore approval mode. Assess the actual qualified opportunities against total spend and rep time before enlarging the campaign.

The navigation, approval behavior and source controls above follow Reply's setup documentation; the cadence, audience and staffing are illustrative choices. The data calculation uses Reply's published credit rates.

The same campaign can run as an ordinary Multichannel sequence if the founder supplies the audience and messages and the SDRs handle replies. That is the purchase test for Jason: identify which of prospect discovery, personalization and reply handling you will delegate, then verify the quality of those outputs. Buying the agent simply to assemble a sequence that rarely changes is a weak case.

What Reply.io Costs for This Team

Reply.io's Multichannel plan is the sensible starting point for this reader because LinkedIn and calls are part of the intended workflow. Email Volume is the lower entry for email-centric work; Jason AI SDR is the separate automation option. The following are starting configurations, not the full volume ladder. Live pricing.

The wall below Multichannel is straightforward: Email Volume plus LinkedIn and calling add-ons costs $59 + $69 + $29 = $157/month at the quoted starting configuration, versus $99 for Multichannel. That is $58 more before usage and infrastructure. Email Volume can still fit an email-focused operation with different mailbox requirements, but it is an awkward route to this single-rep channel mix. Add-on prices.

If the founder and both SDRs each need a seat, Multichannel is $297/month, or $267/month equivalent on annual billing, a $3,204 annual commitment. These are subscription calculations only. Data, validation, domains, mailbox subscriptions and calling usage can increase the working budget; an additional connected mailbox seat itself costs $29/month. Published plan and seat prices.

AI SDR Starter includes intent signals, personalization, approval or automatic operation, multichannel automation, deliverability assistance and onboarding. AI SDR Growth adds larger allowances, white-glove onboarding, a Slack channel and custom playbooks. AI SDR Enterprise is quoted and adds prompt engineering and CEO strategy calls. Check the selected contact allowance and LinkedIn-account entitlement in the actual quote: Reply's detailed dropdown data and general comparison grid do not consistently state the same account count. AI plans and structured pricing.

For agencies, Agency Core provides separate client workspaces, unlimited clients and users, email automation, warm-up, an agency dashboard, roles and templates, with LinkedIn optional. Agency AI SDR adds client-level agents, included email and LinkedIn automation, personalization, playbooks, live data and AI responses. The Hybrid plan combines standard multichannel and AI sequences. Those arrangements matter to a service business managing client operations; they are not the default purchase for an internal SDR team. Agency inclusions.

Jason Starter's monthly starting price works out to $0.80 per available active-contact slot if the full 1,000-contact allowance is used; its annual equivalent is $0.50. At only 500 active contacts, the monthly subscription is $1.60 per used slot. These are capacity costs, not costs per meeting or guaranteed results. The business measure is your total spend divided by the qualified opportunities you actually obtain. Use observed opportunities to calculate that result after launch. Starter price and allowance.

Limitations That Can Change the Decision

Reply.io's limitations are specific enough to evaluate before paying. For a founder, these operating rules matter more than a generic label such as “easy to use.”

“Unlimited mailboxes” has a defined fair-use ceiling. On Email Volume, Reply's support table allows 25 mailboxes at 1,000 active contacts, increasing with the allowance. Multichannel has its own included mailbox counts. Contact storage also defaults to 100,000 records; the support page prices another 100,000 at $30/month. A plan can provide generous capacity without being literally unbounded. Current limits.

Follow-ups can consume the next billing month's active-contact allowance. The pricing page emphasizes a first email plus follow-ups. The detailed support rule says a contact receiving an outreach step counts in that billing period, and a follow-up in another period counts the contact again. A founder planning only for newly sourced people can therefore underestimate usage. Use the detailed rule when budgeting a sequence that crosses renewal. Multichannel's unlimited active contacts avoids this particular allowance calculation. Active-contact accounting.

Jason's displayed research sources are not a reliable audit trail. Reply's operational documentation says the source explanation is generated after the message, by asking a model which research the finished text seems to use. It can include something unused or miss something used. If a message makes a factual assertion about a prospect, open and check the underlying material; a source label beside the draft is insufficient proof. This is a material limit for teams whose personalization depends on precise company facts. How Jason writes.

Out-of-office handling does not interpret the return date. Reply detects the response and can resume the contact after a configured number of days, but uses the same delay rather than reading each person's stated return. An SDR covering a prospect on extended leave needs to intervene. Reply also says answering teammates' threads is not enabled by default and requires support activation, something a shared reply desk should resolve during setup. Reply-management limitations.

Deleting a pending draft removes the prospect, and changing settings does not rewrite every running contact. Regenerate or edit when the person is suitable but the message is poor. The setup guide also says relevant Jason settings changes apply only to contacts who have not yet received a step. If a claim in the offer changes after launch, inspect the affected running sequence instead of assuming one edit repairs all future messages. Setup and editing rules.

The trial does not prove the paid channel workflow. Reply advertises a 14-day trial with sequence creation, data, reports and integrations, while its pricing cards reserve LinkedIn and Calls/SMS automation for paid subscriptions. Creating a sequence during evaluation is different from exercising every action it contains. The low-volume Email Volume cards also say “per user” while broader copy promotes unlimited users; establish the seat terms of the selected configuration before a team purchase. Trial and plan wording.

These are reasons to configure the evaluation carefully. If your purchase depends on an unsupported assumption, such as reliable source attribution, date-aware out-of-office resumes or an unattended call conversation, the documented product does not establish that requirement.

Reply.io Review Verdict: Buy for a Process You Can Supervise

Reply.io is a strong shortlist choice for a founder or SDR lead who needs reps to work email, LinkedIn and calls as a connected process. Choose Multichannel at $99 per user/month, or $89 with annual billing, when those channels are part of the work and a person remains responsible for the replies. The lower Email Volume plan loses its price advantage when the relevant channel add-ons are required. Current pricing.

Choose Jason AI SDR only when you can name the recurring work it will take over and the person who will supervise it. Its Starter price of $800/month, or $500/month billed annually, needs a separate case based on actual sourcing, personalization and reply workload. An agent with approval gates is useful; an agent without an owner is an unattended sales process. AI SDR pricing.

Choose Instantly for an email-first setup, and shortlist lemlist alongside Reply for rep-led multichannel work. On Monday, define a narrow audience, write the approved offer, assign the reply owner and walk a representative prospect through every step on the plan you would buy. Commit when the sequence, escalation rules and complete bill match the operation you intend to run.

Frequently Asked Questions

How much does Reply.io cost?

Email Volume starts at $59 per user/month on monthly billing. For email, LinkedIn and calls, Multichannel starts at $99 per user/month. Jason AI SDR Starter starts at $800/month; the lower advertised equivalents require annual billing. Data, validation and infrastructure can add to the total. See the cost section and Reply's live plans.

Is Reply a legit company?

If you mean Reply.io, it publishes a commercial sales engagement product with pricing, support documentation and named integrations. That supports evaluating it as an identifiable vendor; it does not establish a deliverability result or support-resolution standard. This review did not purchase the service or run a support test.

Is review.io trustworthy?

That spelling is different from Reply.io, the sales engagement platform covered here. This review makes no finding about a separate review website. Check the exact domain before using a rating or signing into an account.

Which cold email platform is the best?

Reply.io fits coordinated, rep-led multichannel work and optionally supervised Jason automation. Instantly fits an email-first operation; lemlist is another multichannel candidate. Choose by the paid reply workflow, data requirements and complete operating cost, not a promised response rate.

Is cold email still effective in 2026?

A platform's sending features cannot answer that for your market. Evaluate whether relevant prospects enter qualified conversations and whether those opportunities justify software, data and rep time. This review establishes documented capabilities, not a measured campaign outcome or a universal reply rate.

Is there a free platform to send cold emails?

Reply.io advertises a trial, not a permanent free sending operation in the paid lineup reviewed here. Its free signup language should not be read as unlimited ongoing use. Check which channel actions the trial allows before using it to assess the campaign you intend to buy.

What is the best free email account in 2026?

For this outbound decision, a company-controlled business mailbox is the relevant starting point. Choose it around domain ownership, authentication and the sending system you will use. A free personal inbox and a managed business outreach setup solve different needs; this review does not rank free consumer email accounts.

How to send 1000 cold emails a day?

Plan total daily traffic, including follow-ups, around configured mailbox limits, domain condition and the audience you can serve. Reply offers multiple sending accounts and controlled ramp-up, but unlimited monthly email does not remove daily caps. A volume target alone is not evidence that sending at that level is appropriate. Reply's sending controls.

Is cold emailing illegal?

It depends on the campaign and jurisdiction. In the US, CAN-SPAM covers commercial B2B email and requires accurate sender information and subjects, advertising identification, a postal address and an opt-out process, among other duties. Buying Reply does not establish compliance. Consult the FTC's business guidance and the rules for the markets you contact.

Use the AI Business Workflow Audit Checklist to map the owners, handoffs and recurring costs in your outbound process.