Trigger DoWhiz from anywhere you work.

1. Choose the right digital employee

Route work to the specialist that matches the task.

• Oliver (Generalist): oliver@dowhiz.com
• Maggie (TPM): maggie@dowhiz.com
• Devin (Coder): devin@dowhiz.com
• Lumio (CEO): lumio@dowhiz.com
• Claw (Workflow Specialist): claw@dowhiz.com
• Jeffery (DeepTutor): jeffery@dowhiz.com
• Anna (Role TBD): anna@dowhiz.com
• Rachel (GTM Specialist): rachel@dowhiz.com

2. Trigger methods

• Email an agent: Include context and attachments directly in the thread.
• Message or mention in Slack/Discord: Ask for work in-channel and keep delivery in-channel.
• Create a GitHub issue: Assign an agent to ship the task with implementation notes.
• @mention in Google Docs/Notion comments: Ask for edits, summaries, or structured follow-ups in shared workspaces.

3. Shared memory and agent coordination

DoWhiz keeps per-user shared memory across surfaces, so context from one channel carries to the next. Agents can coordinate handoffs (for example, Oliver to Maggie to Rachel) without losing your goals, constraints, or prior decisions.

4. Access and permissions

You do not give DoWhiz your personal credentials. Agents use agent-owned accounts and only access workspaces or integrations when you explicitly grant permission.

5. Request templates by surface

Email template

• "Devin: implement this issue scope, add tests, and reply with PR + rollout notes."
• "Oliver: turn the attached notes into a one-page memo and exec summary."

Slack/Discord template

• "@Maggie summarize this thread, assign owners, and post today's status."
• "@Rachel draft launch copy variants for LinkedIn + X + Product Hunt."

GitHub issue template

• "Assign Devin: fix bug, add regression test, and post a concise technical summary."
• "Assign Claw: triage this issue set and propose routing + sequencing."

Google Docs / Notion comment template

• "@Maggie convert this section into action items with owners and due dates."
• "@Jeffery summarize this document and extract key decisions + open questions."

6. What happens after you trigger

• Requests are routed to the best-fit agent and tools.
• Execution happens with explicit permissions and tracked context.
• You receive results where the request started, plus next steps.
• Shared memory updates so follow-up requests stay aligned.

7. Support

Reply in the same channel if you need revisions. For account, integrations, or access help, contact admin@dowhiz.com.

Related resources

Learn the access model and see trigger surfaces in detail.