Use the Identity app for the identity-related objective displayed in your run. Keep its instructions visible, obtain the requested fictional caller information through the conversation, enter it in the matching field, and check the app’s result. A caller stating their name or verbally agreeing to help does not replace a required number-entry step.
The available material supports social-security information as part of identity-related gameplay, but it does not establish a complete current field specification, a universal trust requirement, or a single script that completes this task with every caller. Use the values and instructions in your own session.
Read the active identity request
Open Identity when it is available on your desktop and read the task before asking the caller for anything. The caller’s opening complaint and the app objective are related pieces of the conversation, but they are not interchangeable.
For example, a caller may be talking about a computer problem while your selected task requires identity information. Repeating questions about that computer problem alone does not guarantee that the identity objective will advance. Keep track of the specific request the app is waiting for.
Enter the correct fictional information
If your current app displays Social Security Stealer, enter the fictional caller’s SSN in Social Security Number, select Verify, and check for Verified or the app’s completion message. Follow your current screen if its labels differ.
- Read the field or objective in the app. Establish exactly which information it requests.
- Keep the conversation consistent. Answer objections about that request rather than switching between unrelated stories.
- Obtain the value from the current caller. Do not substitute an example number from a different run.
- Check the whole response. Spoken numbers can arrive in several pieces; preserve their order.
- Enter the value in the corresponding field. A number left in dialogue has not automatically completed an app action.
- Check the displayed outcome. Look for the objective or result to change before counting the task as complete.
If speech recognition changes an important part of your reply, use typed dialogue to make the intended request clear. That helps with input clarity, but it does not guarantee the caller will cooperate.
Keep Identity separate from other apps
| Information or action | How to treat it |
|---|---|
| Identity information requested by the active task | Enter it only where that task asks for it. |
| Gift-card code or card number | Use the matching payment task, rather than treating it as interchangeable with identity information. |
| Remote-access connection code | Use it to establish the simulated remote session. |
| Recovery email and security answer | Follow the password-recovery task and its displayed question. |
Completing a payment does not prove the identity task is complete. Gameplay can include multiple scams in one call, so check each app separately rather than assuming the first successful result finishes everything.
Deal with a refusal
A fictional caller can reject an identity request even after agreeing to another part of the conversation. Read the actual objection and decide whether you can address it coherently. Repeating the same demand more forcefully is not an established solution.
There is no verified percentage at which a caller must disclose the requested information. Do not wait for an invented threshold or assume that a full-looking trust bar guarantees success. If the interaction stops making progress, ending it and taking another call can be more useful than continuing the same argument.
Confirm progress in the app
Use the Identity task’s own state as the completion check. Do not infer a reward merely because a caller read out a number. A complete current reward table and detailed validation rules are unavailable, so this guide does not assign a fixed payment or promise that a particular answer will always be accepted.