Floe for Microsoft Teams.
Floe posts a recap of every qualifying demo and website conversation to a Microsoft Teams channel: who the lead is, their score, what they wanted, and their earlier visits.
Works with: Website agent, Demo agent.
Last updated
What does Floe post to Teams?
A card per lead.
Each qualifying conversation arrives as a card in your channel, marked as a demo or a website conversation.
What your team needs to act.
The lead, how far to trust their contact details, their score, intent and a summary.
The history behind them.
A returning lead's earlier conversations, and with visitor analytics on, their visits and the pages they read.
What lands in Teams?
A finished demo, or a website conversation that produced an email, a phone number or real buying intent. A page view or a generic question on its own sends nothing.
- One card per qualifying conversation, in the channel behind your webhook.
- The lead, their contact details and how far to trust them.
- The lead score, intent and a summary of the conversation.
- A returning lead's earlier conversations.
What's on a Teams card?
Most parts show only when the conversation produced them.
| Part | What it shows |
|---|---|
| Title | Demo recap or Website conversation, with your product's name. A lead who came back is marked as returning. |
| The lead | Their name, role and company. |
| How to reach them | Their email as a link to write to them, and their phone as a link to call, each labelled with how far to trust it. |
| Duration and intent | How long the conversation lasted, and the next step they're ready for. |
| Lead score | The score and why. For a returning lead, it also shows their previous score. |
| Not a fit | A line saying so, when they asked for something your product doesn't do. |
| Summary | What the conversation covered, in a paragraph. |
| History | Their most recent earlier conversations, each linked, and with visitor analytics on, their visits and the pages they read most. |
| From the conversation | The first few of their buying signals, the features shown, their questions, tech stack, pain points, capability gaps, objections and what they were interested in. |
| Button | Open in dashboard, for the whole conversation in Floe. |
How do you connect Microsoft Teams?
Create a webhook in Teams.
In Teams, use the Workflows app's "Post to a channel when a webhook request is received" to create a webhook.
Paste it into Floe.
Paste it into the Microsoft Teams card on Site → Integrations, turn it on and save.
Send a test.
Send a sample recap to check the channel.
What applies.
Same detail as Slack.
Teams recaps carry the same labels, history and pages as Slack recaps.
You can check each post.
If the webhook stops accepting messages, the delivery shows as failed in Floe's delivery log.
Save, then test.
The sample recap goes to the saved webhook, so save a new address before you test it.
A channel per site.
Each site has its own webhook, so different products can post to different channels.
Alongside Slack, or instead.
Teams and Slack are separate. Use either one, or both, and each gets its own post.
Internal only.
The card is for your team. The prospect never sees it, and it carries no booking link.
Who connects it.
Owners and admins add the webhook from the dashboard.
Questions. Ask Floe.
Do we install a Teams app?
Can recaps go to any webhook?
Can we see the format first?
Do we need a CRM as well?
Who can see the cards?
Works with the rest of your stack.
CRM
HubSpot
Qualifying conversations as notes on the prospect's contact, with an optional deal.
CRM
Salesforce
Qualifying conversations as tasks on the prospect's contact, with an optional opportunity.
Team alerts
Slack
A recap of every qualifying conversation in the channel you choose.
Booking
Calendly and Cal.com
Your Calendly or Cal.com page, opened inside the conversation.
Analytics
Factors
Agent conversations and demos as events in your Factors account.
Support hand-off
Periskope
WhatsApp tickets for your team when a support user needs a person.
AI tools
AI tools (MCP)
Ask Claude, ChatGPT or Cursor about your demos and edit your agent.