How does the AI draft actually use account context?
The AI draft panel pulls from the full Strkr account and contact record: enrichment data (contact title, LinkedIn profile summary, company size, industry), deal history (prior deals with this account, won/lost outcomes, prior reps who worked it), conversation history (recent email threads, meeting notes, call summaries), intent signals (which ICP keywords the account recently researched), and technographic data (which vendors the account currently uses). The draft output references specifics the buyer will recognize: "I saw your team just adopted Snowflake alongside your existing Looker setup; typically that pairing surfaces pipeline attribution questions, and I wanted to share how we think about that specifically." Compare to classic AI drafts that generate "I noticed your company and had a thought." The specificity drives reply rate because the buyer sees evidence the sender did the research. Reps review and edit the draft before sending; the AI accelerates the first draft rather than fully automating the send.
How does deliverability monitoring work?
Native mailbox integration (Gmail, Microsoft 365) surfaces deliverability metrics at three levels. First, inbox placement: percentage of sends landing in the primary inbox vs the promotions tab vs the spam folder, measured via seed-list testing across major receiver domains. Second, mailbox health: Gmail reputation score, Outlook sender score, SPF/DKIM/DMARC alignment status, domain age and warming status. Third, send-pattern diagnostics: daily send volume vs mailbox limits, bounce rate trends, complaint rate (recipients marking as spam). The metrics surface on the rep's sequence view with recommended actions when thresholds get breached: "Spam folder rate climbing on Gmail; reduce daily send volume to 100 for 7 days to allow reputation recovery" or "SPF record misaligned; coordinate with IT to fix before continuing cold outbound." The monitoring is proactive rather than retrospective; reps act on the signals before deliverability tanks completely.
What does the reply classification capability do?
AI reply classification analyzes every inbound reply and tags it by intent: interested (reply indicates buyer wants to engage), not interested (polite decline or hard pass), out-of-office (auto-responder or vacation message), forward-to-colleague (reply names a different person to engage), unsubscribe request (opt-out), ambiguous (reply does not fit the above). The classification drives workflow: interested replies land in the rep's priority inbox with a suggested next step, OOO replies auto-snooze the sequence with a resume date, unsubscribe requests add to the suppression list and halt the sequence, forward-to-colleague replies suggest adding the named person as a new contact. The classification accuracy runs 92-96 percent on the common patterns; edge cases (ambiguous "let's circle back next quarter," colleague-forwarding without explicit interest, nuanced responses) misclassify at 4-8 percent. Reps should spot-check the classification queue weekly to catch misclassifications; the ambiguous bucket typically needs manual review.
How does multi-channel orchestration work with LinkedIn?
Multi-channel sequences support email, LinkedIn connection and InMail, and phone call steps in a single orchestrated flow. The LinkedIn integration runs through the LinkedIn Sales Navigator API where available (requires Sales Navigator license on the user's LinkedIn account) and falls back to browser-based execution for connection requests and messages. The sequence steps run with configurable delays (email on day 1, LinkedIn connect on day 3, follow-up email on day 7, LinkedIn message on day 10, call on day 14). The important caveat: LinkedIn's terms of service limit automated connection volume (typically 100-200 connection requests per week per account). Strkr's defaults are conservative to stay within platform policy; teams running aggressive LinkedIn automation risk account restrictions. The practical pattern: use LinkedIn connection and message as a complement to email, not a replacement, and respect the platform volume limits.
How does the compliance surface handle GDPR and CAN-SPAM?
Three compliance capabilities run on every send. First, opt-out management: a unified suppression list across all channels (email, LinkedIn, call) that hard-blocks sends to any contact who requested unsubscribe. The suppression list respects CAN-SPAM, CCPA, state-level opt-outs, and vendor-level opt-outs. Second, GDPR consent: for contacts in EU regions (determined by mailing address or inferred from company HQ), the compliance surface requires documented consent (opted-in to marketing, is an existing customer in the current contract, has a direct business relationship) before sending outbound email. Contacts without documented consent hard-block for cold outbound. Third, audit trail: every send maintains an audit record showing the compliance checks that ran and their outcome. The compliance surface is admin-configurable: specific jurisdictions, specific consent models, specific suppression categories can be tuned to the organization's legal counsel's requirements. Legal reviews the configuration; the system enforces it on every send.
What are the limits of sales email tooling?
Three real limits. First, tooling does not fix a bad message. AI drafts amplify the underlying message strategy. If the value proposition is generic, the buyer persona is wrong, or the point of view is weak, the AI drafts produce more volume of weak messages. Fix the message upstream. Second, tooling does not substitute for ICP work. Sending to non-ICP accounts at scale fails faster. The database and ICP definition work is upstream of the email tooling; teams spraying volume at non-ICP accounts see low reply rates regardless of tooling quality. Third, deliverability depends on sender behavior. The monitoring surfaces signals; the rep still has to act. Teams that treat the monitoring as a passive dashboard without responding (reducing volume, warming domains, improving message quality) see deliverability continue to tank. The tooling is leverage on good fundamentals; it does not create good fundamentals. Teams that understand these limits and build the fundamentals (message, ICP, sender discipline) typically see sales email tooling deliver sustained reply-rate and pipeline gains; teams expecting the tooling to compensate for weak fundamentals see partial returns.