Changelog
Every 11x release, newest first. Feature launches for Alice and Julian, drawn from the 11x Launch Sequence, with links to the relevant documentation.
Every 11x release, newest first. Releases are published as Launch Sequence episodes — each one a single capability shipped to Alice or Julian. Episode 1 is the most recent.
Episode numbering follows the 11x Launch Sequence, where each episode covers one shipped capability. Watch the walkthrough for any release on its Launch Sequence page.
Releases by worker
Alice releases
Live Web Search, Playbooks, Qualification Agent, Custom Deep Research, Smart Email Deliverability, Knowledge Base, ABM Plays, Smart Replies.
Julian releases
Multichannel, Assessments & Smart Outcomes, Connection Boosts, Dynamic Triggers.
Alice Live Web Search
Alice now researches prospects against the live web at the moment of engagement, combined with a database of 400M+ verified B2B contacts. Outreach reflects what is true today rather than what a database cached last quarter.
Why it matters. SDRs spend roughly half their time researching prospects, and much of that research is stale by the time the email sends. Live Web Search removes both the manual research time and the staleness.
Where to configure it: Set up Alice → knowledge base and research · Alice capability reference
Julian Multichannel
Julian now connects text and voice into one continuous conversation. If a call from an unknown number goes unanswered, he follows up by SMS or WhatsApp in the same thread rather than starting over.
Why it matters. Unknown numbers get ignored even when the timing is right. Multichannel means a missed call isn't a lost lead.
Where to configure it: Set up Julian → connect your lead sources · Julian capability reference
Alice Playbooks
Proven sales motions become one-click campaigns. A playbook bundles the target definition, messaging angle, channel mix, and success criteria for a specific play — closed-lost revival, competitive takeout, event follow-up — so the motion is reusable rather than rebuilt each time.
Why it matters. Most GTM teams already know which motions they want to run. Execution is the bottleneck.
Where to configure it: Core concepts → playbooks · Set up Alice → configure a sequence
Julian Assessments & Smart Outcomes
Call-quality evaluation and structured outcome tracking for inbound calls at scale. Every conversation is assessed and every result recorded as a structured outcome, so quality is auditable rather than assumed.
Why it matters. Once inbound calls run at volume, the question stops being whether AI can handle them and becomes whether you can verify what happened on each one.
Where to configure it: Set up Julian → build a call flow · Julian capability reference
Alice Qualification Agent
Leads are filtered in real time against your ICP before outreach begins, so touches are only spent on accounts that actually match your profile.
Why it matters. Outbound volume is no longer the hard part — precision is. Filtering before contact protects both your sending reputation and your reps' time.
Where to configure it: Set up Alice → define your ICP · Core concepts → qualification
Julian Connection Boosts
Phone deliverability for inbound and callback attempts. Connection Boosts manage number reputation so calls actually connect rather than being blocked or labelled as spam by the carrier.
Why it matters. Speed to lead is worthless if the call never goes through.
Where to configure it: Set up Julian → provision phone numbers
Alice Custom Deep Research
Research can now be directed toward the specific context your motion needs, rather than relying on the same surface-level signals for every play.
Why it matters. Most "personalization" is a handful of generic signals on repeat. Custom Deep Research goes deep enough to make a claim the prospect recognises as specific to them.
Where to configure it: Set up Alice → build the knowledge base · Alice capability reference
Alice Smart Email Deliverability
Inbox-placement visibility per mailbox and per domain, with volume paced against sending reputation — reported transparently rather than hidden behind a single aggregate score.
Why it matters. Teams send thousands of emails a month and many never reach an inbox. Without per-mailbox visibility, you can't tell which mailbox is dragging the domain down.
Where to configure it: Set up Alice → authenticate your sending domain · Why emails go to spam
Alice Knowledge Base
Alice absorbs your company's knowledge — positioning, product detail, differentiation, objection handling, proof points — and applies it to personalized outbound, compressing SDR ramp time from months to minutes.
Why it matters. The knowledge base is the highest-leverage input you control. Generic outreach is almost always a thin-knowledge-base problem.
Where to configure it: Set up Alice → build the knowledge base · Core concepts → knowledge base
Julian Dynamic Triggers
Calls can now be triggered, logged, and synced automatically from your CRM or via the API, removing the delay between lead capture and conversation.
Why it matters. If Julian learns about a lead through a delayed sync cycle, nothing downstream recovers the lost time. Triggers connect the event directly.
Where to configure it: Set up Julian → connect your lead sources · Webhooks
Alice ABM Plays
11x is now account-aware. Upload a target account list, sync it from your CRM, or build it with web filters — Alice then finds the contacts within each account, qualifies them, and builds pipeline across the buying committee.
Why it matters. ABM treats the account as the unit of work. Multi-threading a buying committee by hand doesn't scale.
Where to configure it: Set up Alice → define your ICP · Core concepts → playbooks
Analytics
A dashboard that measures pipeline, CRM enrichment, time saved, cost savings, and ROI — rather than activity counts like emails sent and replies received.
Why it matters. Activity metrics tell you a digital worker is running. Pipeline and cost metrics tell you whether it's working.
Where to find it: Set up Alice → review, then launch · Set up Julian → test end to end
Smart Replies
Alice categorizes prospect replies — information requests, product inquiries, meeting requests, objections — drafts a response, escalates when a human is needed, and automates follow-up so conversations keep moving.
You define the handling for each category: respond automatically, skip, or escalate. A testing mode lets you simulate conversations and review drafts before enabling auto-reply.
Why it matters. Plenty of tools help you receive replies. Most still require a human to triage every one, which is where outbound stalls.
Where to configure it: Alice capability reference · Getting started as a User → escalations