Where every fellow lives, Teams edition

FellowHire +

FellowHire + Microsoft Teams

Every FellowHire fellow runs in Microsoft Teams. Sales, support, ops, paralegal, EA, and more. Same fellows. Same workflows. Native to your tenant, your channels, and your chats.

What a fellow does in Teams

๐Ÿ’ฌ

Lives in any channel you add them to. @mention them, post in thread, or DM them in chat.

๐Ÿงต

Reads channel and chat context. The fellow understands the conversation before responding, not just the last message.

๐Ÿ”’

Works in 1:1 and group chats for private workflows like CRM updates, calendar holds, or pulling reports.

๐Ÿ“ข

Posts proactive updates. The fellow watches for the things you care about and posts when there is something to flag.

๐Ÿ“Ž

Uses Teams' native features. Channels, chats, mentions, reactions, file shares, and adaptive cards. All supported.

๐Ÿ›ก๏ธ

Respects channel and team boundaries. If you scope a fellow to one team, that is all the fellow sees.

๐Ÿ‘ฅ

Multiple fellows in one tenant. Each fellow has its own app identity, scope, and permissions.

How the install works

1

Install during fellow setup

During your fellow setup call, we install the FellowHire app to your Microsoft 365 tenant. Your tenant admin approves the requested Microsoft Graph permissions. Most installs use admin consent so individual users do not have to approve.

2

We scope teams, channels, and chats

You decide which teams and channels each fellow can read and post in. The fellow only sees what your admin grants. You can change scope at any time from the Microsoft 365 admin center.

3

Fellow joins the channels

Once installed, the fellow shows up as an app in the channels you picked, posts a short intro, and is ready to work. No training period. The fellow already knows your role, your stack, and your team.

Permissions and scopes

FellowHire requests Microsoft Graph permissions scoped to what each fellow needs. Read-only fellows get read-only scopes. Fellows that post and react get matching write scopes. Fellows that handle files get file scopes only when their workflow requires it.

ChannelMessage.Read.Group Read messages in channels the fellow is added to
ChannelMessage.Send Post messages as the fellow
Chat.ReadWrite Participate in 1:1 and group chats with the fellow
Files.Read.All Read files shared in scope, when the fellow's role uses files
User.Read.All See tenant members so the fellow can @mention correctly

Tenant admins can review every requested scope before granting consent. You can revoke or rotate at any time from Azure AD.

What it looks like in your Teams

General ยท Sales
SC

Sarah Chen 9:14 AM

@Casey just got off a discovery call with Acme. They want a follow-up by Friday. $48k ARR.

Casey BOT 9:14 AM

Logged. Acme deal updated to Proposal in Salesforce, ARR $48k. Drafted recap email. Want me to send it?

General ยท Support
M

Marcus 11:02 AM

@Patch ticket 4471 โ€” customer says webhooks stopped firing this morning. Can you check?

Patch BOT 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. Posted in the ticket as a draft.

Chat ยท Hayden
L

Lena 8:47 AM

Hayden, can you find me 30 minutes with Marcus this week? Pre-board call.

Hayden BOT 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.

Compliance and security

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 Microsoft Teams specifically: we install via standard Teams app + Azure AD admin consent. We only access teams, channels, and chats your admin grants scope to. We do not export your Teams history. Your tenant admin can audit every connection, every channel scope, and every fellow at any time. You can revoke the install in one click from the Microsoft 365 admin center or Azure AD.

Every fellow runs in Teams

Same 15 fellows you would get on Slack. All native to Teams.

Casey, the Sales Fellow

Runs your pipeline. Qualifies leads, drafts outreach, updates the CRM, and reports on the pipeline from your Teams.

Quinn, the Paralegal Fellow

Drafts legal documents, logs matter activity, runs intake conversations, and answers questions in your firm's Teams channels.

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 Teams request. Revises in chat.

Hayden, the Executive Assistant Fellow

Manages calendars, books meetings, drafts replies, and triages exec inboxes from chat.

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 project tools, 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 Teams.

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 the product channel.

Ash, the Data Analyst Fellow

Pulls data, runs queries, and drafts data-backed answers to business questions in Teams.

Morgan, the Marketing Fellow

Drafts campaigns, runs SEO research, and reports on traffic and funnel data in the marketing channel.

Don't see your tool? We build it.

FellowHire is not a directory of 3,000 integrations. We build the integrations your fellow needs. Teams 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 cannot connect to it. It means we will scope it during setup. Tell us what you run on. We will make it work.

Tell us your stack โ†’

On Slack instead?

FellowHire fellows run in Slack too. Same fellows, same workflows, same compliance posture. If your team is on Slack, start there.

See FellowHire + Slack โ†’

Bring on a fellow that lives in your Teams.

Tell us about your team and which fellow you need first. We will set up the fellow, install in your tenant, and have it working in about a week.