Resident agents for installed bases
Thread puts a resident AI agent on every account you've already sold, to activate the add-on, finish the rollout, complete the onboarding. It texts, emails, and calls with a professional's patience, hands the close to your team when that's what works, and only calls it done when your system of record says so.
Conversation platforms get paid when the chat ends. Thread gets paid when your warehouse says the customer activated.
How it works
You write the outcome in plain language and name the system that proves it. The guide owns the path.
Point a guide at a cohort, 50 accounts or 5,000. Consent attested before the first touch. Each account gets its own resident agent with its own memory.
It texts first. Answers questions from your knowledge base. Nudges. Emails. After a quiet week it calls, or books your closer with the full story. Weeks of patience, not a drip.
On every claim of done, it reads the record, Snowflake, HubSpot, Pendo, Slack. "The customer says it's connected" is a lead, not a close.
The last card fills only on a fresh read of your system. Closes you confirmed by hand are counted apart. Your CFO can audit the difference.
The platform
One system: resident guides on every account, the harness that runs them, and the surfaces your team and your customers see. Your CRM and warehouse stay the source of truth, Thread reads and writes; it doesn't replace.
Long-lived resident agents, one per account, each with its own memory and a single goal: get this account live. Pursued across text, email, and voice for weeks, every answer grounded in your knowledge base.
And when the next step hides inside the customer's own product — a setting to flip, a snippet to place, a screen they've never opened — the guide sends Sidekick, a white-labeled agent that does the clicking for them: it drives the browser while the customer watches, hands control back wherever a login or an approval needs a human, and the step still closes on your system's read, not on the agent's word.
a guide · one account · its memory · text, email, voice · the floor · the close
The same agentic harness turned inward: your back office, for long-horizon automation. When the work sits inside a console you don't own — the storefront, the theme, the settings, most of it with no API — Sidekick, the white-labeled browser leg, clicks through the admin itself, hands control back when someone needs to log in, and takes it again to finish.
The close condition is what the rendered page shows, not that the file was created — and every session is recorded. The flagship run: PayPal Pay Later messaging placed byte-exact in a real Shopify admin, in a draft theme it will not publish, confirmed against the rendered page rather than against its own report.
a runbook · the task · guardrails · skills · the session · the recording · the close
Text, email, and voice are one thread with one memory. The owner replies wherever they actually answer, and the guide follows, nothing re-asked, nothing lost between channels.
Your team supervises from one workspace and steps in only where a human converts better.
A portal under your brand, magic-link, no passwords, where documents land, steps complete, and progress is visible. The guide walks people to it; the record proves they arrived.
The floor
These aren't settings someone remembers to turn on. They're the runtime, enforced in code on every guide, every channel, every wake.
Add your own rules on top. The floor never comes off.
Where guides work
Five installed-base problems, one motion. Find yours.
Thousands of merchants already pay for the module. The guide activates them one at a time, and proves every activation in your warehouse, not in a dashboard of sends.
Every acquisition hands you a book of merchants stalled between signed and transacting. The guide runs the chase per merchant, collect, verify, push, confirm, until the record is in your CRM.
POS migrations, program launches, compliance pushes, every location gets a guide carrying the program to done, with an audit trail your counsel can read.
Activation verified in product telemetry while CSMs judge instead of chase. For operating teams: one playbook, N portcos, metered per verified outcome.
Roughly half the addresses you built past never take the service. One guide per serviceable address, pre-registration to kept install to billing-active, verified against OSS and billing.
Voice, in the same room
Design the voice agent beside the guide: instructions, guardrails, knowledge, a number. Calls follow the same floor, every dial asks a human first, and the call never verifies; only the read does. Try it right now: +1 (669) 348-3154.
A guide at work
Ok I think I connected it just now
Great, give me a second to check the record on our side.
guide · checking before celebrating
Confirmed, it's live. You'll see the first report Monday. Thanks for sticking with the setup.
closed · done · verified
Start here
50–100 of your customers plus a matched holdout, so the lift is real, not vibes.
The guide texts and calls as you, on numbers registered to you, under your consent posture.
The close is a fresh read of your warehouse or CRM. You watch every step live, as it happens.
No platform fee. No setup fee. No implementation project. You pay for activations your own system confirms.
Lift vs. holdout and cost per verified activation, the two numbers a CFO asks for, pre-registered up front.
If the number doesn't move, keep the readout and the audit log. No lock-in, nothing to unwind.
