> By Kris Newlin · Written with [Viktor](https://viktor.com), the AI employee.

## Key Takeaways

- **Slack's own AI got serious this summer.** On [July 29, 2026](https://slack.com/blog/news/slackbot-july-surfaces-slide-creation-code) Slack shipped four Slackbot capabilities: Code Execution in a secure sandbox, Surfaces (live pinned dashboards and reports), Slide Creation, and Image Generation.
- **The connection layer landed earlier.** Slack made [Slackbot's MCP client generally available](https://slack.com/blog/news/slackbots-mcp-client) on June 17, 2026, launching with more than 20 partner apps including Atlassian, Box, Canva, Docusign, Linear, Notion and Zoom.
- **Where Slackbot clearly wins:** nothing to install, nothing to approve, and it is governed by the Slack admin controls your IT team already runs.
- **Where an AI employee wins:** breadth of tools with real read and write access, jobs that run on a schedule without being asked, and the same teammate in Microsoft Teams if half your company is not in Slack.
- **The honest test is not a feature list.** Give both the two most annoying recurring jobs on your team and look at what comes back Friday.

Our head of growth used to keep a Monday ritual: open the ad accounts, open the billing dashboard, open the spreadsheet where last week's plan lived, and reconcile the three by hand before anyone asked. It took most of the morning, and by Wednesday somebody in a meeting still quoted a different number.

That ritual is exactly what both products in this post are aiming at, from two different directions. Slack is pushing its own assistant deeper into the conversation. Viktor is an AI employee you add to that same conversation. If you work in Slack, this comparison decides who does your Monday.

## What is Slackbot in 2026?

Slackbot is Slack's built-in AI, and Slack has been shipping to it in monthly waves. In its own words from the July announcement: "In April, Slackbot learned to act. In May, it learned to see. In June, it learned you and your systems." July was about producing finished work inside the channel rather than sending you somewhere else to make it.

The four July capabilities, taken straight from Slack's announcement:

| Capability | What Slack says it does |
| --- | --- |
| Code Execution | Runs real Python in a secure sandbox and hands you the file back |
| Surfaces | Builds a live, pinned dashboard or report connected to real data, which the channel can sort, comment on and drill into |
| Slide Creation | Turns a brief plus your template into a shareable PowerPoint or Google Slides deck, with a built-in Deck Design skill |
| Image Generation | Mocks up and visualizes what used to need a design request |

Two months earlier Slack made the Slackbot MCP client generally available, which is the piece that lets it reach outside Slack. Slack describes it as connecting any app to Slackbot, launching with 20+ partner apps and rendering their output as interactive Block Kit components inside the thread.

That is a real product, built by the company that owns the surface. Anyone comparing against it should start by saying so.

## What is Viktor?

Viktor is an AI employee you add to your workspace and message like a colleague. He lives in Slack and Microsoft Teams, connects to 3,200+ integrations with real read and write access, and works on a persistent cloud computer, so a job that needs a spreadsheet built, a PDF rendered or a small web app deployed happens in the same thread where you asked.

The mental model is different from an assistant. You do not open Viktor and give him a task, you hire him into the channel and hand him a job description.

```prompt
Every Monday at 8am, pull last week's spend from Google Ads and Meta Ads, reconcile it against the plan tab in our Growth sheet, and post the variance in #growth. Flag anything more than 15% off plan and ask me before changing a single budget.
```

Nobody built a workflow for that. It runs every Monday, and when the format is wrong you correct it in the thread and the correction sticks.

![Two AI helpers in the same Slack channel, doing different jobs](/images/blog/viktor-vs-slackbot/same-channel-different-jobs.webp)

## Where does Slackbot beat an AI employee?

In three places, and they matter.

**Nothing to install and nothing to approve.** Slackbot is already there. No app to add, no security review to schedule, no admin to convince on a Tuesday. For a team that has been stuck waiting on IT for two quarters, that alone can decide it.

**It inherits governance you already run.** Whatever your admins have configured for Slack applies. There is no second set of controls to learn, no separate audit surface, and no new vendor question in your next security review.

**Output that lives in the channel as a first-class object.** Surfaces are Slack building on its own canvas: a pinned, live, sortable thing the whole team can comment on. An app posting a message can attach a file or a link, but it cannot invent a new native object inside Slack. Slack can.

If your requirement is "AI that everyone in the company can use tomorrow with zero rollout", Slack's own AI is the shortest path in the building. Say yes to it.

## Where does an AI employee beat Slackbot?

On the size of the job, and on who owns it afterwards.

**Breadth of real write access.** Slack launched the MCP client with more than 20 partner apps and says more are coming. Viktor connects to 3,200+ integrations today, including the unglamorous ones a back office actually runs on: the billing system, the ad accounts, the ATS, the ticketing tool, the sheet someone made in 2023 that finance still uses. Most recurring work fails on the one tool that is not connected.

**Work that happens without being asked.** An assistant answers when you type. An employee owns a standing job: the Monday reconciliation, the invoice chase, the weekly board digest, the onboarding checklist. That difference shows up not in what gets produced but in what stops being forgotten.

**One teammate across Slack and Microsoft Teams.** Plenty of companies run Slack in product and engineering while sales or the parent company sits in Teams. Slack's AI is Slack's. Viktor is the same teammate in both, with the same skills and the same memory of how your team likes things done.

**Review-first by default.** Viktor drafts and waits. Nothing gets sent, changed or deleted in a connected tool without your yes, which is what makes it safe to connect the systems that scare you.

**Jobs that grow past a single answer.** A request that turns into a 40-page PDF, a cleaned dataset, a deployed dashboard, or a code change on a branch is normal work for a persistent cloud computer with shell access.

## Which one handles the work you actually have?

Named jobs, not categories.

| The job | Slackbot | Viktor |
| --- | --- | --- |
| Summarize what happened in this channel while I was out | Native, instant, no setup | Also works, but this is Slack's home turf |
| Clean a messy CSV somebody dropped in the thread | Code Execution runs Python and returns the file | Same, plus the file can flow into the next step of a standing job |
| Build a live pinned dashboard the channel can sort | Surfaces, a native Slack object | Viktor deploys a live Space and links it in the thread |
| Chase overdue invoices in the billing system every week | Depends on the app being among the MCP partners | Standing job, drafts each chase for approval before sending |
| Update the CRM after a call and post the next step | Depends on your CRM being connected | Read and write across 3,200+ integrations |
| The same teammate for the sales org that lives in Microsoft Teams | Slack only | Slack and Microsoft Teams |
| A recurring process that should improve every time it runs | Skills can be shared across the team | Corrections in the thread [become a reusable skill](https://viktor.com/blog/how-to-turn-a-recurring-task-into-a-shared-skill) |

The pattern is simple. Slackbot is strongest on work that starts and ends inside Slack. An AI employee is strongest on work that starts in Slack and ends in six other systems, on a schedule, with somebody accountable for it.

## Do you have to choose?

No, and most teams should not pretend otherwise.

Slackbot will get used for what it is good at without anyone running a rollout, because it is already sitting in the sidebar. The question worth your time is the second one: which recurring, cross-tool jobs is nobody doing well, and who should own them.

![Decide by the job, not by the feature list](/images/blog/viktor-vs-slackbot/decide-by-the-job.webp)

**Run the two-request test this week.** Take the two jobs your team complains about most, the ones that involve at least two systems outside Slack, and hand them to an AI employee on Monday. On Friday, look at the output, not the demo. Five days of real work tells you more than a quarter of evaluation, and the same test works for [judging any AI teammate that claims to work everywhere](https://viktor.com/blog/how-to-judge-an-ai-teammate-that-works-everywhere).

If your honest answer on Friday is "the summaries were nice but the systems work still landed on Marta", you were never comparing two assistants. You were deciding whether to hire.

## Frequently Asked Questions

### Is Slackbot a competitor to Viktor?

Partly. They overlap on conversational work inside Slack, where Slackbot has the home advantage. They separate on cross-tool execution: Viktor is an AI employee with read and write access across 3,200+ integrations, and he runs standing jobs on a schedule instead of only answering when messaged.

### What did Slack ship for Slackbot in July 2026?

Slack announced four capabilities on July 29, 2026: Code Execution running Python in a secure sandbox, Surfaces as live pinned dashboards and reports, Slide Creation producing PowerPoint or Google Slides from a brief and a template, and Image Generation. The announcement is on Slack's own news blog.

### What is the Slackbot MCP client?

Slack made Slackbot's Model Context Protocol client generally available on June 17, 2026, so Slackbot can connect to outside apps and render their output as interactive components in a thread. Slack launched it with more than 20 partner apps, naming Atlassian, Box, Canva, Docusign, Linear, Notion, Replit, Webflow and Zoom among them.

### Can I use both Slackbot and Viktor in the same workspace?

Yes. They coexist in the same channels, and in practice they split by job shape: quick in-Slack answers and native Slack objects on one side, recurring cross-system work with approvals on the other.

### Does Viktor work if my team is on Microsoft Teams?

Yes. Viktor works in Slack and Microsoft Teams with the same skills and the same context, which matters when different parts of a company standardized on different chat tools. [Where an AI employee lives](https://viktor.com/blog/best-ai-agents-for-slack) drives whether anyone actually uses it.

### How does Viktor keep write access safe?

Review-first by default. Viktor drafts the email, the CRM update or the budget change and waits for your approval in the thread before anything leaves the building. Viktor maintains SOC 2 Type I and is hosted by default.

### What should I not use an AI employee for?

High-volume customer-facing traffic. If you need an agent handling thousands of end-customer sessions a day, that is a different product category. Viktor works with your team, on your team's jobs.

---

**Viktor is an AI employee that lives in Slack and Microsoft Teams, connects to 3,200+ integrations, and does real work for your team.** [Add Viktor to your workspace -- free to start →](https://viktor.com/?utm_source=blog&utm_medium=cta&utm_campaign=viktor-vs-slackbot)