Documentation / Working with tickets

To do

Minimum role
Viewer
Applies per
organisation
Last updated
11 October 2026
aishaa version
80c056408

Menu path: To do

In short: To do is the list with everything waiting for a person: proposals from aishaa that someone has to approve (for example a plugin action, a message to the customer or to an external party), and requests and tasks that a workflow sets up for your team. You see everything across tickets, filter by kind, person and status, and handle an item by expanding it. Whatever nobody handles expires by itself after a while.

Where to find this

  • The To do menu in the left-hand navigation. The page subtitle is Requests, tasks and proposals waiting for someone.
  • Next to the menu item is the number of open items, with the tooltip To do: (number). That number is exactly what the list shows when you open it. It is also in the menu on your phone.
  • The Dashboard has the To do tile with the same number. Clicking it opens this page.
  • On a ticket, the same items are on the Activity tab. See Reviewing and starting actions on the ticket.

Who: everyone with access to tickets sees the list, from the Viewer role upwards. Handling items (answering, marking as done, executing, rejecting) is possible from the Agent role upwards. For a plugin action, the minimum role set per action applies on top of that.

You see the items of all organisations you have access to, limited by your Work scope (see below). Everyone within that scope also sees the items assigned to a colleague.

The To do page with the search field, the Kind, For and Status dropdowns, and the columns What, Status, Where, Due, Created by and Created.

What is in To do

Kind Where it comes from What you do
Proposal aishaa or a workflow proposes something that a person has to approve: a plugin action in a connected system, a message to the customer, a WhatsApp template, a message to an external party, a change to the ticket (status, assignment, labels, merging) or snoozing a ticket. Check it and Execute, Send or Reject.
Request A workflow asks a colleague for a decision or for details, and waits for the answer. Fill in fields if needed and click one of the answer buttons.
Task A workflow sets up a task for the team. The workflow does not wait for it. Do the work and click Mark as done.

Not in To do:

An item usually belongs to a ticket. A workflow can also set up a request or task that belongs to no conversation at all; the Where column then says Outside a conversation.

Filtering and searching

At the top of the list, from left to right:

Element Options
Search Searches in the title, the summary, the plugin and action, the ticket number and the ticket subject.
Work scope Only if your account has more than one organisation. Choose from which organisations you see the items. The tooltip shows Work scope: all organisations or Work scope: (number) of (number) organisations. The same work scope applies to the ticket list, the dashboard and the counter next to the menu item.
Kind All (default), Proposals, Requests, Tasks.
For Everyone (default), Me (assigned to you), Not assigned.
Status Pending (default), Executed, Failed, Rejected, Expired, Replaced, All.

The Refresh button reloads the list. The list also refreshes by itself when a colleague handles something.

With the status Pending, the item with the earliest deadline is at the top; items without a deadline come after that, newest first. With the other statuses, the newest item is at the top.

The columns

Column What you see
What The title or summary. For a request or task, Request or Task is shown below it, and For (name) if it is assigned to someone.
Status Pending, Failed, Rejected, Expired or Replaced. A handled item is called Executed (proposal), Answered (request) or Done (task).
Organisation Only in an account with several organisations: logo and name.
Where The ticket number and subject; clicking opens the ticket. Or Outside a conversation.
Due Date and time, with a red Overdue chip if an open item is past its deadline.
Created by The workflow, the AI agent or the colleague, with the source below it: AI proposal, aishaa, on request, From view, Manual or Workflow.
Created Date and time. For an outdated proposal, the chip (age) old or New message since; for an executed item, Executed by.

Expand a row with the arrow at the front to see the whole item and handle it straight away. Double-click a row to open the ticket. If there is nothing, it says Nothing to do here.

Answering a request

An expanded request from a workflow in the To do list, with the line Workflow: (name), the deadline, the From the workflow block, input fields and the answer buttons.

A request shows:

  • the title, Workflow: (name of the workflow), the status, For (name) if it is assigned to someone, and Due (time) or Overdue;
  • buttons to what the request is about, for example the customer, a recorded conversation or a document the workflow made;
  • the workflow’s question;
  • under From the workflow, the details the workflow shows with it;
  • possibly fields you have to fill in, already filled in where the workflow could;
  • one to six answer buttons. The person who made the workflow decides the text of the buttons.

Click the answer that fits. The first button checks whether the required fields are filled in; the other buttons do not. You see Answer sent and then on the item (name) answered “(answer)” on (time). The workflow continues straight away with your answer and the fields you filled in.

If nobody answers before the deadline, the request expires and the workflow continues without an answer: Nobody answered in time, so the workflow went on without an answer. A request always has a deadline: seven days by default, thirty days at most, as set in the workflow.

A request can be assigned to a colleague, but any colleague with the Agent role can answer it. You cannot assign an item in To do to someone else.

Completing a task

A task shows the text the workflow gave it, possibly with a deadline. Do what is asked and click Mark as done. You see Task done and then Done by (name) on (time).

The workflow that made the task does not wait for it to be marked as done. If the deadline of a task passes, it gets the Overdue chip; it does not expire because of that.

Reviewing a proposal

You expand a proposal into the full card, with the same buttons as on the ticket:

Proposal Buttons
Plugin action Check or change the parameters, Execute or Reject (with Reason).
Message to the customer Change the text, Send or Reject. The message goes out in the conversation’s own channel, with your signature.
WhatsApp template to the customer Only change the values, Send template or Reject.
Message to an external party Change the text, Send or Reject.
Change to the ticket Execute or Reject.

If a proposal is more than 24 hours old, or a new message has come in since, you first have to confirm that the content still holds. How that works, the AI’s doubts and who may execute are explained in Reviewing and starting actions on the ticket.

In the To do list, a card does not fetch extra data from connected systems, and the button to add a produced file to your reply is not there. Open the ticket for that.

If the proposal came from a workflow, that workflow continues as soon as you decide: after executing, rejecting or when the proposal expires.

When an item expires

Whatever nobody handles does not stay forever:

  • Closed ticket: if a ticket is closed or deleted, everything that was still open on it expires at once. The item says Expired: the ticket was closed before anyone decided. If you reopen the ticket, the items do not come back.
  • Account term: proposals from aishaa and items from a workflow without their own deadline expire after the term the Account admin sets. The item says Expired: nobody decided within the account’s term.
  • Own deadline: a request or proposal with its own deadline follows that deadline.
  • An action that a colleague started by hand does not expire through age.

An expired item has the status Expired. An Account admin sets the term under Account > Account settings, section To do, with aishaa’s proposals expire after: Standard (14 days), 7 days, 14 days, 30 days, 60 days, 90 days or Never. See Account settings.

If a particular proposal from an agent keeps being left until it expires, aishaa proposes turning that proposal off. You see that proposal under Organisation > Intelligence > Changes, with the buttons Yes, turn off and No, keep it. See Changes and reverting.

Good to know

  • The status Replaced means that aishaa replaced her own proposal with an updated version. The old proposal says aishaa replaced this proposal with an updated version.
  • You do not get an email or push notification for items in To do. You see them in the list, in the counter next to the menu item, on the dashboard tile and on the ticket itself.
  • The old address of the Plugin actions page now also opens To do.
  • You do not create requests and tasks by hand in To do; they come from workflows. How to have a workflow set up a request or task is explained in Building blocks: people.
  • Tasks in To do are different from follow-up actions (Open actions). You link follow-up actions to a ticket yourselves and they do not count in To do.

Related

Last updated on 11 October 2026. Checked against aishaa version 80c056408. Something wrong or missing? Email support@aishaa.nl.