Guide

Request a password from a Freshservice ticket

Stop passwords landing in ticket replies. Send a secure request from the ticket, and the password is destroyed when the ticket closes.

The problem

When a technician needs a user's password, it usually arrives in a ticket reply, an email or a chat message. It then sits in Freshservice's history, readable by anyone with access, long after the ticket is closed.

How it works with Freshservice

  1. Connect once. An admin connects Freshservice to SafeHanded with an API key.
  2. Request from the ticket. A canned response puts the request link on any ticket. The link carries the ticket number: SafeHanded looks the ticket up in Freshservice through that connection and fills in the requester's name, email and mobile.
  3. The user sends it safely. The password is encrypted in the user's browser to the technicians named on the request. A technician reveals it with their passkey.
  4. Close the ticket as normal. SafeHanded destroys the password and adds a private note to the ticket.
A SafeHanded request linked to a helpdesk ticket, with its spoken code, recipients and timeline.

Set it up

It takes about ten minutes and needs a Freshservice admin and SafeHanded's Team plan or above. The Freshservice setup guide in the docs has every step.

Try it

Hand over the next password properly.

Start on the free plan and send your first request, or read how the encryption works first.

Start freeSee how it works