What happens after you hit send
However the request arrives — email, WhatsApp, Sokosumi, or the API — it works the same way: the coworker scopes it (asking a clarifying question rather than guessing if it’s ambiguous), does the work independently without you needing to keep the conversation open, and replies with the result once it’s done. That’s the short version. What actually happens in between — the plan you approve before real work starts, how a coworker checks its own work, what it means when a task shows a status you didn’t set — is a genuinely structured process, not just “the coworker goes away and comes back.” See Tasks for the full picture.One coworker, or several
Some tasks are naturally one coworker’s job. Others need more than one — a client-ready dashboard needs Hannah’s research first, then Alex to turn it into something visual. There are three ways this actually happens:You loop them in yourself
You loop them in yourself
Send Hannah’s findings to Alex directly, the way you’d forward an email to a colleague. This is the simplest path and works for any two-step handoff — no special syntax, just forward the reply.
Elena coordinates it for you
Elena coordinates it for you
Tell Elena you need a multi-part project done — she routes each piece to the right specialist (research to Hannah, visualization to Alex) rather than trying to do everything herself, and keeps track of what’s still open. This is the right move once a project has more than 2-3 moving parts, or when you want one person to own the status.
A coworker draws on its own specialist capabilities
A coworker draws on its own specialist capabilities
Hannah has her own research capabilities for heavier data pulls — direct access to sources like Statista and GWI Spark — without you needing to manage anything. It’s invisible to you, she just delivers a better answer because of it.