Onboards like a person
No prompt-engineering. Hop on a call, walk it through the job the way you'd brief a new hire, and it gets going.
Same frontier models under the hood. The difference is what happens next: ChatGPT hands you text to copy-paste, a droid picks up the phone, works your tools, and ships the deliverable — then keeps doing it on a schedule.
ChatGPT is a brilliant place to think out loud — and your droid runs the same frontier models for the reasoning. The difference is what happens after the answer: ChatGPT hands you text in a browser tab, while a droid lives in Slack, email and on the phone, and finishes the job. Most teams keep both — ChatGPT to think, a droid to do.
At a glance — the full table is just below
The same job, two tools. Here's how they differ where it actually counts.
| Droid | ChatGPT | |
|---|---|---|
| What it is | An AI worker you hire for a role. It joins calls, works your apps, and ships deliverables. | A general-purpose chat assistant for questions, writing, and brainstorming. |
| Where it lives | In Slack, Teams, email, SMS and on a real phone number — the surfaces your team already uses. | In its own web and mobile app. You leave your workflow to go talk to it. |
| Does the work, or talks about it | Executes. Writes and runs code, queries your apps, drafts the artefact, sends the email, opens the PR. | Describes what to do. Plugins and connectors help, but you still paste outputs and run the steps. |
| Voice, phone & video | Live voice calls, its own phone number, and joins Zoom / Meet / Teams calls with screen-share. | Voice chat with the app. No phone number, doesn't join your meetings. |
| App integrations & actions | ~3,000 apps via managed OAuth, with read / write / destructive actions and per-tool policies. | A growing set of connectors and GPTs. No managed, governed OAuth across your business stack. |
| Memory | Typed, persistent memory — contacts, knowledge, past work — shared across every channel and run. | Conversation-scoped memory. Better than it was, but not a shared team brain. |
| Scheduled & triggered work | Durable tasks that run on a schedule or fire on an event — a new email, a webhook — laptop closed. | You start each conversation. Nothing runs on its own in the background. |
| Team & sharing | One workspace, shared memory and automations. Everyone @mentions the same droids. | Primarily one person per chat. Team plans exist, but conversations don't share context. |
| Approvals & governance | Sensitive actions (send mail, push code, move money) wait for approval. Credentials never reach the model. | Not built for taking gated, side-effecting actions on your business systems. |
| Pricing shape | Workspace credits, shared across the whole team. No per-seat charge. | Per-user subscription (Plus / Pro / Team) priced per seat. |
These aren't cleverer answers — they're the things that turn an answer into work that's actually done.
No prompt-engineering. Hop on a call, walk it through the job the way you'd brief a new hire, and it gets going.
It doesn't hand you a draft to paste somewhere. It sends the email, files the record, updates the CRM, opens the PR.
Slack, Teams, email, SMS, a phone number. You reach it where you already work, and so do your customers.
What it learned on Monday is there on Friday — contacts, decisions, the shape of your business — across every channel.
Hand it a recurring job once. It wakes itself up, does the rounds, and only pulls you in when something's genuinely off.
Anything with a side effect waits for your approval. Credentials live in a vault the model never sees.
We'd be lying if we said otherwise — for a lot of jobs, ChatGPT is the right tool, and your droid leans on the same models to think.
It uses frontier models — Anthropic Claude, OpenAI, and Google Gemini — routed per task by cost, latency, and quality. So yes, OpenAI is one of the engines. The product is everything around the model: the voice and channels, the app access, the memory, the schedules, and the approval gates that let it actually take action.
They're built for different jobs. ChatGPT is a general-purpose chatbot for thinking and writing; a droid is a worker that connects to your tools and ships work. Plenty of teams use ChatGPT for individual brainstorming and a droid for the cross-tool, team-wide stuff.
Plugins and GPTs bolt some tools onto a chat session. A droid is a long-lived worker: managed OAuth to ~3,000 apps with read/write governance, durable scheduled tasks, persistent memory, real telephony, and approval gating — all wired into Slack, Teams, email, and phone rather than a chat window.
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.
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 that's been eating your week.
Starter credits, no card. Walk a droid through the job on a call and watch it ship the first one before you hang up.