Inactivity and disconnection

During a module, two different things can take tickets out of your hands: not acting while tickets wait for you, and losing your connection. Each has its own clock, and the Console warns you before anything happens.

Inactivity

When the clock runs

The inactivity clock runs only when a ticket is waiting for an action from you — typically a reply to the customer — and you take none. If you have no tickets, or the next step is the customer's, the clock does not run. Being available with nothing to do is never counted.

The clock starts only after 5 minutes without any action at all, so reading a long conversation or writing a long reply is not counted as inactivity.

What each step does

1. 10 minutes of inactivity. No new tickets are sent to you. You keep the tickets you have, and new ones resume when you act again.
2. 20 minutes of inactivity. The module is disconnected and released, your tickets go to another Human Node, and the module is recorded as not delivered.

Counting the 5 minutes before the clock starts, this happens at about 25 minutes without any action.

The inactivity within a module also adds up. If it reaches 1 hour in the same module, even in short pauses, the module is disconnected. The total starts again with each module.

The warning

The Console tells you when you are inactive and, before the module is disconnected, shows how much time is left.

Losing your connection

What happens when you drop

1. Razviel notices that you went offline. The inactivity clock stops: being offline is not the same as not acting.
2. Your tickets wait for you. They stay with you. The AI does not take them over, because they reached you precisely because they needed a person.
3. You have 30 minutes to come back. Reconnect within that time and you resume your own tickets where you left them, except any ticket the brand's team has already opened and answered.
4. After 30 minutes, your tickets go to other Human Nodes on the brand, or to the brand's own team if no one is available. The rest of the module is offered to other Human Nodes when there is enough of it left.

A dropped module still counts

The 30 minutes run in full. If you do not come back in time, the module counts as not delivered, the same as a module you never entered. The commitment is to deliver the module, not to stay signed in. See Missing a module.

Keeping your connection and equipment working during a module is your own responsibility. A failed connection is never handled through a deduction from what you already earned. See What you need.