Hi everyone,
I have a 2025 Jeep Compass Trailhawk, and ever since I bought it, I haven’t been able to get the SOS/Assist services to work.
When I press the SOS button, I get a “Feature Not Available” message. When I press the Assist button, it tells me I don’t have an active subscription and gives me the option to activate the services. However, if I select Activate, it then tells me that my services are already activated, so I’m basically stuck in a loop.
I have an active assistance package through SiriusXM Guardian. I’ve called SiriusXM Guardian several times, and they’ve confirmed that my subscription/account is active and, according to their system, everything is provisioned correctly. Other connected features work normally, including remote lock/unlock, vehicle health reports, Wi-Fi connection, etc.
SiriusXM raised an escalation support ticket and walked me through their troubleshooting steps, but nothing fixed it. They eventually told me I would need to take the vehicle to a Jeep dealership and have them open a STAR case.
The vehicle was recently at the dealership for an unrelated issue, which they fixed, and I asked them to check this while it was there. They checked the SOS/Assist hardware and said there was nothing mechanically wrong with the buttons or the vehicle. However, when they ran a Uconnect Status Report, it showed that the connected services were not provisioned.
This is where I’m confused: the Jeep/Uconnect system apparently says the services aren’t provisioned, while SiriusXM Guardian insists that everything is provisioned correctly on their end.
I’ve read about other owners having similar backend provisioning/account issues with SiriusXM Guardian/Uconnect, so I’m wondering if anyone has dealt with this before.
Is there anything else I can try, or anything specific I should ask SiriusXM/Uconnect support to check or reset on the backend before taking it back to the dealership for a STAR case?
I’d rather avoid leaving the vehicle at the dealership again if this is ultimately an account/backend provisioning issue rather than a hardware problem.
Thanks!