PD Support PIN gives clients a short PIN they can read to your support team. Staff check the PIN against the selected client account and receive a match or no-match result, without needing to reveal the stored PIN.

This gives your team a consistent account-checking step during a call. A match confirms that the supplied PIN matches that account; it does not establish the caller’s identity on its own or authorise every requested account change.

What the client sees

With the client-dashboard panel enabled, the client signs in to their WHMCS client area and finds Support PIN on the home page. They can read that PIN to your team when asked.

If you allow clients to regenerate their own PIN, the panel also gives them a way to replace it. Staff should check the PIN the client is currently viewing rather than an older value copied into a previous conversation.

What your team does

1. Open PD Support PIN → Verify.
2. Select the client account involved in the request.
3. Ask the caller for the PIN shown in their signed-in client area.
4. Enter the value they provide and check the result.

Verification compares the supplied value without displaying the stored PIN. If the result is no-match, confirm that the correct client account was selected and ask the client to check their current PIN. Follow your normal account-verification process if the check still does not match.

The module also provides an in-context Support PIN row on the client’s admin Summary page. When enabled, the ticket-view panel lets staff check the PIN while working on that client’s ticket.

Settings to review before your first check

Install PD Support PIN through the PD Modules panel, then open PD Support PIN → Settings. Review these choices for the workflow you want:

• Show the PIN on the client’s dashboard makes the PIN available in the signed-in client area.
• Hide the PIN until clicked (reveal-on-click) masks it in staff panels. Blind verification does not require revealing it.
• Let clients regenerate their own PIN controls whether clients can replace it themselves.
• Regenerate the PIN after a successful verification changes it after a match when enabled. Leave it off if you want the same PIN to remain available until another regeneration or rotation.

On Staff access, choose which staff roles may reveal and regenerate PINs. Other roles can still check the value a caller supplies. This separates caller checking from permission to view or replace the stored PIN.

Check your workflow

Before introducing the process to your team, use a test client account you control. Confirm that the dashboard panel is visible, that a correct PIN produces a match and that an incorrect value produces no-match. Review the Activity tab to see the recorded checks.

Keep PINs out of public screenshots and avoid copying them into tickets. If a PIN has been exposed, regenerate it using the controls available to the client or authorised staff.

Explore PD Support PIN for WHMCS for the module details. Plan which roles should verify callers and which should also be able to reveal or regenerate PINs.

Support PIN task guides

• Find and regenerate your Support PIN in the WHMCS client area
• Let staff verify Support PINs without revealing them in WHMCS
• Configure Support PIN rotation and one-time mode in WHMCS
• Connect a helpdesk or phone system to the Support PIN API in WHMCS
• Fix a Support PIN no-match or rate-limit result in WHMCS