What We Shipped in Q1 2026
Q1 was focused on three things: making flow building faster, giving teams better visibility into what's working, and tightening the Slack integration so completion tracking doesn't require switching contexts. Here's a detailed look at each.
Flow Builder: Drag-and-Drop Redesign
The biggest change this quarter was a full redesign of the flow building experience. The old builder was functional — you could create branching flows, attach voice segments, add checkpoints — but the sequence management was clunky. Moving a step from position 3 to position 7 required a drag across a long vertical list, and reorganizing a 12-step flow often felt like moving furniture.
The new flow builder uses a card-based canvas with true drag-and-drop reordering. Each step is a card. Cards can be moved anywhere on the canvas; connectors update automatically. Branching now shows visually: when you add a conditional branch at step 4, the canvas splits into two parallel paths and shows both tracks simultaneously. You can see the whole flow at once instead of scrolling through a linear list.
A few specific changes that came directly from user feedback:
Multi-step undo. Previously, the undo function in the flow builder was single-step — you could reverse one action. The new builder maintains a 20-step undo history, so you can experiment with restructuring without fear of losing work.
Step duplication. If you're building a flow where several steps have similar structure — same prompt format, same response options, just different content — you can now duplicate any step and edit the copy. This cut the time to build a 10-step branching flow from roughly 25 minutes (based on internal timing during user research sessions) to around 12 minutes for flows with repeating structure.
Template library at flow creation. When you start a new flow, you can now choose from a set of starting templates: New Hire Orientation, Tool Setup Walkthrough, Benefits Enrollment, Customer Product Tour, Policy Refresh, and Custom (blank). The templates pre-populate the step structure and checkpoint types that match the use case, so you're filling in content rather than designing structure from scratch for common scenarios.
Analytics Dashboard: Team-Level Visibility
The analytics update adds a layer above the per-flow metrics that existed before. Previously, you could see completion data for each individual flow — how many people started it, how many finished, where drop-off happened. What you couldn't see was a team-level view: how is the Q4 new hire cohort progressing across all their assigned flows collectively? Which manager's team has the highest completion rates? Which role has the most step-three drop-offs?
The new Analytics Dashboard is built around three views:
Cohort view: Groups learners by any dimension you can filter — department, manager, start date, role, or any custom tag. Shows aggregate completion rates, average time-to-complete, and checkpoint pass rates across the cohort's assigned flows. The cohort view is where an HR lead can see, in one place, that the engineering cohort starting in January is at 85% completion across their week-one flows, while the sales cohort starting the same week is at 52%.
Flow health view: Shows all your active flows ranked by completion rate and drop-off concentration. Flows with high drop-off at a specific step are flagged automatically with a "needs attention" indicator. The goal is to make it obvious which flows need a re-record rather than requiring the admin to manually audit each flow's per-step metrics monthly.
Individual progress view: Available to managers and HR admins with appropriate permissions. Shows each learner's completion status across their assigned flow sequence, with timestamps. This is the view managers can open before a day-5 check-in to see exactly where their new hire is in the onboarding sequence — useful as a conversation starter and as a signal of whether something is blocking progress.
The Analytics Dashboard is available on Growth and Team plans. Starter plan retains the per-flow completion count view that existed before.
Slack Integration: Completion Notifications and Direct Flow Launch
The Slack integration existed before this quarter, but it was limited to a single notification: when a flow was assigned to you, you got a Slack DM with a link. That was the full integration.
The Q1 update deepens this in two directions: notifications for managers, and the ability to start a flow directly from a Slack message without navigating to the Cor web app.
Manager completion notifications. When a new hire completes a flow, their manager can now receive a Slack notification. This is opt-in at the workspace level (turned off by default — we wanted to avoid notification fatigue for managers who aren't using Cor actively). When enabled, the message reads: "[Learner name] completed [Flow name] — step 4 checkpoint: answered correctly." It's low-noise and gives the manager a natural opening for follow-up.
Reminder nudges in Slack. For flows assigned but not started within 24 hours of the assigned window, Cor can send a reminder DM from the Cor bot. The reminder message includes the expected completion time ("3 minutes") and a direct button to launch the flow. The intent is to reduce the friction of "I need to find the link again" as a reason for non-completion.
Flow launch from Slack. Using the Slack action menu (the three-dot menu on any Slack message), team members can now search and launch any Cor flow they have access to without leaving Slack. For flows that don't require screen sharing — knowledge walkthroughs, policy reminders, quick process refreshers — this makes Cor accessible in the tool where most teams already spend their day.
Smaller Improvements Worth Noting
A few smaller items from Q1 that didn't make the feature headline but have had consistent positive feedback:
Mobile audio recording. Voice capture from a mobile browser now works on iOS Safari and Android Chrome. Previously it was desktop-only. This matters for operations teams and field teams building flows for distributed workforces where the flow author doesn't always have a desktop.
Flow expiry settings. Admins can now set an expiry date on any flow — after which assigned learners see a message indicating the flow is being updated and will be available again shortly. This is a simple but practical mechanism for managing content that needs periodic refresh (quarterly policy reminders, product update walkthroughs) without leaving outdated content active in learners' queues.
Custom completion messages. The final screen of any flow can now be customized with a message from the flow author. Previously it was a generic "Flow complete — great job!" The new default prompts for a custom message during flow creation. This small change significantly improves the handoff quality between completing a flow and taking the next action — a good completion message can say "You're all set to attend tomorrow's team kickoff. Bring any questions that came up during this walkthrough."
What's Coming in Q2
A few things we're actively building toward for the April-June window, shared here with the caveat that timelines are best estimates and can shift:
SSO / SAML support. Currently available as a Team plan item planned for Q3 2026, but based on inbound from a cohort of growing customers with SSO requirements, we've pulled this forward in the roadmap. We're targeting a beta for Team plan accounts in May, full release in June. SAML 2.0 compliance, with Okta and Azure AD as the primary tested identity providers.
Cohort scheduling. The ability to schedule a full set of flows to be delivered to a defined cohort on a defined start date — without manually assigning each flow. HR teams hiring in monthly cohorts have been requesting this since launch. You'll be able to create a "January cohort" package, set a start date, and have flows delivered automatically in sequence.
Checkpoint question library. A shared library of knowledge-check question templates organized by use case — tool setup, policy review, process confirmation — so flow authors don't have to write checkpoint questions from scratch. Community-submitted templates alongside our own curated set.
As always, if a specific integration or feature is blocking your team's ability to use Cor the way you need to, the fastest path to influencing the roadmap is telling us directly — [email protected] gets to the team, not a ticket queue.