Lead task
Assign sales follow-ups such as clarifying details, preparing a proposal, calling the customer or checking an attached file.
Tasks in eContractor are built for installation teams that work across leads, jobs, documents, crews and payments. Managers create the next action in context, the team sees execution on Kanban, and nothing depends on scattered chats or memory.
When tasks live outside the operating process, teams lose customer details, technical notes and ownership. In eContractor, a task can be created exactly where the work appears: inside a lead, inside an installation job or as a personal team task.
Assign sales follow-ups such as clarifying details, preparing a proposal, calling the customer or checking an attached file.
Control delivery actions after approval: issue materials, check crew progress, verify payment or prepare the next document.
Create internal reminders and administrative work that does not need a lead or job connection.
Kanban gives managers a clear view of what is new, in progress, completed and waiting for review. Each card keeps its lead or job connection, so the team can jump from the task to the customer, object, files and full history.
Each task has an assignee and a reviewer. The assignee takes the task into work, adds a reply or files, and the reviewer accepts the result or returns it with feedback. It gives managers control without turning simple work into bureaucracy.
Task control works best when the system keeps important work visible. eContractor combines Telegram alerts, reminders, filters and assignee/reviewer roles so managers can control execution without chasing updates in chat.
Assignees and reviewers receive alerts about creation, status changes, due dates, replies, returns and reminders.
A reviewer can remind the assignee about an active task without leaving the Kanban board.
Filter by status, type, assignee, reviewer, lead, job or personal tasks.
Hide tasks from the board when needed while keeping them available in lists and tables.
When task creation is fast and execution is visible, the team relies less on chats, memory and improvised reminders. Tasks become part of the lead and job workflow, not a separate list that sits outside operations.