Dispatch Flow Builder

the dispatch flow builder allows you to control how delivery tasks are assigned to your agents it helps automate the assignment process and ensures that orders are distributed efficiently based on your preferences navigating to the dispatch flow builder within the autozod panel, in the left side menu, click on the dispatch builder section understanding the flow the flow is designed in a simple step by step structure in house only defines that orders will be handled by your internal agents automatically assign orders enables automatic task assignment in house driver settings let's you configure how agents receive and handle assigned tasks assignment modes (auto/ manual assignment) enable for auto assignment or disable for manual assignment directly from the autozod dashboard, offering flexibility in managing order allocation based on your preference order assigning logics autozod presents three assignment logics, namely "all," "round robin," and "force assign," each designed to efficiently allocate delivery tasks based on different parameters and operational needs round robin orders are offered to the closest available rider first within the https //help hyperzod com/settings#tvfet ; if rejected or not accepted within a timeframe, it goes to the next available rider within the same radius all orders are sent to all available riders within the https //help hyperzod com/settings#tvfet ; the first acceptance gets the delivery force assign orders are forcibly assigned to the closest rider within the https //help hyperzod com/settings#tvfet without the option to accept/reject, ensuring swift allocation of deliveries max tasks per agent set the maximum number of orders a driver can handle simultaneously once this limit is reached, the system will halt sending or assigning new orders until ongoing ones are delivered task lock minutes after this duration, task statuses cannot be reversed, and final incentives are calculated and added to autozod reports note it is recommended to keep the task lock minutes value as low as possible so the driver can see their earnings for the task, and accordingly, the task reports can also be created for the order agent task accept seconds specify the time frame within which driver apps must accept order requests before they expire wakeup time for scheduled tasks (minutes) this setting defines how early a scheduled order is moved to the active task list from the scheduled list, so that the system can start assigning it to an agent for example, if an order is scheduled between 5 00 and 6 00 pm and the wake up time is set to 1 hour , the system first calculates the midpoint (5 30 pm) based on the wake up time, the order will move to the “all tasks” section at 4 30 pm , after which the system will begin assigning a rider note it is recommended to set the wake up time to 1 hour to ensure smooth assignment of scheduled deliveries auto assign re attempts these settings control how the system retries assigning a task when no agent accepts it, including how many times it should retry and the delay between each attempt auto assign retries it dictates the number of attempts the system makes to auto assign an order after initial failure, encompassing scenarios where no rider accepts the order within the time limit, all riders reject it, or when no available rider is found auto assign retry backoff set the waiting time before the auto assign retries restart order assigning radius this section helps you control how far the system should look for available agents when assigning a task task agent max radius (miles) it determines the distance from the originating store's location within this radius, the system searches for available agents to fulfill order requests