[
    {
        "role": "user",
        "content": "when%20using%20remote%20incident%20manager%20and%20I%20am%20receiving%20help%20I%20am%20getting%20an%20erro%20saying%20the%20keyword%20isn%27t%20valid%20but%20it%20is%20the%20same%20keyword"
    },
    {
        "role": "assistant",
        "content": "The error you're seeing\u2014\u201ckeyword isn\u2019t valid\u201d when entering the same keyword in Remote Incident Manager (RIM)\u2014can be frustrating. Below are several likely reasons this happens, plus steps to diagnose and fix it. If you can share more specifics about your setup (OS, version of RIM, how it's installed), I can give more precise guidance.\n\n---\n\n## Possible Causes and Fixes\n\n1. **Install Mode / Role Misconfigured**\n   - RIM installs in two roles: *Target* (the machine receiving help) and *Controller / Technician* (the machine providing help). If a machine that should be acting as the Controller is installed in Target mode\u2014and vice versa\u2014you may see the keyword validation fail. ([pneumasolutions.com](https://pneumasolutions.com/it/remote-incident-manager-rim/?utm_source=openai))\n   - **Fix**: Check that you're running RIM in the correct mode. If you're \u201cproviding help\u201d, ensure you're in Controller mode under \"Provide Help Instead\" rather than Target/Keyword mode. ([pneumasolutions.com](https://pneumasolutions.com/it/remote-incident-manager-rim/?utm_source=openai))\n\n2. **Case Sensitivity or Typo**\n   - Although it may look like the same keyword, check for issues like leading/trailing spaces, uppercase vs lowercase letters, or similar characters like \u201c0\u201d vs \u201cO\u201d or \u201cl\u201d vs \u201cI\u201d. RIM may treat \u201cKeyword123\u201d and \u201ckeyword123\u201d as different. ([pneumasolutions.com](https://pneumasolutions.com/it/remote-incident-manager-rim/?utm_source=openai))\n   - **Fix**: Re-enter the keyword carefully, ensure it exactly matches, no extra spaces.\n\n3. **Self-Voicing or Screen Reader Prompt Confusion**\n   - In some setups, when a target is deployed by a technician, there\u2019s a *self-voicing prompt* that both reads aloud and shows the keyword. If the self-voicing prompt didn\u2019t work (e.g. due to accessibility settings or a missing screen reader), the user might mis\u2010understand or mistype the keyword. ([pneumasolutions.com](https://pneumasolutions.com/wp-content/uploads/2024/11/RIM-2022-whitepaper.pdf?utm_source=openai))\n   - **Fix**: Ask the technician to verbally confirm each character of the keyword, or use a different prompt method (visual + verbal) to ensure clarity.\n\n4. **Keyword Already in Use / Session Collision**\n   - If the same keyword is already in use for another active session, the system may reject it as \u201cinvalid\u201d to avoid overlap. RIM treats the keyword as a session identifier. ([pneumasolutions.com](https://pneumasolutions.com/it/remote-incident-manager-rim/?utm_source=openai))\n   - **Fix**: Choose a new, unique keyword\u2014not something generic that others might use.\n\n5. **Network / Configuration Glitches**\n   - If RIM can\u2019t check the keyword against its cloud or server backend because of a connectivity issue, or if the configuration isn\u2019t deployed properly, it may fail to validate the keyword. ([pneumasolutions.com](https://pneumasolutions.com/wp-content/uploads/2024/11/RIM-2022-whitepaper.pdf?utm_source=openai))\n   - **Fix**: Ensure the RIM app has internet/network access to reach the necessary services. If using an enterprise or private cloud installation, ensure your network or firewall rules allow communication with the RIM server or cloud.\n\n6. **Version or Deployment Type Specific Behavior**\n   - RIM has slight differences depending on whether it\u2019s configured for cloud or on-premises use, and depending on whether targets were preconfigured by the technician vs installed manually by the end-user. ([pneumasolutions.com](https://pneumasolutions.com/it/remote-incident-manager-rim/?utm_source=openai))\n   - **Fix**: If possible, ensure the target machine was deployed by the technician (pre-config mode), or check the deployment type and adjust how keyword is entered/prompted accordingly.\n\n---\n\n## Diagnostic Steps You Can Take Now\n\nTo narrow down the issue, try the following:\n\n- Verify the app is installed in the correct role (Target vs Controller). If you're providing help, make sure you selected \u201cProvide Help Instead\u201d after install. ([pneumasolutions.com](https://pneumasolutions.com/it/remote-incident-manager-rim/?utm_source=openai))\n- Reinstall RIM if you suspect the installation mode might be corrupted.\n- Use a simple keyword (e.g. \u201ctest123\u201d) to avoid character confusion, no spaces.\n- Check for internet connectivity on both ends (user and technician).\n- Try another device or network to see if the issue persists.\n- Read any error logs you have from RIM to see if there are more descriptive messages (sometimes access or permissions issues are reported in logs).\n\n---\n\nIf you want, I can guide you through exactly what to check in RIM based on your OS/version\u2014or help troubleshoot step-by-step. Do you know what version of RIM you're using, and whether it's cloud or on-premises?"
    }
]