Work and actions

In Wagend, everything that needs doing is a task: an appointment, a table, a visit, a delivery. A conversation can create one; you also create them by hand with the New task button or through the API. The panel gives you three main destinations: Today, Inbox and Work. The rest lives under More.

Today, Inbox and Work

• Today is your day's board. It shows what needs your attention, what is next, what is in progress, what is later today and, collapsed, what is completed. Team members see only their own (Mine); owner and manager switch between Mine and All.
• Inbox gathers the conversations that need a person. See The bot and the AI.
• Work is where you see all tasks. You look at it along two axes that combine.

Work: set × form

First you choose which work to see (the set):

Then you choose how to see it (the form):

"If it has nothing, it does not show": a form only appears when your business needs it. All of them open the same task detail. Filters (search, priority, tag, dates), order and grouping apply to every form.

The task and its stages

Each task is in a stage. Stages are your business's vocabulary: a barbershop uses Confirmed → In progress → Completed; a delivery uses Unassigned → Accepted → On the way → Delivered. Behind them are fixed states (hold, confirmed, in progress, completed, cancelled, absent, failed), so numbers and statistics mean the same in every industry.

The task detail shows the customer, the date and resource, notes, form data, the origin (for example the WhatsApp conversation it came from) and the comments and activity.

Forms per service

A service can ask for its own data when the task is created: the delivery address, the reason for the visit, the equipment model. That data is filled in on the task and stays with it. It is defined on the service (More → Business → Services).

Actions

Actions are a task's buttons. Depending on the stage, role and business, the panel shows one big main action (for example Accept delivery or On my way) and the rest under Other actions. Each action can ask for confirmation or a short form (a comment, a reason).

An action can do more than change stage. The available effects are:

Everything an action does happens together or not at all: if something fails, nothing is left half done. And an action never grants extra permissions: a team member cannot assign tasks even if the button existed.

Unassigned tasks and queues

Some jobs have no set time, like deliveries. They enter as Unassigned, whoever can do them takes them and then follows the sequence. A team member sees the tasks assigned to them and those their group can take, without the customer's phone or email until they take it. A courier first sees only the approximate area.

Example in the deliveries industry:

1. An order arrives: it is Unassigned.
2. A courier taps Accept delivery: the task is theirs. (Or the manager taps Assign delivery.)
3. If they cannot, they tap Release delivery and it goes back to the queue.
4. They tap On my way, then Arrived.
5. They close with Complete, or with Not home or Refused (plus a reason).

Each industry with its own vocabulary

Stages and actions come from your industry's template (barbershop, aesthetics, clinic, restaurant, deliveries) and can be adjusted. Barbershop, aesthetics, clinic and restaurant come with Start, Complete, Cancel and No-show. To rename them or add actions, today you do it through the API or the MCP server: see API and MCP.

Work evidence

An action can ask for the location at that moment (for example when marking "Arrived") and a task accepts attachments (photo, document, audio, note). They are private: only people with access to that task see them, download links expire after 60 seconds and files are deleted after a retention period (30 days by default). The owner or manager can delete a location.

What each role sees

More in Roles and permissions.

Automate the work

Every stage change or action can trigger a message or a flow: see Flows.