The requests belong to your company. So does the access.
Zelo holds your warehouse's requests, catalogue and operating history. Each company's data is kept apart from every other, access is by invitation only, and the roles that administer or pick require two-factor authentication.
Two-factor authentication required for anyone who administers or picks
A password alone isn't enough for an account that changes the queue, the catalogue and the operating rules. Two-factor authentication is required for management and warehouse manager roles and available to every account.
Required for administrative roles
Enforced for the management and warehouse manager roles. Every other account can turn it on from its own profile.
Authenticator app
A short-lived code from an authenticator app is required on top of the password. Codes expire after 30 seconds and can't be reused.
Recovery codes
Recovery codes are generated when two-factor authentication is set up, so access isn't lost when the phone isn't at hand.
Trusted device, for a limited time
If your company enables it, a trusted browser can be remembered for up to seven days. After that, the code is asked for again.
Your data stays yours — kept apart from every other company
Your company's requests, catalogue and team are visible only to the people you invited.
Separated by company
Every query is scoped to your company. No other account on the platform can reach your requests, your catalogue or your team.
Roles in the operation
Engineers, warehouse staff and management see and do what their role allows, and every alert respects the access the person has at that moment.
Removal takes effect immediately
When you remove someone or change their role, their access to requests and alerts changes on the very next request.
Invitation-only access
New users join only by invitation from one of your company's administrators. There is no open sign-up or self-registration.
A history that tells what happened — not what someone remembers
Every request keeps when it was sent, how far ahead, under which rule and which statuses it went through.
Rule recorded on submission
The minimum window and cut-off in force at submission are stored with the request. Changing the settings later doesn't rewrite how older requests were classified.
Protected status changes
If two people change the same request at once, the second is told it has already changed instead of silently overwriting the first.
No duplicate requests
A double click or a flaky connection doesn't create the same request twice, send repeated alerts or use up the plan twice.
Message processed, content erased
For WhatsApp requests, the content of each message is deleted once processed, and an unfinished request is deleted about 30 minutes after the last message. For AI reading, Zelo doesn't send phone numbers, user names or the company name, and Anthropic, which provides the model, may not use that data to train AI. Every AI proposal is checked and confirmed by the engineer before it becomes a request.
