fynn
Welcome back
Identity-only sign-in. No workspace-level permissions asked — we just need to know it's you.
Sign in with SlackWorkspace hasn't installed fynn yet? Join the waitlist →
The signals that decide who stays don't show up in your annual engagement survey — they show up between Tuesdays. fynn is a Slack-native people platform that turns weekly check-ins, calendar-aware 1:1 pairings, watercooler threads, channel listening, celebrations grounded in real context, point-in-time surveys, in-person meetups, calendar-aware 1:1 meetings, Slack-native time-off, peer shout-outs, low-friction feedback, and an empathetic Support Desk concierge into leading indicators you can walk into a board meeting with — not another engagement survey to send.
Slack-native, no email
·
Consent-first AI · legal-safe
·
HRIS-sourced, not CSVs
·
/timeoff not Timetastic
·
30-day free trial
Apr 14 – 18, 2026 · 14 teammates replied
Onboarding flow live Tuesday. Three APAC client dashboards rolled out. Timezone-aware scheduler production-tested at 150 people.
Stripe migration waiting on legal (target: early next week). One infra ticket open — owner on leave; backup picks it up tomorrow.
Q3 planning. Two people prototyping an HRIS sync. Genuine interest in an in-person retro surfaced this week.
One click OAuth. No tokens to paste. fynn syncs your full members list automatically on install.
Start a Check-in, a Pairing program, or a Watercooler — each has its own schedule, channel, and audience. Nothing is "global" that doesn't need to be.
Pick the channels worth watching. fynn's daily digests (never quoting verbatim) feed watercooler topic suggestions, engagement profiles, and per-person follow-ups — so every prompt sounds like your team. Admin approves before anything posts.
Twelve pillars, twelve outcomes — each one owned by its own service, its own safety rails, its own metric.
Every check-in is one threaded conversation per teammate — opener, questions, follow-ups, wrap-up — paced by their reply rhythm, not a stopwatch. fynn plans the question order per recipient, opens with continuity from what they said last round, and asks curiosity-first follow-ups that anchor on what the teammate actually said. A Canvas digest lands in the channel you choose, weaving cross-run patterns over the past month — so leadership gets narrative, not a transcript.
When both teammates link Google Calendar or Outlook, fynn finds a mutually-free 30-minute window and drops a Zoom link right into the intro DM. 48h later, a one-tap "did you meet?" — winning starters feed next round's AI, every round shows its met-rate vs an 8-round baseline.
fynn posts the question, then drops its own first reply 60 seconds later to break the silence. Topics come from an admin-approved queue — never surprise output. PACK badges show which prompts pulled replies, reactions, and voices beyond the usual few.
Add the channels worth listening to — or let fynn auto-enroll anything with an eng- prefix (configurable). It builds a compressed daily digest per channel — never quoting anyone verbatim — and proposes typed admin-approved interventions: post a prompt when a channel goes quiet, celebrate a shipped thing, surface a related thread, DM dormant members back in. Nothing posts without one click.
Point-in-time deep dives or weekly pulses on a recurring schedule — multi-question DMs that open as a Slack modal, or single-question polls posted inline. fynn drafts questions from the last fortnight of channel activity (the headline differentiator vs Polly / Viva fynn), drafts the invite copy, clusters free-text answers into themes on close, and scores sentiment per answer. Non-respondents get empathetic, AI-written nudges in the thread of their original DM — cadence scales with window length (1 for a 3-day flash poll, 3 for a 3-week pulse), and each lands the empathy beat first, never "last shot" out of nowhere. Anonymous mode is a real anonymity contract — no timing-attack join, no admin-visible handle.
AI messages grounded in the person's recent channel context — never "happy birthday to an amazing teammate 🎂". Dates come straight from your HRIS (Zoho People today). Optional Suno song on birthdays, optional Leapsome recognition on anniversaries. Festivities sub-feature: a rolling cultural calendar (Diwali, Earth Day, Eid, World Music Day…) that auto-derives region tags from your roster's countries and routes world-days to the right guild channel.
Every #loc-* city channel auto-enrols. Pick a cadence per location (Weekly / Bi-weekly / Monthly / Quarterly), and fynn posts a "let's actually meet" headline with two pre-approved activity ideas (never reusing one within a year) + budget tiers inline. When members start planning, fynn participates — a paraphrased read of the thread + an occasional nudge to converge on a date, capped at 2 chimes per post so it never becomes the loudest voice. Quiet threads get gentle T+2d / T+5d follow-ups; busy ones get left alone.
/timeoff book opens a Slack form. The manager gets an Approve / Decline DM (manager comes from your HRIS — no CSV, no rebuild). Balances, departments, public holidays, half-days, carry-forward all live in fynn. The atomic-conditional update means concurrent admins can't double-decide and the requester gets exactly one decision DM. Migrating off Timetastic? One CLI walks the XLSX and brings 8K+ historical bookings over, idempotent on Booking Id.
Schedule from a Slack mention, see the agenda in the same DM that nudged you in, capture talking points and action items in /me/meetings, and let fynn carry the open items forward to the next session. Admin-curated templates, optional meeting-bot transcript capture, shared + private notes. No separate web app to remember to open.
@fynn shoutout @teammate for X posts to a public channel and a permanent web "polaroid wall". AI coaches the giver toward specifics ("could you mention which value this lived?") — never ghost-writes the message. No leaderboards, no points, no guilt nudges. Recipients can mute a single post without erasing the giver's intent.
Peer-to-peer Invite / Give / Self-reflection in Slack and on /me/feedback — modeled on Know-Your-Team's "helpful interactions" methodology. Feedback content is never exposed to admins. The receiver's Accept / Acknowledge / Discard verdict is never returned to the giver. No per-person watch lists. AI helps compose; it never authors.
Ask in Slack the way you'd ask a colleague. The concierge searches the admin-curated knowledgebase first and answers warmly with sources — about 40–60% of common asks deflect on the spot. If we can't solve it together, the same conversation becomes a real ticket with SLA, assignee, and CSAT. Every admin reply runs through a mandatory concierge polish layer — strict tone-only rewrite, every fact preserved. Confidential tickets DM the HR confidant only; nothing lands in the public support channel.
Each pillar targets a specific culture KPI — and each one gives you data you can walk into a board meeting with. Turn on what you need. Every pillar respects the same hard opt-outs, timezone-aware send windows, and self-service DM commands.
Scheduled async check-ins that surface what your team is actually feeling, every week or fortnight — not quarterly. One threaded conversation per teammate (opener, questions, follow-ups, wrap-up), curiosity-first AI follow-ups that anchor on what the teammate said, and a Canvas digest in the channel your leadership reads. Reply rates 2–3× an engagement-survey email.
Not random names-from-a-hat. fynn scores by shared topics + activity mix, writes a "why you two" brief from both people's engagement profiles, finds a mutually-free time on both calendars, and drops a Zoom link into the intro DM. A 48h follow-up nudge asks "did you meet?" — and every round shows a meet-rate vs baseline, so you can prove the matching is working.
Rotating questions in the channels you pick. fynn posts, then drops its own warm first reply so threads don't die in silence. Topics come from an admin-approved queue — never a surprise post that ends up in a leadership Slack with the subject line "what is this bot doing?". PACK badges show which prompts pulled voices beyond the usual few.
Auto-enroll every eng- (or any prefix you configure) channel into fynn's watch list. A compressed daily digest per channel — paraphrased, never quoted — feeds watercooler suggestions, engagement profiles, and a new admin queue: channel interventions. fynn proposes when to post a prompt, celebrate a shipped thing, nudge dormant members, or surface a related thread. Admin one-click approves; nothing ships without consent.
A multi-question survey opens as a Slack modal; a single-question poll posts inline with vote buttons. Run them once, set a weekly / monthly recurrence and let fynn spawn a fresh instance every cycle, or fire per-user N days after each person's start date — onboarding day-7 / day-30 check-ins that show up on each new hire's individual timeline. A 17-pack best-practice library ships with every workspace — the EX baseline (Onboarding, Offboarding, Manager Effectiveness, Engagement, Comp & Benefits, D&I, Mental Health, L&D, Teamwork, Remote Work, Autonomy & Enablement, Change Management, Hyper Growth) plus a cultural-transformation cluster built for teams shifting how they work (AI-Native Culture, Psychological Safety, Feedback Culture, Innovation & Experimentation, Values in Action, Decision-Making Cadence) and short quick-pulse picks (Weekly Pulse, Recharge Check, Employee NPS). One click clones a pack into a fully editable draft. fynn drafts questions from recent team activity, drafts the invite copy, clusters free-text answers into themes on close, and scores sentiment per response. Choice questions support an "Other" with tell-us-more elaboration; any question can carry a show only if rule that filters analytics to qualifying respondents. Dynamic-cadence in-thread nudges follow up with non-respondents — 1, 2, or 3 nudges scaled to your open→close window — each AI-written to lead with empathy ("totally fair if your week's been packed") and never repeat the same beat; clicking Not right now stops further nudges for that recipient. Anonymous mode is a three-layer contract: nullable user FK + jittered submit timestamps + reflection-asserted no-join model boundary. Anonymous channel polls are vote-once via a hashed Slack-ID gate — no admin can correlate handles, and a motivated voter can't stuff the count. CSV export respects anonymity — respondent columns are omitted entirely, not blanked.
The cheapest retention lever you have is making someone feel seen on their day. fynn pulls dates straight from your HRIS (Zoho People today, BambooHR / Workday / Rippling next) via direct OAuth — no CSV you have to keep uploading, no birthday that gets missed because someone left your roster spreadsheet stale. The AI reads the last three weeks of channel context so each message names something real the person shipped or shared. Never "happy birthday to an amazing teammate 🎂".
Optional amplifiers: Suno generates a custom birthday song from the same context; Leapsome receives the anniversary as a public praise post on their feed. Both degrade gracefully. Opt-outable per person via one Slack DM — so consent is never a question legal has to ask.
Festivities — a rolling cultural calendar alongside. fynn auto-derives your region set from the team's timezones (HRIS country when available), proposes a 90-day festivity calendar (Diwali + Ambedkar Jayanti on the same day, Earth Day, World Music Day, Lunar NY…), and routes world-days to the right guild channel. Fixed-date festivities auto-materialize yearly; variable-date ones (lunar, Islamic, ecclesiastical) nudge you via DM and an in-app strip on the calendar page. No template voice. No default-privileging language. No politics.
Every #loc-* city channel auto-enrols overnight. Admins set a per-location cadence (Off / Weekly / Bi-weekly / Monthly / Quarterly), pick a day + tenant-local hour, and approve activity ideas into a queue. On the chosen minute, fynn posts the headline: "Let's get the Bangalore crew together IRL" with two activities pulled by a least-recently-picked rotation (with a 1-year freshness floor — no idea repeats within a year) and the explicit framing "pick one, tweak it, or do your own thing — the point is that y'all actually meet". Budget tiers are inline; 👋 / 💡 reactions are seeded.
Then fynn doesn't disappear. Three engagement modes share one thread: the headline opens it; scheduled follow-ups at T+2d and T+5d gently re-engage quiet threads (skip-if-engaged the moment any non-bot reply or ≥3 distinct reactors land); and proactive thread chimes fire when members are planning. fynn reads a paraphrased thread snapshot (never quoted, never named) and adds one useful nudge — "sounds like Friday lunch is the lean — anyone close want to scout a spot?" — capped at 2 chimes per post with a 12-hour cooldown. Hard rules: never tag anyone, never promise logistics, never quote a member. The post auto-closes at T+7d so the next cycle gets fresh ideas.
Need a post right now? "Suggest a meet-up now" on the location's edit page fires the same flow — rate-limited 1/15min per location. Disable the cadence entirely by setting Cadence to Off; pillar-disable Meetups in Setup to turn it off across all hubs. When your activity queue depletes under the 1-year floor, the edit page shows a 🪫 banner before the next cron tick — so the channel never goes silent on you by surprise.
Time off is your most-touched HR workflow. Every separate-login leave tool taxes your team a little more on the days they most need flow. fynn keeps the whole thing in Slack: /timeoff book opens a form, the manager gets a single Approve / Decline DM (no inbox, no portal), and the requester sees one decision DM with the outcome and any optional reason. Manager hierarchy comes from your HRIS — Zoho People today, BambooHR / Workday / Rippling next — so onboarding doesn't require a CSV upload to know who reports to whom. Per-user manager_locked + department_locked flags shield admin overrides from the next sync.
fynn owns balances. Admin sets per-leave-type defaults; per-user × per-type × per-year overrides handle the unusual cases. Half-day support (AM / PM / full); carry-forward with a configurable cap; per-country public holidays (IN / US / GB bundled — admins can extend); five-tab read-only Filament view of every request (Pending / Approved / Declined / Cancelled / Upcoming) so HR has the audit trail without needing the approver console. Filament has no Approve / Decline button — that's the point. Decisions happen where the manager already lives.
A daily "who's off today" channel digest lands at your configured hour, zero-noise when no one's off. AI-generated headline (fynn's house voice) above a deterministic list — the list is the source of truth, the headline is tone. Monthly burnout-recharge nudges DM teammates with no booked leave in 90+ days, with hard rails in the prompt: never imply underperformance, never compare to others. Triple-gated against duplicates: per-user opt-out + 90-day analytics-event dedup + cache mutex.
Migrating off Timetastic? One CLI command walks your full XLSX export — 11+ departments, every user's per-year allowance, 8K+ historical bookings, every approver — and lands the lot idempotent on Timetastic's stable Booking Id. The 1,952 half-day rows in a typical export get correctly inferred from the time-of-day column. Re-runs against an updated export are no-ops modulo any rows whose status changed.
Opt out of recharge nudges via pause timeoff nudges. Approval DMs are not opt-outable — they're the workflow itself, not automation.
How is this different from the engagement survey we already run?
Surveys produce lagging indicators — you find out someone's disengaged after they've decided to leave. fynn produces leading indicators: weekly reply cadence, Pairing meet-rate, Watercooler participation by cohort, dormancy signals. It complements an annual eNPS — it doesn't replace your analytics tool. And people reply because fynn's follow-ups read like a colleague, not a form.
We tried Donut and it fizzled. Why would this be different?
Three reasons teams tell us Donut fades: random pairings that don't land, intros that never turn into a meeting, and celebration posts that feel corporate. fynn matches on shared topics learned from your channels (not a shuffle), drops a calendar-aware slot picker into the intro DM so meetings actually happen, and pulls celebration dates from your HRIS so birthdays are never missed. Every round is measured — you see the meet-rate vs baseline, not a vanity chart.
What's the board-level story I can walk into a QBR with?
"Check-in reply rate is X% across teams, ±Y pts versus last quarter. Pairing meet-rate is landing above baseline in Eng and Sales, below in Ops — here's what we're tuning. Z people re-engaged from dormancy after a thoughtful nudge. Celebrations posted N birthdays + M anniversaries, with Leapsome-amplified recognition." One dashboard, one row per pillar, green/yellow/red.
Does fynn ever post something I'd need to apologize for?
No AI output goes to a public channel without admin approval. Watercooler topics land in a review queue first. Celebrations inherit your brand voice and a hard-coded never-discuss list (health, family, finances, religion, politics, performance, mental health, trending crises). If the AI's first draft is off, an admin edits before posting — it's not a "send and hope" system.
What's the consent and legal posture for AI on employee data?
Consent-first. Every teammate has hard opt-outs reachable by one Slack DM (pause, celebrations off, delete my profile) that bypass the AI entirely — the service code checks flags before spending a single token. AI calls happen under Anthropic's zero-retention commercial terms; no employee data trains external models. Full detail on the Privacy page — GDPR, UK GDPR, DPDP (India), CCPA/CPRA all covered. We'll send your DPO the DPA.
How do we roll this out without it feeling like surveillance?
Pilot, don't broadcast. Start with Watercoolers in one channel + one volunteer cohort for Pairings. Announce what fynn does + doesn't do, point people at show my profile + delete my profile the day you turn it on. Every subsequent pillar is a separate decision. Default tone is warm + specific; never corporate. Most teams we work with hit steady-state adoption in about 6 weeks.
What integrations matter for a CHRO deploying this?
Native Slack (no email). Direct-API HRIS sync for birthdays + anniversaries + titles + departments + reporting manager (Zoho People today; BambooHR / Workday / Rippling pluggable next — we'll prioritize yours). Google Calendar / Outlook for Pairings scheduling. Zoom for meeting links. Optional Leapsome integration so anniversary recognition amplifies to the same feed your team already uses. Timeoff ships with a Timetastic XLSX importer so you can decommission a paid tool the same week you switch on fynn.
We're on Timetastic / BambooHR / Workday for time off. What changes?
fynn's Timeoff is Slack-native — managers approve in DM, employees never log into fynn. The Timetastic XLSX importer migrates 8K+ historical bookings idempotent on Booking Id, brings every user's per-year allowance over, and resolves the approver hierarchy in a two-pass walk. For BambooHR / Workday / Rippling we read manager + department from the same HRIS connector that already feeds Celebrations — no parallel auth flow. fynn owns balances; we don't write back to your HRIS's leave module.
Who owns fynn day-to-day?
People Ops runs it from a single Filament dashboard. Engineering owns the Slack app install + HRIS OAuth setup (30 minutes once). Admins approve AI topics, review engagement signals, act on the dormant-users widget. No ticket-to-engineering required to tune anything that isn't a code change.
30 days, every feature, unlimited users, no card required. Pick one channel and one pilot cohort — you'll know by week three whether it's landing. Legal gets the DPA; your DPO gets real answers.
Donut is a solid product. Here's where fynn is different — and where we're not.
Comparison reflects fynn features that are live in the codebase today. Donut rows reflect their published documentation at the time of writing. We'll update this as either product changes.