Top 20 user questions about DoWhiz
This Help Center answers the most common setup, workflow, security, and support questions from teams using DoWhiz across channels.
1. What is DoWhiz?
DoWhiz is a multi-channel, tool-native digital employee team with shared memory. You can trigger work from the tools you already use and receive finished outputs in context.
2. How do I get started?
Pick the employee that fits your request, then send a clear task with context, deliverable format, and deadline from your preferred channel such as email, chat, GitHub, or shared docs. Afterwards, create a DoWhiz account to gain further access to employee tools, such as editing employee memory.
3. Which channels can I use to trigger tasks?
DoWhiz supports triggers through email, Slack, Discord, GitHub issues, and shared document comments such as Google Docs and Notion.
4. How do I choose the right digital employee?
Use Oliver for general execution tasks, Maggie for TPM coordination, Devin for coding tasks, Rachel for GTM workflows, and the other role pages for specialized scopes.
5. What information should I include in my request?
Include objective, context, files/links, constraints, due date, and what a successful output looks like. Clear acceptance criteria helps agents deliver faster. If you want the employee to remember information across sessions, alter the employee memory.
6. What kinds of work can DoWhiz handle?
Common tasks include writing, summaries, planning docs, status updates, technical implementations, testing support, and tool-native deliverables such as docs, sheets, slides, and code.
7. Can DoWhiz work inside existing threads or issues?
Yes. You can trigger from existing email threads, chat channels, GitHub issues, and document comments so context stays in one place.
8. Can multiple employees collaborate on one request?
Yes. Employees can hand off between roles when needed while preserving shared context and returning a unified result.
9. Do employees remember context across channels?
Yes. Shared memory keeps durable preferences and project context so follow-up requests are more consistent.
10. Can I update or reset what is remembered?
Yes. You have full control of your agent's memory after creating a DoWhiz account, and can choose what is (and isn't) remembered by your agent.
11. Do I need to share my personal passwords?
No. DoWhiz uses agent-owned identities and does not require your personal credentials for day-to-day task execution. For DoWhiz accounts, the password you enter is secure and protected.
12. How are permissions managed?
Access is permission-bound. Employees only operate in local workspaces and integrations that you explicitly authorize, and access can be revoked through platform controls.
13. How is my data used?
Data is used to route requests, execute tasks, and return outputs. See Privacy and Trust & Safety pages for details on handling, retention, and controls.
14. Are requests and outputs auditable?
Yes. Work is tied to the trigger surface (for example, issue, thread, or comment) and returned with a clear task summary.
15. Can an employee access everything on my device?
No. Access is scoped to what has been granted for that workflow and channel via isolated workspace.
16. Can DoWhiz ship code changes and PRs?
Yes, for repositories that DoWhiz employees have write access to. DoWhiz employees can implement scoped changes, run checks, and summarize outcomes.
17. Can DoWhiz edit docs, sheets, and slides?
Yes. Tool-native workflows support document and spreadsheet updates in supported workspaces.
18. What if I need revisions?
Reply in the same thread with specific edits. DoWhiz iterates quickly and keeps previous context.
19. How quickly do tasks complete?
Simple requests can finish quickly, while complex work takes longer. You receive progress-oriented updates and final deliverables in the same channel.
20. How do I get support or request a new integration?
Email admin@dowhiz.com with your use case, current workflow, and desired integration. The team can advise setup and next steps.