Where every fellow lives
+
Slack is the front door of FellowHire. Every fellow installs once, lives in your workspace, and works from your channels and DMs. No new app for your team to learn. They're already in the right place.
Your team does not want another tab. They do not want a separate AI dashboard, a Chrome extension, or a 'talk to your assistant' web app.
Slack is where the questions get asked. Slack is where the work gets handed off. Slack is where someone says 'can someone update the deal?' or 'did anyone reply to that ticket?' and a real teammate answers.
FellowHire fellows answer there too. Same channels. Same threads. Same way your team already works.
Lives in any channel you invite them to. DM them, @mention them, or just talk to them in thread.
Reads the channel context. The fellow understands the thread before responding, not just the last message.
Works in DMs for private one-to-one workflows like CRM updates, calendar holds, or pulling reports.
Posts proactive updates. The fellow watches for things you care about and posts when there is something to flag.
Uses Slack's native features. Threads, reactions, files, and Slack canvas — all supported.
Respects channel boundaries. If you set the fellow to only read #sales, that is all the fellow sees.
Multiple fellows in one workspace. Each fellow has its own user, its own scope, and its own permissions.
Install during fellow setup
During your fellow setup call, we install the FellowHire app to your Slack workspace. Workspace admin approves the OAuth scopes. Your team does not have to do anything.
We scope channels and permissions
You decide which channels each fellow can read and post in. The fellow only sees what you grant access to. You can change scope at any time from your Slack admin.
Fellow joins the channels
Once installed, the fellow joins the channels you picked, introduces itself in a short message, and is ready to work. No training period. The fellow already knows your role, your stack, and your team.
FellowHire requests Slack OAuth scopes scoped to what each fellow needs. Read-only fellows get read-only scopes. Fellows that post and react get the matching write scopes. Fellows that handle files get file scopes only when their workflow requires it.
channels:history, groups:history
Read messages in channels the fellow is invited to
chat:write
Post messages as the fellow
reactions:write
Add emoji reactions for status updates
files:read
Read files shared in scope, when the fellow's role uses files
users:read
See workspace members so the fellow can @mention correctly
Workspace admins can review every requested scope before approving install. You can rotate or revoke at any time.
Sarah Chen 9:14 AM
@Casey just got off a discovery call with Acme. They want a follow-up by Friday. $48k ARR.
Casey APP 9:14 AM
Logged. Acme deal updated to Proposal in HubSpot, ARR $48k. Drafted recap email. Want me to send it?
Marcus 11:02 AM
@Patch ticket 4471 — customer says webhooks stopped firing this morning. Can you check?
Patch APP 11:02 AM
Looking. Their account shows webhook deliveries dropped to zero at 7:14 AM PT. Cause: they rotated their signing secret yesterday and didn't update the receiver. I drafted a reply with the fix and a one-line snippet. Posted in the ticket as a draft.
Lena 8:47 AM
Hayden, can you find me 30 minutes with Marcus this week? Pre-board call.
Hayden APP 8:47 AM
Two windows that work for both of you. Wed 2:30-3pm or Thu 10-10:30am. I'll hold both until you pick.
FellowHire is SOC 2 and ISO 27001 compliant. Encrypted in transit (TLS 1.3) and at rest (AES-256). No-training enterprise agreements with OpenAI and Anthropic.
On Slack specifically: we only access channels and DMs you grant scope to. We do not read other channels. We do not export your Slack history. Your workspace admin can audit every connection, every channel scope, and every fellow at any time. You can revoke the install in one click from the Slack app management page.
Slack is the platform. Every fellow we ship runs here. Pick the role and the integration follows.
Casey, the Sales Fellow
Runs your pipeline. Qualifies leads, drafts outreach, updates the CRM, and reports on the pipeline from your Slack.
Quinn, the Paralegal Fellow
Drafts legal documents, logs matter activity, runs intake conversations, and answers questions in your firm's Slack.
Patch, the Support Engineer Fellow
Triages tickets, answers technical questions, and posts incident updates straight into your support channel.
Iris, the Market Researcher Fellow
Runs market scans, drafts research briefs, and answers ad-hoc research questions in thread.
River, the Copywriter Fellow
Drafts blog posts, ad copy, and email copy from a Slack request. Revises in thread.
Hayden, the Executive Assistant Fellow
Manages calendars, books meetings, drafts replies, and triages exec inboxes from DMs.
Kai, the Developer Fellow
Reviews PRs, drafts technical specs, triages bugs, and answers code questions in your dev channel.
Sage, the Customer Success Fellow
Watches account health, flags churn risk, and drafts save plays in your CS channel.
Rowan, the Operations Fellow
Tracks ops projects, updates Notion or Asana, and answers "where are we on X" questions.
Sterling, the Finance Fellow
Reconciles transactions, answers spend questions, and drafts board-level finance summaries.
Avery, the Recruiting Fellow
Screens inbound applicants, drafts outreach to candidates, and updates your ATS from Slack.
Reese, the Account Manager Fellow
Tracks renewals, logs customer touches, and flags expansion signals.
Wren, the Product Manager Fellow
Runs PRD drafts, triages feature requests, and answers roadmap questions in #product.
Ash, the Data Analyst Fellow
Pulls data, runs queries, and drafts data-backed answers to business questions in Slack.
Morgan, the Marketing Fellow
Drafts campaigns, runs SEO research, and reports on traffic and funnel data in #marketing.
FellowHire is not a directory of 3,000 integrations. We build the integrations your fellow needs. Slack is where the fellow lives. The other tools your fellow connects to — your CRM, your support tool, your docs, your ATS — get built into the fellow during setup. If you run on a tool we have not published a page for yet, that does not mean we can't connect to it. It means we'll scope it during setup. Tell us what you run on. We'll make it work.
Tell us your stack →FellowHire fellows run in Microsoft Teams too. Same fellows, same workflows, same compliance posture. If your team is on Teams, start there.
See FellowHire + Microsoft Teams →Tell us about your team and which fellow you need first. We will set up the fellow, install in Slack, and have it working in about a week.