Appearance
Identity Verification
Identity verification lets a technician confirm that the person on the phone is the ticket's requester before resetting a password, MFA method, or other account setting. From the ticket, send the requester a Duo push, a Microsoft Authenticator push, a text message code, or a voice call code. Junto ranks the methods by strength, guides you through what to say, and records the result on the ticket.
A verification is identity evidence, not authorization. It tells you who you are talking to; your MSP's own policy still decides whether an account change is allowed.
Phone Intake matches callers by phone number and name only; verify them here before changing their account.
Where to Find It
Verification works on tickets from ConnectWise PSA, Autotask, HaloPSA, and Syncro. Use it in the Junto ticket view, or inside your PSA from the ConnectWise Service Ticket Pod, the Autotask Insight, or the Junto tab in HaloPSA. A ticket needs a company and a requester contact.
- Verify requester -- The user-check button in the ticket chat's action rail opens the verification panel.
- Status pill -- The ticket bar (and the tab row in your PSA's Junto panel) shows whether the requester is verified: Not verified · Verify, Verifying with a countdown, Enter code, Verified with how long ago, or Denied / Fraud. Click it to open the panel.
- Identity checks -- In the Junto ticket view, the details drawer lists every check on the ticket, newest first, with who started it and its strength. PSA panels have no history list; the status pill reopens the latest check.
Every staff role from Technician up can start, cancel, and complete a check, and view trusted callback numbers. If your organization limits which companies a person can see, they can only verify requesters for those companies.
Before You Start
Each method needs its own connection. Methods that aren't set up for the ticket's company are listed in the panel under a collapsed section, such as 2 ways aren't available, each with its reason.
| Method | What it needs |
|---|---|
| Duo push | The Duo integration connected, the ticket's company mapped to a Duo subaccount, and the contact's email matching exactly one active Duo user with Duo Mobile activated. Your Duo Admin API application must be allowed to send verification pushes; see Duo's Admin API documentation for the permission name. |
| Microsoft Authenticator push | Either CIPP with the company mapped to a tenant, or Authenticator verification turned on in the company's Microsoft 365 settings (see below). The contact's email must match exactly one Microsoft 365 user. |
| Text a code / Call with a code | A phone number on file: a phone registered to the person in Duo, or the phone or mobile number on the PSA contact. Junto sends the codes itself; there is nothing to configure. |
Microsoft Authenticator Without CIPP
Admins and Owners can let technicians send Authenticator pushes through the company's own Microsoft 365 connection instead of CIPP:
- Go to Settings > Integrations > Microsoft 365 and find the company's tenant card.
- Under Authenticator verification, tick I understand the tenant's identity threat detection may flag this new credential.
- Optionally tick Use this instead of CIPP for this company. Otherwise this route is used only when CIPP isn't mapped.
- Click Turn on.
Junto adds a credential named "Junto end-user verification" to the tenant's Azure Multi-Factor Auth Client app and renews it automatically before it expires. The card shows when the credential renews next. Turn off removes the credential. Disconnecting Microsoft 365 for the company also turns it off.
Verifying a Requester
- Open the ticket and click Verify requester (or the status pill).
- Review the methods. The strongest available one is marked Recommended; pick another under Other ways if you need to.
- Click the send button: Send Duo push, Send Authenticator push, Text the code, or Call with the code.
- Follow the Say to the caller script in the panel. Never read a code to them.
- Complete the check:
- Duo push -- The requester approves the push, then reads you the code shown in it. Enter it in Code the caller reads back from the push and click Confirm.
- Microsoft Authenticator -- The requester approves the push. There is no code to read back.
- Text or call -- The requester reads you the code they received. Enter it in Code the caller received and click Check code.
Each check lasts 10 minutes, shown as a countdown. Codes allow 5 tries. Click Cancel to stop a check; a request already sent may still arrive, but a late approval never counts.
Strength
| Strength | Method | Why |
|---|---|---|
| Strong | Duo push with the code read back | Proves the person on the call holds the enrolled device |
| Moderate | Microsoft Authenticator push, or a Duo push approved without the code read back | Proves the device owner approved, but not that they are the caller |
| Basic | Text or voice code | Proves they have the phone, not who they are |
Results
Identity Verified
The panel shows Identity verified with the method, where it was sent, whether the code was read back, when, and who requested it. Use Copy summary to paste the evidence elsewhere, or Verify again to run a new check.
Denied or Reported as Fraud
If the requester denies the push or reports it as fraud, the panel shows what to do now:
- Don't change their account on this call.
- End the call politely; don't say why.
- Call them back on a trusted number, not one the caller gave you.
Click Show trusted numbers for callback numbers: the person's Duo-registered phones and PSA numbers that have been on file for at least 30 days. If there are none, reach the person through their manager or another known contact.
A fraud report, or three or more denials for the same person within 24 hours, posts a "Possible social engineering" alert to the channel routed to the Alerts slot (see Notification Channels).
Other Outcomes
Expired, Didn't complete, and Cancelled checks show the reason and Try again. Outcome unknown means Junto couldn't confirm the request was sent: if the person receives it now, ask them to deny it, and start a new check rather than accepting a late one.
Phone Numbers and Limits
- New PSA numbers wait 30 days. A phone number on the PSA contact becomes usable for codes and callbacks 30 days after Junto first sees it, and the wait restarts whenever the number is removed or added. Until then it is listed as This number changed recently. Usable from date. Numbers registered in Duo have no wait.
- Voice calls go only to supported countries; other numbers show Voice calls to this country are not allowed.
- One active check per person. Cancel the running check before sending another.
- Send limits per person: one check a minute, 5 an hour, and 15 a day, across all tickets. Your organization can send up to 200 checks an hour.
What Gets Recorded
- Ticket note -- Every finished check adds an internal note to the PSA ticket with the person, the result, the method and masked destination, who requested it, and a reminder that it is identity evidence only. Full phone numbers and codes are never written.
- Identity checks -- The ticket's history keeps every check.
- Alerts -- Fraud reports and repeated denials post to Alerts, as described above.
When the Agent Requests a Check
In the ticket chat, the agent can list the verification options for the requester (or another contact of the ticket's company) and request a check before an account change. A request always needs a person's approval: the approver sees who will be checked, the method, and the masked destination, and can't change them. After approval, a card in the chat tracks the check and takes the code the caller reads back. The agent never sees codes or full phone numbers.
These tools appear in your Tool Policies as List Requester Verification Options, Request Requester Verification, and Get Requester Verification Status. Request Requester Verification is always confirmed by a person: admins can raise its Minimum role or set its Approval to Escalate, but not to Automatic or Per session. The agent can request checks only from the ticket's own chat, not from Explore or unattended processing.
Evidence on Account-Change Approvals
Approval cards for a Duo user recovery, a CIPP password or MFA reset, or a Microsoft 365 password reset show the verification evidence for that ticket: who was verified, how long ago, by which method, and its strength. If no one was verified, or the change targets a different account than the person verified, the card says so. The evidence is for the approver's judgment and never blocks the action.
Troubleshooting
| Issue | What to check |
|---|---|
| Verify requester is missing | The ticket needs a company and a requester contact. |
| This ticket has no company | Assign the ticket to a company in your PSA, then try again. |
| No Duo user matches this contact's email | The contact's email must match exactly one Duo user in the company's mapped subaccount. |
| Map this company to a subaccount in Duo settings | Map the company under the Duo integration settings. |
| Connect CIPP, or turn on Authenticator verification in this company's Microsoft 365 settings | Set up one of the Microsoft routes described in Before You Start. |
| This number changed recently | The PSA number is in its 30-day wait. Use another method or a Duo-registered phone. |
| A check is already in progress for this person; cancel it first | Open the running check and click Cancel. |
| Wait a minute before sending another check or Too many checks for this person | A send limit was reached. Wait, or verify another way. |
| Didn't complete with no reason | The provider refused the request, for example because the phone doesn't accept pushes or the person has no Authenticator push set up. Try another method. |
| Authenticator verification shows a renewal error | Turn Authenticator verification off and on again on the company's Microsoft 365 card. Do the same if the company's Microsoft 365 is now connected to a different tenant. |
| The Azure Multi-Factor Auth Client app is disabled in this tenant | Enable it in Entra under Enterprise applications, then turn Authenticator verification on again. |