01
Picks up the phone
Its own number plus live voice and video. It joins the Zoom, takes the call, and follows up by SMS — not just Slack threads.
All comparisonsDroid vs Viktor
Two AI employees. One also joins the call.
Of everything here, Viktor is the closest to a droid: it lives in Slack, connects to thousands of tools, runs on a schedule, and ships real deliverables. The honest difference is reach beyond chat — a droid also has a phone number, joins voice and video calls, and talks to your customers, not just your team.
Voice, phone & video calls
Customer-facing channels
Onboard on a call
~3,000 governed apps
The short version
The honest short version.
We'll say it plainly: Viktor is a real AI employee, not a chatbot — it logs into your tools, runs analyses, ships deliverables, and automates recurring work with approvals. On that core, a droid and Viktor look a lot alike. Where a droid goes further is off the keyboard: its own phone number, live voice and video, SMS and email, and customer-facing conversations — and you onboard it by talking it through the job like a new hire. If your work lives entirely in Slack, Viktor is excellent; if it spills onto the phone and out to customers, that's a droid.
Droid
Viktor
Takes real action across ~3,000 apps
Runs unattended on a schedule
Approvals + credential vault
Joins calls — voice, phone & video
Customer-facing phone, SMS & email
Slack & Teams
Onboard by talking, like a hire
message in Slack
At a glance — the full table is just below
Side by side
Droid and Viktor, line by line.
The same job, two tools. Here's how they differ where it actually counts.
| Droid | Viktor | |
|---|---|---|
| What it is | An AI worker you hire for a role — across chat, email, voice and the phone. | An AI employee that lives in Slack/Teams and does real work across your tools. |
| Where it lives | Slack, Teams, email, SMS, voice and a real phone number. | Slack today, Microsoft Teams coming. Text-based, in your team's workspace. |
| Voice, phone & video | Own phone number, live voice calls, and joins Zoom / Meet / Teams with screen-share. | No telephony or meetings — it works in chat threads. |
| App integrations | ~3,000 apps via managed OAuth, with read / write / destructive actions and per-tool policies. | 3,200+ tools via managed OAuth, browser fallback, custom connectors. Genuinely comparable. |
| Executes real work | Writes and runs code, queries apps, ships PDFs / decks / records, opens PRs. | Same idea — a cloud computer that writes code, builds reports, dashboards, even deployed web apps. |
| Scheduled work | Durable scheduled and event-triggered runs, laptop closed. | A 'heartbeat' that runs recurring workflows and proposes automations. Comparable. |
| Customer-facing | Answers the phone, follows up by SMS / email, and joins external calls. | Built for internal team work in Slack, not customer conversations. |
| Onboarding | Hop on a call and brief it like a new hire. | Message it in Slack like a teammate; no call-based onboarding. |
| Approvals & governance | Sensitive actions wait for approval; credentials in a vault the model never sees. | Also approval-gated, OAuth not passwords, per-tool scopes, SOC 2. Comparable. |
| Pricing shape | Workspace credits, shared across the team. | Credit-based too, with free starter credits. Similar shape. |
The difference
What a droid adds.
Not a knock on Viktor — these are the places a droid reaches that a Slack-native employee doesn't.
02
Talks to customers
A droid can run customer-facing conversations across phone, SMS and email, not only internal team chat.
03
Onboards on a call
Brief it out loud like a new hire, screen-share and all — instead of typing instructions into a thread.
04
Lives in more places
Slack, Teams, email, SMS, voice and phone from day one, so the whole company reaches it where they already are.
05
Joins the meeting
Sits in on Zoom / Meet / Teams with screen-share, takes the actions, and writes up what happened.
06
Same governance, wider surface
Approval gates and a credential vault, extended across voice and customer channels — not just app actions.
Credit where it's due
Where Viktor shines.
Real talk — Viktor is the closest thing to a droid on this page, and it's very good at it.
- A true 'do the work' AI employee — it logs into tools and ships output, not just text.
- 3,200+ integrations with managed OAuth, browser fallback, and custom connectors.
- Builds and deploys full web apps — dashboards, internal tools — from a Slack message.
- A 'heartbeat' that proposes useful automations on its own, with approvals and SOC 2.
- If your team lives in Slack, it's a fast, low-friction way to offload real work.
Common questions
The questions we hear most.
Is a droid just Viktor with phone support?
No — but credit where it's due: Viktor and a droid overlap a lot on the core of doing real work across your apps with approvals. The honest difference is surface area. A droid is built around real-world channels — a phone number, live voice and video, SMS and email, and customer-facing conversations — and you onboard it by talking to it like a hire. Viktor is excellent at Slack-native team work; a droid extends that to the phone and beyond.
Which should I pick?
If everything you need happens in Slack and stays internal, Viktor is a strong choice. If the job involves the phone, meetings, or talking to customers — or you'd rather brief an agent on a call than in a thread — that's where a droid fits.
Do both connect to ~3,000 apps?
Yes. Both use managed OAuth across roughly 3,000+ tools with per-tool scopes and approval gates, with browser fallback for apps without APIs. On integration breadth they're genuinely comparable.
Is my data used to train models?
No. Your conversations, files, and integration data aren't used to train shared models. Our providers operate under no-training, zero-retention terms for Droid traffic. See /security for the full posture.
How do I try one?
Start free with starter credits, no card. The quickest way to get going is the way you'd onboard a person — hop on a call and walk a droid through the job.
See what a droid does off the keyboard.
Starter credits, no card. Brief a droid on a call and watch it pick up the phone, work your apps, and follow up — all in one run.