Task deadlines: answer windows, ladders and finishes
Chapters
A customer is promised an answer in fifteen minutes, the task sits for an hour, and nobody notices until they complain. In Fivexer every task carries its own plan for what happens after you press Create, so a task keeps its promise even when nobody is watching it.
The answer window
The first part of the plan is the answer. You give a worker a set time to accept the task, for example fifteen minutes. If they let that time pass, the task goes to someone else, and the person who let it pass is skipped next time.
An escalation ladder
Urgent work can have a ladder. If the first group of people does not answer, the task moves up to the next group, and each step raises its priority. At the top of the ladder the task stops and waits for you, so it can never circle forever without anyone noticing.
The finish
The second part of the plan is the finish. You can say that the work is due four hours after it is accepted, and that it comes back to you if it runs over. Work that is useless by tomorrow can be set to drop itself, and after a number of refusals the task stops and waits for a person to decide.
Seeing the clocks
Open any task to see its clocks. A task that has run past its finish time shows a red bar with how far over it is, and Live ops lists stopped work under Needs you. From the list of stopped tasks you can send one back to the queue and choose whether its clocks start over.
You can set the defaults for every new task in Settings and still change them on any single task. The previous guide covers skills and levels, and the next one shows Live ops on a busy morning.
Transcriptthe full narration, 8 paragraphs
A customer was promised an answer in fifteen minutes, but the task sat for an hour and nobody noticed. Here is how a task keeps its own promise.
Every task carries a plan for what happens after you press Create. The first part is the answer. Give a worker fifteen minutes to accept. If they let it pass, the task goes to someone else and skips them next time.
Urgent work can have a ladder. If the first group doesn't answer, the task moves up to the next one, and each step raises its priority. At the top of the ladder, it stops and waits for you.
The second part is the finish. This work is due four hours after it is accepted, and it comes back to you if it runs over. Work that is useless by tomorrow can drop itself, and after three refusals it waits for a person.
Create the task, and the deadlines travel with it from now on.
Open any task to see its clocks. This one ran past its finish time, and the red bar shows by how much.
Stopped tasks wait here for you. Open one and send it back to the queue, and choose whether its clocks start over.
You can set the defaults for every new task in Settings and still change them on any single task. The next guide looks at Live ops on a busy morning.