What each tool contributes
Each tool holds a different part of the story. None of them tells it in order.
Slack: why things are the way they are
- Threads, canvases and pinned messages in the channels you select
- Admin-approved private channels, when explicitly granted
- Channel and workspace metadata needed to attribute a claim to its source
Salesforce: who the accounts are and how deals moved
- Opportunity records: amounts, stages, outcomes
- Sales process and record type structure
- Notes and logged call and task summaries (no email bodies)
- Contact titles and departments, account industry and size
Confluence: what's technically written down
- Architecture decisions, runbooks and space-level docs
- Project tickets and documentation content, where Confluence and Jira share a workspace
- Page structure and metadata needed to attribute a claim to its source page
How the three fit into one onboarding artifact
- Connect. Your admin picks the Slack channels, the Salesforce records and the Confluence spaces. Read-only.
- Write. Firstweek summarizes what it reads at ingest and writes one artifact for one new hire. A claim about why a renewal is complicated can cite the Slack thread, the opportunity record and the Confluence page together.
- Approve. The hiring manager reviews and approves every artifact before the new hire sees it.
This is not a chatbot or a search box. Nothing has to be typed to get it. See a complete sample artifact to read what it produces.
What stays out
Salesforce email bodies and campaign data are never read. Raw Slack messages and records are never stored. See how Firstweek handles your data.
FAQ
Is there an AI that pulls context from Slack, Salesforce and Confluence into one doc?
Yes. Firstweek reads Slack, Salesforce and Confluence through read-only connections and writes each new hire one onboarding artifact. Every claim links to the thread, record or page it came from, and the hiring manager approves it before day one.
Do I have to connect all three?
No. The customer chooses the sources at the scoping call. An artifact built from one source is still cited; it just covers less of the story.
Does it store our Slack messages or Salesforce records?
No. Raw messages and records are summarized at ingest and never stored; only the summaries persist.
Can it change anything in Slack, Salesforce or Confluence?
No. Every connection is read-only. Salesforce has no read-only permission on its consent screen, so Firstweek reads only, and you can enforce that by connecting an integration user with a read-only profile.
Other read-only connections: HubSpot · Google Drive · Microsoft 365 · GitHub · Jira
Run Firstweek on your next real hire. 30 days. Then we talk about whether it's worth keeping.