Tasks & Projects
The GoWeBa Tasks & Project Management module is a full-featured Kanban system integrated with the CRM. It combines the simplicity of a to-do list with the power of a project management tool: visual pipelines, subtasks, time estimates, AI prioritization, and workload analysis.
Key Concepts
Data Model
Task Fields
Task Statuses
Priorities
Pipelines and Stages
What is a pipeline?
A pipeline is a visual workflow made up of ordered stages. Each organization can create multiple pipelines for different processes:
- Sales Pipeline: Prospecting → Qualification → Proposal → Negotiation → Won / Lost
- Support Pipeline: New ticket → Pending → In progress → Resolved → Closed
- Project Pipeline: Backlog → Sprint → In development → Testing → Delivered
- Recruiting Pipeline: Application → Interview 1 → Interview 2 → Offer → Hired
Pipeline Configuration
Pipeline Stages
Views and Displays
Kanban View (Board)
The primary view is an interactive Kanban board:
- Columns = pipeline stages
- Cards = tasks with title, priority, due date, assignee
- Drag & drop: move a task between stages
- Colors: visual priority and status indicators
- Filters: by assignee, priority, tags, due date
List View
A sortable table view with all tasks:
- Sort by date, priority, status, assignee
- Advanced filters: combined criteria
- Multi-select: bulk actions (change status, assign, delete)
- Export: CSV or PDF of filtered tasks
Pipeline View (Pipelines page)
The Tasks → Pipelines page offers an administrative view of pipelines:
- List of all organization pipelines
- Statistics: number of tasks per stage
- Management: create, edit, archive, reorder pipelines
- Stage configuration: add, rename, delete, reorder
Artificial Intelligence and Automation
Creating Tasks via WEBA
WEBA can create tasks from natural language: "Remind me to invoice Acme Inc on Friday" → Task created: "Invoice Acme Inc", Due: Friday, Priority: NORMAL "Urgent task: fix the payment bug before noon tomorrow" → Task created: "Fix the payment bug", Due: tomorrow 12 PM, Priority: URGENT
AI Prioritization
The /api/tasks/ai/priority API uses an AI model to suggest the optimal priority for a task based on:
- Task description and title
- Due date and remaining time
- Current workload of the assignee
- History of similar tasks
- Estimated business impact
Workload Analysis
The /api/tasks/ai/workload API provides an AI-driven analysis of work distribution:
- Load per member: number of tasks and estimated hours per person
- Overload detection: alerts when a member has too many urgent tasks
- Reassignment suggestions: proposals to balance the workload
- Predictions: estimated delivery time for tasks in the pipeline
Post-call Actions
After a phone call, WEBA automatically extracts action items and can convert them into GoWeBa tasks:
- Call summary — WEBA transcribes and summarizes the conversation
- Action item extraction — Commitments made are identified
- Task conversion — Each action item can be created as a task with one click
- Assignment — Tasks are assigned to the appropriate user
Subtasks and Comments
Subtasks
Each task can have subtasks to break down the work:
- Unlimited hierarchy: subtasks of subtasks
- Progress: the parent task’s completion percentage reflects its subtasks
- Cascade: deleting a parent task also deletes its subtasks
- Independence: each subtask has its own status, priority, and assignee
Comments
Comments enable discussion on a task:
- Free text with markdown formatting
- @member mentions to notify a colleague
- Full comment history
- Attachments: files linked to the comment
Task Analytics
The Tasks → Analytics page provides detailed statistics:
CRM Integration
GoWeBa tasks are deeply integrated with the rest of the platform:
Real-world Use Cases
Scenario: Sales pipeline
- Create the pipeline — Sales: Prospecting → Qualification → Proposal → Negotiation → Won ✅ / Lost ❌
- New lead — Create a task "Contact Acme Inc" in the Prospecting stage
- Qualification — After the first contact, move to Qualification
- Proposal — Create a quote via WEBA and link it to the task
- Negotiation — Pricing discussion, tracking exchanges
- Conclusion — Move to "Won" → the task is completed
Scenario: Sprint management
- Create the pipeline — Project X: Backlog → Sprint → In progress → Review → Done
- Sprint planning — Move priority tasks from Backlog to Sprint
- Execution — Developers move their tasks to "In progress"
- Review — Completed tasks go to review for validation
- Delivery — Validated tasks move to "Done"
- Analytics — Check sprint velocity in the analytics dashboard
Troubleshooting and FAQ
Q: How many pipelines can I create? A: Unlimited. Create one pipeline per business process. Q: Can a task be assigned to multiple people? A: Currently, a task has a single owner (ownerUserId). For collaborative work, use subtasks assigned to different people. Q: Are expired tasks automatically deleted? A: No. Overdue tasks remain visible with a red visual indicator. They must be closed manually (DONE or CANCELLED).
— End of Module 06 —
GoWeBa — Operations Bible Document generated on May 6, 2026
| Concept | Description |
|---|---|
| Task | Unit of work with title, description, status, priority, due date |
| Pipeline | Custom workflow (e.g., Sales, Support, Development) |
| Stage | Column in the pipeline (e.g., To do, In progress, Done) |
| Subtask | Child task linked to a parent task (hierarchy) |
| Comment | Discussion and notes attached to a task |
| Tags | Labels for categorizing and filtering tasks |
| Field | Type | Description |
|---|---|---|
| title | Text | Task title (required) |
| description | Long text | Detailed description, instructions |
| status | Enum | TODO, IN_PROGRESS, BLOCKED, IN_REVIEW, DONE, CANCELLED |
| priority | Enum | LOW, NORMAL, HIGH, URGENT |
| dueAt | Date | Task due date |
| startAt | Date | Planned start date |
| completedAt | Date | Completion date (filled automatically) |
| estimatedMinutes | Number | Estimated time in minutes |
| actualMinutes | Number | Actual time spent in minutes |
| ownerUserId | UUID | Member assigned to the task |
| relatedContactId | UUID | Associated CRM contact |
| tags | List | Categorization labels |
| sortOrder | Number | Display order within the stage/list |
| pipelineId | UUID | Pipeline the task belongs to |
| stageId | UUID | Current stage in the pipeline |
| parentTaskId | UUID | Parent task (for subtasks) |
| Status | Description | Color | Closed? |
|---|---|---|---|
| TODO | To do — not yet started | Gray | No |
| IN_PROGRESS | Currently being worked on | Blue | No |
| BLOCKED | Blocked by an obstacle | Red | No |
| IN_REVIEW | Awaiting validation/review | Orange | No |
| DONE | Completed successfully | Green | Yes |
| CANCELLED | Cancelled — no longer relevant | Strikethrough gray | Yes |
| Priority | Level | Visual indicator | Typical usage |
|---|---|---|---|
| LOW | 1 | 🟢 Green | Non-urgent tasks, future improvements |
| NORMAL | 2 | 🔵 Blue | Standard daily work |
| HIGH | 3 | 🟠 Orange | Important, handle quickly |
| URGENT | 4 | 🔴 Red | Critical, immediate action required |
| Field | Type | Description |
|---|---|---|
| name | Text | Pipeline name (required) |
| description | Text | Pipeline description and purpose |
| color | Hex | Identification color |
| icon | Emoji/text | Visual icon |
| isDefault | Boolean | Default pipeline for new tasks |
| isArchived | Boolean | Archived pipeline (hidden but data preserved) |
| sortOrder | Number | Display order in the pipeline list |
| Field | Type | Description |
|---|---|---|
| name | Text | Stage name (e.g., "In progress") |
| color | Hex | Kanban column color |
| sortOrder | Number | Position from left to right |
| isClosed | Boolean | Closed stage (tasks are considered completed) |
| isWonStage | Boolean | Won stage (Sales pipeline: "Won") |
| Metric | Description |
|---|---|
| Total tasks | Total number of tasks in the period |
| Tasks by status | Distribution: TODO / IN_PROGRESS / DONE / etc. |
| Tasks by priority | Distribution: LOW / NORMAL / HIGH / URGENT |
| Overdue tasks | Number of tasks past their due date |
| Average completion time | Average duration from creation to DONE |
| Load per member | Number of tasks per assignee |
| Velocity | Number of tasks completed per week |
| Tasks created vs completed | Productivity ratio |
| Module | Integration | Example |
|---|---|---|
| Contacts | relatedContactId | Task linked to a contact: "Follow up with Acme Inc" |
| Calendar | Via WEBA | Task → event: "Meeting to discuss the task" |
| Billing | Via WEBA | Task "Invoice Acme" → invoice created via the Studio |
| Telephony | Post-call action items | The call automatically generates follow-up tasks |
| Via Webabox | Task created from an email: "Reply to the client" | |
| WEBA | Voice/chat creation | "Remind me to…" → task created |
| Issue | Likely cause | Solution |
|---|---|---|
| Task not visible | Active filter hiding it | Reset filters ("Clear filters" button) |
| Drag & drop not working | Incompatible browser | Use a recent version of Chrome, Firefox, or Edge |
| Subtask disappeared | Parent task deleted | Subtasks are deleted in cascade — restore if possible |
| Analytics empty | Period too short | Expand the analysis period (30 d, 90 d, 1 yr) |
| WEBA does not create the task | Intent not detected | Rephrase with clear keywords ("task", "remind me", "to do") |