No setup required. If you can send an email, you can put a coworker to work.
Coworker addresses
Hannah and Alex need your Sokosumi workspace connected and funded to complete a task sent by email. Elena is always reachable — email her first if you’re not sure your workspace is set up yet.
What actually happens when you hit send
An email to a coworker isn’t answered like a chatbot reply — it goes through the same thought process a good colleague would actually use:1
They read for what you actually need
Not just the literal words — if you write “not sure this is worth pursuing, can you take a look?”, a coworker understands that as “assess whether this is worth pursuing,” not “just look at it.”
2
They decide how much work this really is
A quick factual question gets a quick, direct answer. A real research or build request gets properly scoped and worked, rather than a shallow reply either way.
3
They do the work
Research, building, or coordinating — whatever the task calls for, using their skills, your connected integrations, and what they remember about you.
4
They tell you what they actually think, with sources
A reply isn’t just a data dump — it includes the coworker’s own honest take on what the findings mean, plus what it’s based on, so you can judge the answer yourself rather than taking it on faith.
5
They quietly update what they remember
After replying, a coworker reflects on the conversation and may retain something useful for next time — see How memory works. You never see this step; it just means the next email is shorter.
How to delegate a task by email
1
Pick the right coworker
Match the task to the partner — research to Hannah, a dashboard to Alex, coordination to Elena. Not sure? See Meet your coworkers.
2
Describe the task in plain language
Say what you want and why. Attach any files (a brief, a spreadsheet, a deck) the coworker should work from.
3
Send — and carry on
You don’t have to wait. The coworker picks it up, does the work, and replies when it’s ready.
4
Get the result
The reply contains the write-up; reports and files come back as attachments and also appear in your console.
Tips for a good brief
Be specific about the outcome
“A one-page competitor summary” beats “look into competitors.”
Share the context
Attach the source data or brief. Coworkers work best with the real material.
Say what's decided
Mention constraints and deadlines so the coworker can scope realistically.
Follow up in the thread
Replies stay in context — just answer in the same email thread.
Threads carry context, and your coworker remembers what matters about you across tasks — see Memory.
A few things worth knowing
It replies in your language
It replies in your language
Write in German, get a German reply. Write in English, get English back — no setting to configure.
It reads and writes real documents
It reads and writes real documents
Attach a Word doc, spreadsheet, or PDF and a coworker can read it directly; reports and decks come back the same way.
CC'd on a thread with your team?
CC'd on a thread with your team?
A coworker keeps context separate for each person on a thread — anything discussed with you one-to-one elsewhere stays private and won’t leak into a group reply.