Arlo vs Viktor — which AI coworker fits your team?

Viktor and Arlo are the two products most likely to be on the same shortlist: both are AI coworkers you talk to in your team's chat, both connect to thousands of tools, and both promise finished work rather than just answers. The overlap is real, so this comparison focuses on where they genuinely differ — channels, governance defaults, and the kind of work each is best at.

Viktor, made by a fast-moving team that raised a reported $75M round in May 2026, positions itself as an "AI employee" for Slack and Microsoft Teams. Arlo is an AI colleague for the workspace that works across iMessage and SMS, Slack, Microsoft Teams, and live phone calls. If your team's work stays inside Slack, both deserve a look. If it spills into text threads and phone calls — or if approval-first governance is a requirement — the comparison tilts.

What Viktor is (as of July 2026)

As of July 2026, from Viktor's public materials:

• It's an autonomous AI employee that lives in Slack or Microsoft Teams — teammates @mention it in channels and it carries tasks to completion.
• It connects to 3,200+ tools and handles analytics, automation, reports, and campaigns.
• It writes and executes code, and can build small web apps and artifacts on request.
• It's SOC 2 Type 1 certified, with controls over which tools require approval before executing.
• It publishes an unusually deep content library and case studies — the team ships fast and says so publicly.

Viktor is a polished product with serious momentum, and for teams that want to delegate technical, in-chat work at volume, it's a genuinely strong option. Details shift quickly — check Viktor's own site for the current state.

What Arlo is

Arlo is one AI colleague for the whole workspace. It works in the channels your team already uses — including the two most companies ignore: text messages and live phone calls. You can text Arlo from iMessage or SMS like a person, and it can place and take real calls — confirm an appointment, chase a vendor, field an inbound question — then summarize the call and update your records.

It connects to Slack, Gmail, Notion, Linear, GitHub, and 3,000+ other tools, and for software with no API it logs in once through a secure browser session and works the interface like a person would. It keeps persistent memory across conversations and channels, delivers one morning briefing of what changed overnight, and suggests automations for work it sees repeating.

Governance is the center of the product, not a setting to find later. Every connection resolves through policy before each run, sends and writes wait on a reviewer you pick, and every run leaves a full audit trail — each tool call, source, and approval.

Feature comparison

Capability	Viktor	Arlo
Category	AI employee for team chat	AI colleague for the workspace
Slack	✓	✓
Microsoft Teams	✓	✓
iMessage / SMS	—	✓
Live phone calls (in + out)	—	✓
Tool integrations	3,200+	3,000+
Tools with no API	Not a stated focus	✓ Secure browser session
Writes and executes code	✓	Not a stated focus
Persistent memory + morning brief	Learns from delegation	✓ Memory across channels, daily brief
Approval gates	Configurable per tool	✓ On by default, reviewer you pick
Audit trail per run	Activity visibility	✓ Full trace: calls, sources, approvals
Compliance posture	SOC 2 Type 1	Governance-first design, audit export on Business

Both products evolve weekly; treat this as a snapshot from July 2026 and verify anything load-bearing.

Where Viktor wins

Concede the real things: Viktor is excellent at high-volume, in-chat delegation — especially work that benefits from writing and running code, like data pulls, report generation, and quick internal tools. Its integration count is enormous, its case-study library is public, and SOC 2 Type 1 is a checkbox some procurement teams will want on day one. If your team lives entirely in Slack and wants an AI employee to bury in tickets, Viktor is a credible hire.

Where Arlo wins

Arlo wins on reach and on defaults. Work doesn't stay in Slack: customers text, vendors only answer the phone, and half your own team responds faster in iMessage than in any channel. Arlo is the only one of the two that works across texts and live calls as first-class surfaces. And when an AI touches production systems and customer inboxes, Arlo's model — approval before the send, audit trail after it, policy checks in between — is on from the first minute, not assembled from settings.

How to choose

Ask two questions. First: where does your work actually happen? If the answer is "Slack, full stop," both fit; if it includes texts and calls, that's Arlo. Second: what's your tolerance for un-reviewed AI action? If you want every outbound send gated by a human until trust is earned, Arlo's approval-first defaults are the shorter path. Both offer trials — the cheapest way to decide is to give each the same three tasks from your actual backlog.

Frequently asked questions

Are Viktor and Arlo direct competitors? Partly. Both are AI coworkers that do real work from team chat. Viktor is Slack/Teams-only and leans into code execution; Arlo also covers iMessage, SMS, and live phone calls, and centers approval-first governance.

Does Viktor work over iMessage or SMS? No — as of July 2026, Viktor's stated channels are Slack and Microsoft Teams. Arlo works in iMessage and SMS as first-class channels alongside Slack and Teams.

Can either make phone calls? Arlo places and takes live phone calls, then summarizes them and updates your records. Phone calling isn't part of Viktor's stated product as of July 2026.

Which is better for a non-technical team? Teams that mostly need coordination — scheduling, follow-ups, inbox triage, CRM updates, calls — tend to fit Arlo's shape. Teams that want an AI to write and run code from chat requests tend to fit Viktor's.

Can I try both? Yes, and you should. Arlo starts free — no card needed — with paid tiers from $20/month. Run the same real tasks through each and compare the finished work, not the demos.