Whether you’re giving advice or exploring a partnership, see the claims behind the request before you decide.
See where a claim comes from.
Room can check public project activity in GitHub. It turns what it finds into specific claims, shared only when the sender approves them.
The logos beside a request show the sender’s connected tools. Each claim names its source and when Room checked it.
StripeGitHub
InboxScore
Channel partner offer89
Request for advice64
Vendor proposal28
Room’s notesReach new customers through a channel partner.
89/100Score
They’re proposing to resell your product to customers in your target market.
Supporting context
40 customers in your industry
HubSpot · Customer records
50% revenue growth last month
Stripe · Revenue records
Proposed checks · not available yet
Illustration: An illustrative inbox has three requests with scores of 89, 64 and 28. A channel partner offer is selected, showing a score of 89 out of 100. The opportunity is to reach new customers through a channel partner proposing to resell your product in your target market. Company statistics appear underneath as supporting context. The score is a ranking, not a probability. Example claims: 40 customers in your industry and 50 percent revenue growth last month. Proposed sources: HubSpot customer records and Stripe revenue records. These checks are not available yet.
What the check means.
A source check shows what a connected tool reported at that time. A confirmation records what someone told Room. A document is material the sender provided. None guarantees a future result.
Room’s notes separate supporting evidence from unanswered questions. You choose whether to accept, ask a question, or decline.
Stripe
GitHub
ChatGPT
Claude
Muse