Use Claude with Thread

What you’ll leave with

A provenance-backed prospect or research brief in the correct tenant.

Why this matters: Teams can use the AI assistant they prefer without losing tenant boundaries, provenance, or human approval.

Confirm connection scopes

Search with your ICP

Review and push only approved work

The workflow

Step 1
Confirm the approved connection
Use the tenant-approved MCP connection and verify the requested scopes before searching.
Step 2
Search with the ICP
Ask Claude for candidates using Thread's governed prospect-search workflow.
Step 3
Select one candidate
Review provenance and explicitly choose the prospect to save; do not bulk-create by default.
Step 4
Push the result into Thread
Save the selected prospect or research result and confirm the audit trace.

Workflow visual

Synthetic reference example

Without Thread

Brightline Manufacturing is a promising account, but the signal is scattered across search tabs, notes, and inbox context.

In Thread

Ask Claude to research Brightline Manufacturing, inspect provenance, and push only the approved result into Thread.

Evidence stays attached

What you leave with

A governed, provenance-backed result in the correct workspace.

Use Claude with Thread workflow for Sales teams. Illustrative synthetic data only. Use the practice lab below with your own account context.

Practice lab

Ask Claude for one target account, inspect the evidence, and decide what should—and should not—be written to Thread.

What evidence makes this worth pursuing?

What is the next human action?