The magic of WhatsEngine team assignments is that you don’t need to learn any special commands. You just talk about what needs to happen and who should do it, exactly like you would in a normal conversation.Instead of: Click dropdown → Select person → Enter task → Set deadline → Choose priorityYou say: “Sarah should review the proposal by Friday afternoon”That’s it. WhatsEngine handles the rest.
Direct Assignments
Assign tasks to specific team members by name
Question-Based Assignments
Ask “Can someone handle…?” for flexible assignments
Collaborative Tasks
Create tasks that involve multiple people working together
You: "Sarah should review the marketing proposal by Friday"Bot: ✅ Task assigned to Sarah Johnson for Friday at 9:00 AM [Task #15]→ Sarah gets WhatsApp notification immediatelyYou: "Mike needs to follow up with the client tomorrow morning"Bot: ✅ Task assigned to Mike Wilson for tomorrow at 10:00 AM [Task #16]→ Mike gets task details and deadlineYou: "Lisa can handle the design review this afternoon"Bot: ✅ Task assigned to Lisa Chen for today at 2:00 PM [Task #17]→ Lisa sees the assignment in her WhatsApp
Copy
You: "Can someone review this document before the meeting?"Bot: ✅ Task posted to team: Document review needed before 3:00 PM meeting [Task #18]👥 Available team members will be notifiedYou: "Who can handle the client presentation prep?"Bot: ✅ Task available for assignment: Client presentation prep [Task #19]💬 I'll ask the team who's availableYou: "Does anyone have time to review the budget today?"Bot: ✅ Task posted: Budget review needed today [Task #20]🔔 Notifying team members with availability
Monday, 8:45 AM - Team Planning SessionYou: "Good morning everyone! Let's plan out this week. Sarah, you should focus on the content strategy document - can you have that ready by Wednesday?"Bot: ✅ Task assigned to Sarah Johnson: Content strategy document - Wednesday at 2:00 PM [Task #21]Sarah (via WhatsApp): Got it! I'll start working on the content strategy today.You: "Perfect! Mike, we need the technical specs reviewed before the client call on Thursday. Can you handle that by Wednesday afternoon?"Bot: ✅ Task assigned to Mike Wilson: Review technical specs - Wednesday at 3:00 PM [Task #22]Mike (via WhatsApp): Sure thing! I'll prioritize the tech specs review.You: "Great! And Lisa, can you prepare the presentation slides once Sarah and Mike are done? We'll need them for Thursday morning."Bot: ✅ Task assigned to Lisa Chen: Prepare presentation slides - Thursday at 9:00 AM [Task #23]✅ Dependencies noted: Waits for tasks #21 and #22Lisa (via WhatsApp): Sounds good! I'll wait for Sarah and Mike's input first.Bot: 📈 Team workflow created:• Sarah: Content strategy (due Wed 2 PM)• Mike: Tech specs review (due Wed 3 PM)• Lisa: Presentation slides (due Thu 9 AM, after Sarah & Mike)• Team: Client call (Thursday)
Wednesday, 3:30 PM - Urgent Client IssueYou: "We have a situation! The client just called with an urgent issue. Mike, can you jump on a call with them right now to understand the problem?"Bot: ✅ URGENT task assigned to Mike Wilson: Client emergency call - NOW [Task #24]🔔 Mike notified immediately with high priorityMike (via WhatsApp): On it! Calling them now.You: "Sarah, once Mike figures out what's wrong, you'll need to draft a response plan. This is top priority."Bot: ✅ Task assigned to Sarah Johnson: Draft client response plan - depends on task #24 [Task #25]⚙️ Set as high priority, will notify Sarah when Mike completes his callYou: "And Lisa, can you prepare a follow-up presentation in case we need to present solutions tomorrow?"Bot: ✅ Task assigned to Lisa Chen: Emergency presentation prep - tomorrow 8:00 AM [Task #26]⚡ Marked as urgent with priority notificationsLisa (via WhatsApp): Understood! I'll start working on potential solutions now.[20 minutes later...]Mike (via WhatsApp): "done 24 - figured out the issue, it's a configuration problem"Bot: ✓ Completed: Client emergency call🔔 Notifying Sarah: Ready to start response plan [Task #25]Sarah (via WhatsApp): Perfect timing! Starting the response plan now.
Friday, 4:45 PM - Weekly Wrap-upYou: "Let's see how everyone did this week. What tasks are still pending?"Bot: 📋 Weekly team status:🟢 Sarah Johnson: 6/7 tasks completed (86%)• Pending: Blog post editing [#30] - due Monday🟢 Mike Wilson: 5/5 tasks completed (100%)• All caught up! 🎉🟡 Lisa Chen: 4/6 tasks completed (67%)• Pending: Website mockups [#28] - due today• Pending: Logo variations [#29] - due MondayYou: "Great work Mike! Lisa, do you need help with those mockups? They were due today."Lisa (via WhatsApp): Almost done! Can I have until Monday morning?You: "Sure, no problem. Move Lisa's mockups to Monday morning, and let's make sure she has support if needed."Bot: ✅ Rescheduled: Website mockups - Monday at 10:00 AM [Task #28]👋 Offering support: Who can help Lisa if needed?You: "Sarah, can you review Lisa's mockups once she's done and provide feedback by Tuesday?"Bot: ✅ Task assigned to Sarah Johnson: Review Lisa's mockups - Tuesday at 11:00 AM [Task #31]✅ Dependency: Waits for Lisa's completion of task #28Sarah (via WhatsApp): Absolutely! I'll give detailed feedback on the mockups.
You: "Sarah and Mike should work together on the API documentation. Sarah handles the content, Mike covers the technical details. Both need to be done by Friday."Bot: ✅ Collaborative task created: API documentation [Tasks #32-33]• Sarah: Content writing - Friday at 2:00 PM [#32]• Mike: Technical details - Friday at 2:00 PM [#33]• Coordination: Both team members notified of collaborationSarah & Mike get notifications:"You're collaborating with [teammate] on API documentation. Coordinate to avoid overlap!"
Sequential Dependencies
Copy
You: "Mike needs to finish the database setup first, then Sarah can start the integration testing, and finally Lisa can do the UI testing. This should all be done by next Friday."Bot: ✅ Sequential workflow created:• Mike: Database setup - Tuesday 5:00 PM [#34]• Sarah: Integration testing - Thursday 3:00 PM [#35] (after #34)• Lisa: UI testing - Friday 11:00 AM [#36] (after #35)📈 Dependencies configured: Each person notified when previous task completes
Parallel Work Streams
Copy
You: "Let's work on the product launch in parallel. Sarah handles marketing materials, Mike sets up the technical infrastructure, and Lisa designs the landing page. Everything needs to be ready by Monday."Bot: ✅ Parallel workstream: Product launch preparation• Sarah: Marketing materials - Monday 10:00 AM [#37]• Mike: Technical infrastructure - Monday 10:00 AM [#38] • Lisa: Landing page design - Monday 10:00 AM [#39]🔄 Sync point: Monday 10 AM team check-in scheduled
You: "Someone needs to handle the client onboarding process"Bot: 🔍 Checking team availability...🟢 Available: Lisa (3 active tasks)🟡 Busy: Sarah (7 active tasks)🔴 Overloaded: Mike (12 active tasks)Recommended assignment: Lisa Chen✅ Task assigned to Lisa: Client onboarding - tomorrow at 10:00 AM [#40]Would you like me to reassign some of Mike's tasks?
Copy
You: "We need someone to handle the technical documentation"Bot: 📚 Analyzing team skills for "technical documentation"...Best match: Mike Wilson (Technical Writing: 95%)Good match: Sarah Johnson (Technical Writing: 70%)Basic match: Lisa Chen (Technical Writing: 40%)✅ Suggested assignment: Mike WilsonTask: Technical documentation - due Wednesday [#41]Confirm assignment to Mike?
Copy
You: "Someone needs to join the 6 AM Pacific client call"Bot: 🌍 Checking timezone compatibility...✅ Good timing: Mike (West Coast - 6:00 AM local)⚠️ Early: Sarah (East Coast - 9:00 AM local) ❌ Too early: Lisa (London - 2:00 PM local, but prefers mornings)Recommended: Mike Wilson✅ Task assigned: Client call - tomorrow 6:00 AM PST [#42]
You: "If Sarah is available, she should handle the client meeting. Otherwise, Mike can do it."Bot: ✅ Conditional assignment created:• Primary: Sarah Johnson - client meeting tomorrow 2:00 PM [#43]• Backup: Mike Wilson (if Sarah unavailable)💬 Checking with Sarah first...Sarah (via WhatsApp): I'm available! I'll take the client meeting.Bot: ✅ Confirmed: Sarah assigned to client meeting [#43]
Preference-Based Assignment
Copy
You: "We need someone to handle the presentation. Sarah prefers client-facing work, and Mike is better with technical stuff."Bot: 🧐 Analyzing task type: "presentation"• Client-facing component: Yes• Technical component: MediumBest match: Sarah Johnson (client-facing preference)✅ Task assigned to Sarah: Presentation preparation [#44]Note: I've learned Sarah prefers client-facing tasks for future assignments.
[To Sarah's WhatsApp]💼 New task assigned to you:📄 Task: Review marketing proposal📅 Due: Friday at 2:00 PM👤 Assigned by: [Your name]🆔 Task ID: #15Reply with questions or say "got it" to confirm!
Copy
Sarah: "Got it! Quick question - is this the Q4 proposal or the new client one?"Bot: 🤔 Great question! Let me ask [your name]...[To your WhatsApp]💬 Sarah asks about task #15 (Review marketing proposal):"Is this the Q4 proposal or the new client one?"You: "It's the new client proposal - the one we discussed yesterday"[Back to Sarah]💬 Answer from [your name]:"It's the new client proposal - the one we discussed yesterday"Sarah: "Perfect! I'll get started on it today"
You: "Move Sarah's presentation task to Mike instead"Bot: ✅ Reassigned: Presentation task moved from Sarah to Mike [#15]• Sarah notified: Task removed from your list• Mike notified: New task assignedYou: "Sarah is overloaded, give her report task to Lisa"Bot: ✅ Reassigned: Report task moved from Sarah to Lisa [#16]• Workload rebalanced: Sarah (6 tasks) → Lisa (4 tasks)
Emergency Reassignments
Copy
You: "Mike is out sick today. Move all his urgent tasks to the team"Bot: ⚙️ Processing Mike's urgent tasks...✅ Redistributed 3 urgent tasks:• Client call → Sarah (has client experience)• Code review → Available for any developer• Budget report → Lisa (has capacity)🌡️ Mike's non-urgent tasks postponed until he returns
You: "How is the team performing this month?"Bot: 📈 Team Performance (This Month):🏆 Sarah Johnson:• 15/16 tasks completed (94%)• Avg completion: 1.2 days• Strength: Client communication🏆 Mike Wilson:• 22/23 tasks completed (96%)• Avg completion: 0.8 days • Strength: Technical tasks🏆 Lisa Chen:• 18/20 tasks completed (90%)• Avg completion: 1.5 days• Strength: Creative projects
Copy
You: "Optimize the team workload for next week"Bot: 🔍 Analyzing next week's assignments...⚠️ Current issues:• Mike: 12 tasks (overloaded)• Sarah: 4 tasks (underutilized)• Lisa: 6 tasks (good balance)✅ Suggested redistributions:• Move "API documentation" from Mike to Sarah• Move "Client onboarding" from Mike to Sarah• Keep "Database migration" with Mike (technical)Apply these changes?
[Day before deadline - to team member]🗺 Tomorrow's deadline reminder:"Review marketing proposal" due at 2:00 PM [#15]Need more time? Reply to reschedule![Day of deadline - 2 hours before]⏰ Deadline in 2 hours:"Review marketing proposal" due at 2:00 PM [#15][To you if task becomes overdue]🚨 Sarah's task is now overdue:"Review marketing proposal" was due 30 minutes ago [#15]
Escalation Notifications
Copy
[If task is 2 hours overdue][To you]: 🚨 Escalation: Sarah's task "Review marketing proposal" is 2 hours overdue [#15][To Sarah]: 💬 Your manager has been notified about the overdue task. Please provide an update.[If task is 1 day overdue][To team]: 🆘 Task needs coverage: "Review marketing proposal" [#15]Who can help Sarah complete this?
✅ “Sarah, review the client proposal and highlight any concerns”
✅ “Mike, test the login system and document any bugs”
❌ “Sarah, handle the proposal stuff”
❌ “Mike, check that thing”
Realistic Deadlines
✅ “Finish by Friday afternoon” (gives buffer)
✅ “We need this before the Monday meeting”
❌ “Get this done ASAP”
❌ “Sometime soon”
Team assignments work best when everyone on your team understands they can communicate naturally with WhatsEngine. Encourage them to ask questions, request clarifications, and provide updates just like they would in any team conversation.
