# Hand out passwords without leaving a trail

> IT helpdesks use temp.cool to send temporary passwords, logins and keys as one-time links, so credentials never sit in tickets, inboxes or chat history.

1. **Password resets** Send a temporary password that's gone before the ticket is closed.
2. **New hires** First-day logins without leaving them in onboarding emails.
3. **Vendor credentials** Hand an API key to a supplier without it living in their inbox.

## The problem with tickets

Helpdesk tickets are searchable, exported, and read by many people. A password typed into a ticket reply lives there for years. The same goes for email and team chat.

## How teams use temp.cool

1. The agent resets the password and pastes it into temp.cool, set to open once and expire within a day.
2. The link goes into the ticket reply or chat instead of the password.
3. The user opens it, logs in, and sets their own password. The ticket now holds only a dead link.

The agent's manage link shows when the secret was opened, which helps when a user says they never got it.

## Good to know

- Nothing to install, no accounts for users.
- Encrypted in the browser, stored in the EU, gone after reading.
- Link previews in Teams, Slack or email scanners can't burn the message.