IntegrationsCopy link to this section

A sales conversation is only useful if what happened reaches the person who follows up. Site → Integrations is where you decide where eligible recaps go.

Two summaries are prepared for an eligible session: an internal one for your team and a warmer one for the prospect. Prospect delivery is held if that copy looks like internal sales language. When no final transcript is available, the internal channels can fall back to the agent's end-of-session summary; Floe does not substitute internal copy into a prospect email.

Notification channelsCopy link to this section

Four channels, each an independent switch:

Prospect recap emailCopy link to this section

Sent only when the session has a current source-bound email claim and prospect recaps are enabled for the site and deployment. The delivery is persisted before sending and can be retried after a temporary delivery failure without copying the raw address into durable retry state. It contains a short summary of the conversation, up to seven features the agent actually showed them, and up to three of their own questions quoted back.

It carries your branding: your site logo (falling back to your favicon) and your accent colour. The footer reads "Powered by Floe".

The call to action adapts to how the session ended — a trial invite, an offer to bring in their team, a deeper walkthrough, or a plain follow-up. When you have configured a booking URL, the email includes Schedule a follow-up. Every claim-backed recap also includes a Not you? link.

What the recap actions do

Both actions carry an opaque capability in the URL fragment. A browser does not send that fragment in the initial request, and Floe removes it from the address bar before validation, analytics, or other SDK startup requests.

• Schedule a follow-up reveals the configured HTTPS scheduling destination only after the action is redeemed. If the link returns to the same consented browser source that supplied the address, that exact claim becomes Confirmed. Opening it on another browser or device can still continue to scheduling, but it does not confirm the claim, join the two browser histories, or create a person merge.
• Not you? opens a Floe confirmation page. Merely opening the page changes nothing; the recipient must choose Confirm this was not me. That marks the source claim rejected and prevents it from authorizing later contact. It does not recall an email already delivered or reverse a CRM write that already completed.

When Floe cannot safely return a Schedule action to the original customer page, it uses a Floe-hosted page with an explicit Continue to scheduling button. The hosted page is also inert until that button is selected.

AE recap emailCopy link to this section

Sent to a single address you configure. This is the internal version. It arrives under the same sender name as the prospect recap — your product name — but the body is deliberately Floe-attributed, so an AE can never mistake it for something forwardable.

It contains the prospect's identity and role, session duration, the internal summary, an intent chip, and the structured read on the conversation: buying signals, features shown, questions asked, tech stack, pain points, capability gaps, objections, and what they said they were interested in. Each list is capped at six items. It deep-links to the full session in the dashboard.

AE email, Slack, and Teams label the source as Confirmed contact, Unverified email claim, or Anonymous lead. These labels are evidence for the person following up; they do not themselves grant permission to create or update a CRM contact.

Slack and Microsoft TeamsCopy link to this section

Paste an incoming webhook and turn the channel on.

• Slack — must be a https://hooks.slack.com/services/... URL.
• Teams — must be a *.webhook.office.com or *.logic.azure.com URL. Create one via the Workflows app in Teams: Post to a channel when a webhook request is received.

Those host restrictions are enforced, not advisory. Recaps contain prospect details, so Floe will only post them to the two providers it can verify.

Testing a channelCopy link to this section

Each channel has a Test send button that runs the real notifier against a sample session, so you can see the actual formatting before a prospect does.

Two things that trip people up:

• Save webhooks first. Slack and Teams tests always use the saved webhook. Paste a new URL, hit Test without saving, and the test goes to the previously saved destination — or errors if there wasn't one. The email channels are different: type an inbox next to the button and you can preview without saving.
• The prospect test needs an address to deliver to — pass your own inbox.

Booking linkCopy link to this section

Set Booking URL to an https:// scheduling link. HTTP URLs are rejected. It becomes the call to action in the prospect recap email, the follow-up button in the internal channels, and the destination the agents offer when a visitor asks to talk to someone. A per-prospect Demo Link booking override must also use HTTPS.

Floe uses the URL you configured and does not append the prospect's name, email, company, visitor token, or claim capability as scheduling-provider query parameters. Do not place identity-prefill keys such as email, name, company, or visitor_token in the configured URL: a claim-backed recap will not reveal a destination carrying them. Benign provider parameters can remain. Leave the setting blank to omit booking controls; the recap's Not you? action remains available when a claim-backed prospect email is sent.

Sender identityCopy link to this section

Recap emails always send from Floe's verified sending address, with your product name as the display name. Sending from your own domain isn't supported yet. You can set a Reply-To address you own, so a prospect who hits Reply reaches your team.

CRMCopy link to this section

Floe can write demo recaps into HubSpot or Salesforce.

You connect a CRM from Site → Integrations with the Connect button, which runs an OAuth flow. The provider apps are not yet live in production, so Connect currently fails with "Couldn't start the connect flow" — talk to us and we'll enable it for your account. Once connected, the integration writes:

Floe finds or creates a contact by email only after the exact source claim has been confirmed. An address that is merely claimed, an anonymous lead, or a display label cannot authorize a contact mutation. Floe rechecks the claim and its retention state immediately before each provider write. If the recipient confirms later by scheduling from the same consented source, a durable CRM-only delivery releases then; Floe does not resend the AE, Slack, Teams, or prospect recap. Retries for the same session and CRM capability are duplicate-safe. If Floe cannot determine whether a provider accepted a write, it holds that capability for reconciliation instead of risking a duplicate CRM activity.

HubSpot contacts get name, company and job title; Salesforce contacts get name and job title only. Floe never creates a Salesforce Account, so a contact Floe created has no account to attach an Opportunity to.

The portable CRM artifact is a source-aware agent-qualified lead (AQL) card in the HubSpot Note or Salesforce Task. When the session supplied them, it includes:

• Demo versus Website Agent source, including whether a Website Agent session remained Q&A-only
• Conversation summary, buying and intent signals, and products or features of interest
• Questions, pain points, objections, capability gaps, and relevant tech stack
• Budget and qualification answers
• Lead score or tier and the recommended next step
• Identity assurance and a link to the Floe session

The same values can also be written to customer-provisioned custom contact fields when Floe has configured a field mapping for that integration. There is not yet a dashboard field-mapping UI; without a mapping, the readable Note or Task still contains the information.

Deal creation is off by default on purpose: if you already sync your scheduling tool to your CRM, that tool usually creates the deal, and turning both on gives you two. Its stage and amount depend on the integration configuration available for your deployment; there is no customer dashboard for those mappings yet.

What triggers a recapCopy link to this section

A completed Demo Agent session is eligible for the configured fan-out. A Website Agent session is eligible when it reaches a terminal state — completed or abandoned — and this exact interaction has either an active email claim or concrete qualification or intent evidence. A name, page view, or generic Q&A alone does not manufacture a lead or trigger sales traffic.

A late transcript or qualification signal can make the session eligible without duplicating human-facing recaps. A later same-source email confirmation releases only the confirmed-contact CRM write described above.

FAQCopy link to this section

Can I change what the prospect email says? Not the copy. You control your logo, accent colour, product name, and booking URL; the structure and the summary are generated per session.

Can I send to more than one AE? Not today — the AE recap takes a single address. A shared inbox or a distribution list is the usual workaround, or use the Slack channel instead.

Do I need a CRM for any of this to work? No. Email, Slack and Teams are independent of the CRM integration.

Which other CRMs are supported? HubSpot and Salesforce. Nothing else today.