What stayed and what changed
A quick-reference comparison of Dailybot v2 and v3 — what is the same, what evolved, and what is brand new.
Moving to Dailybot v3 does not mean starting over. Most of what your team knows and uses stays the same. This guide maps exactly what carried over, what evolved, and what is entirely new — so you can orient yourself quickly and focus on the features that matter to your team.
What stayed the same
These are the pillars of Dailybot that did not change in v3. If your team is comfortable with these in v2, nothing breaks.
Check-in experience. Team members still receive prompts in their chat platform (Slack, Microsoft Teams, Discord, Google Chat), answer conversationally, and responses are collected centrally. The interaction model is identical.
Chat platform integrations. All supported platforms work the same way. You do not need to reconnect or reconfigure your Slack or Teams integration after upgrading.
Team structure and permissions. Teams, members, roles, and access controls carry over. Your organizational setup is unchanged.
Scheduling. Timezone-aware scheduling, response windows, recurrence patterns, and holiday awareness work the same. Existing schedules continue without adjustment.
Kudos. The kudos system — giving recognition, team values, and leaderboards — works as before with enhanced analytics in the new dashboard.
Check-in history. Every past response, summary, and data point is preserved. Your historical analytics are intact.
What evolved
These features exist in both v2 and v3, but they got significant improvements.
Check-in workflows → Visual workflow builder. The v2 rule-based system for conditions and follow-ups has been replaced with a drag-and-drop visual builder. Same concepts (triggers, conditions, actions), but much easier to create and debug complex chains. Existing rules are auto-converted.
Dashboard. The v3 dashboard is faster, more customizable, and more information-dense. Widgets are configurable — pin your team feed, analytics, or mood tracker to the spots that make sense for your workflow. The old dashboard layout is gone, but all the same data is accessible.
Summaries → Smart summaries. V2 summaries grouped responses by person. V3 smart summaries use AI to extract key themes, surface blockers, and highlight trends across the team. You get a synthesized view, not just a list.
Analytics. V2 analytics were basic counts and charts. V3 adds trend analysis, cross-team comparisons, and drill-down views. Export capabilities are expanded.
Notifications. The notification system is more granular. You can now configure per-event notification channels, set digest schedules for different event types, and route alerts based on team or project context.
What is brand new
These features do not exist in v2 at all. They are the reason to upgrade.
Agent reporting. Coding agents like Cursor, Claude Code, Copilot, Windsurf, and others can now report their work directly into your Dailybot workspace. Agent updates appear alongside human check-ins in a unified feed. This is the foundation of the hybrid team model.
MCP support. Model Context Protocol integration lets coding agents connect to Dailybot natively. Dailybot’s capabilities are also exposed as MCP tools, enabling agents to query team data, submit reports, and trigger workflows programmatically.
Agent heartbeats. For teams running autonomous agents, heartbeats provide periodic health signals. If an agent stops reporting, Dailybot alerts you before the silence becomes a problem. Think of it as uptime monitoring for your AI workforce.
Proactive intelligence. Instead of waiting for you to check the dashboard, Dailybot v3 surfaces insights proactively. If a team member’s check-in sentiment drops three days in a row, you get a nudge. If an agent’s output decreases significantly, you see a flag. The system watches so you do not have to.
Hybrid feeds. A new feed type that merges human and agent updates into a single chronological view. Filter by source type, team, project, or keyword. This is the daily briefing for teams that work alongside AI.
Improved API. The v3 API is more capable with new endpoints for agent management, webhook configuration, and workflow automation. Versioned and fully documented.
Quick comparison table
| Feature | v2 | v3 |
|---|---|---|
| Check-ins in chat | Yes | Yes (same) |
| Slack, Teams, Discord, Google Chat | Yes | Yes (same) |
| Team structure & permissions | Yes | Yes (same) |
| Scheduling with timezone support | Yes | Yes (same) |
| Kudos & recognition | Yes | Yes (enhanced) |
| Workflow automation | Rule-based | Visual builder |
| Summaries | Grouped by person | AI-powered smart summaries |
| Analytics | Basic | Advanced with trends |
| Agent reporting | No | Yes |
| MCP support | No | Yes |
| Agent heartbeats | No | Yes |
| Proactive intelligence | No | Yes |
| Hybrid feeds | No | Yes |
Who needs to do what
Team members — Nothing. The check-in experience in chat is the same. They will notice smarter summaries and may see agent updates in shared feeds, but their workflow does not change.
Managers — Explore the new dashboard and smart summaries. If your team uses coding agents, set up a hybrid feed. Review your converted workflows in the visual builder.
Admins and developers — Update any custom API integrations to v3 endpoints. Test webhook handlers with v3 payloads. Set up agent connections if applicable. See the migration guide for the full checklist.
The upgrade is designed to be additive. Start with what you know, then explore the new features at your own pace.
FAQ
- What features from Dailybot v2 are still the same in v3?
- The core check-in experience, chat platform integrations (Slack, Teams, Discord, Google Chat), team structure and permissions, scheduling with timezone support, kudos, and the response collection flow are all the same. Your team's daily routine does not change.
- What are the biggest new features in Dailybot v3?
- Agent reporting (coding agents report work into your feed), MCP support for tool integrations, agent heartbeats for monitoring autonomous work, proactive intelligence that surfaces insights before you ask, and a visual workflow builder that replaces the old rule system.
- Will my team need retraining for v3?
- For most team members, no. The check-in experience in chat is almost identical. Managers and admins will want to explore the new dashboard and workflow builder, but the learning curve is gentle since the core concepts are familiar.