Why OglutTicket has no passwords
There is no password selection screen anywhere in the product. The reason is not convenience: with password recovery, the email inbox is already the master key — the password is a second lock on the same door.
Published by Oglut Srl, publisher of OglutTicket.
OglutTicket does not ask people to create a password. Staff members sign in with an email address and a six-digit code delivered to that inbox. Customers using a public request receive a protected link after verifying their email.
The inbox is already the recovery key
In a conventional password flow, a forgotten password is reset through email. That means control of the inbox can already unlock the account. Adding a password often adds a second secret to store and reset without removing email from the trust chain.
What passwordless access improves
- No password database exists to leak or reuse elsewhere.
- New agents do not need to choose another company password.
- Former staff cannot keep using a shared team password.
- Customers do not face password recovery before asking for support.
What it does not claim
An emailed code is a single factor. It is not stronger than well-configured multi-factor authentication, and its security depends on the recipient’s email account. The design goal is a smaller, explicit access model—not a claim that email alone solves every authentication risk.
Read the broader security and privacy model, then see how customers submit requests without creating accounts and how a simple ticketing system reduces setup for agents too.