Outcomes and verification

A guide exists to drive one outcome per customer, and Thread is strict about what “done” means. The guide never verifies its own work. An outcome closes exactly one of two ways:

• The read. The guide cites a fresh read from a connected source — your CRM, your project tracker, a named teammate’s sign-off in a connected channel — taken in the same wake it closes in. The receipt (source, reference, value, read-at) is recorded on the close, and the outcome shows as Done — verified against your system of record.
• Your confirmation. When no read tool is attached, the guide cannot close anything on its own. It proposes done, pages you with its evidence, and waits for your one-tap Confirm done on the watch page. The outcome shows as Done — confirmed by you.

Neither the guide’s word nor the customer’s ever closes an outcome. A customer saying “all set!” is a claim — the guide’s habit is to verify it at the source before celebrating, and the log records both the claim and the read.

​

The close mode is never a surprise

Which arm a guide closes on is decided by one fact: whether at least one read tool is attached and connected. The guide page discloses it everywhere it matters:

• After publish, the guide’s status line states it outright — “closes on fresh evidence — reads: HubSpot” or “closes by your tap”.
• Publishing reads back your instructions’ definition of done alongside the attached read tools, so the definition and the evidence bind together in front of you.
• Detaching the last connected read tool asks for an explicit confirmation that names the consequence — the close mode never flips silently.

​

The five-stage funnel

The guide’s Outcomes tab opens with five stage cards, one per stage, always shown. Every stage is a code-observed fact computed from the log — derived, never authored. Nobody edits a customer’s stage, and the guide cannot narrate itself forward. Each customer counts once, at their current stage, so the five cards add up to the guide’s customer count, and each card shows its count and its share of the whole. A line under the cards says so, gives these five definitions, and says how many customers you’ve heard from in all. That number can be higher than the Engaged card, because a customer you’ve heard from who has since moved on to Verifying or Done is counted there. The line above the cards gives the totals: how many customers, how many are verified, and what share have stalled or opted out. Only a close from a fresh read counts as verified; a close you confirmed counts as done, not verified. Below the cards, How it went sums up the conversations: who you’ve heard from and on which channel, what went out by text, email, and call, and the median time to a first reply and to done. When your emails carried the setup link, the Email cell also shows Tapped the setup link as taps over the emails that carried it. Links are never rewritten; only a tap on the setup link is counted, so a cohort whose emails never carried the link shows no such line. Customers from a rehearsal never appear here. Only real customers count.

​

The roster

Below How it went sits the roster, one row per customer:

• Company — the contact’s name, with the company as a subline.
• Stage — their current stage, plus Needs you (the guide paged you) or Paused when it applies, and Ended (you ended the conversation) or Opted out (the customer asked to stop).
• Last heard from them — the customer’s newest word on any channel, with a relative timestamp, or Never.
• Guide’s last action — the most recent thing the guide did, with a relative timestamp.
• In stage — days in the current stage, with a STALL chip at 7 days short of done.
• Blocker — what’s holding the row: Awaiting you, Awaiting approval, No response, or Send blocked.

Filters compose: click a stage card to narrow the roster to that stage, and combine it with the blocker dropdown, the days-in-stage presets (Any / 3+ / 7+), Stalled only, and Opted out. A counter shows how many customers match. Clicking a row opens a read-only drawer with the customer’s facts and the same certified log the watch page renders. To act on a customer, follow the drawer’s Open watch page link to their watch page.

​

Where the evidence lives

Every read the guide takes lands in the watch log as a monospace receipt — source · reference · value · read-at — and the close event cites the specific receipts that satisfied it. When you want to audit a close, the citation is one click away on the close’s own log entry. The stages, the funnel, and the Done labels all derive from those recorded events, so the numbers you report from this tab are backed by receipts, not summaries.

​

Related pages