Monitoring and Phone Agent troubleshooting
Rshift monitoring tracks brand status across platforms, AI visibility, accounts, and tasks. Phone Agent is used for workflows that require a phone environment.
Common monitoring issues
Source account is disconnected or lacks permission.
Task is paused or queued.
Provider data is delayed.
Keywords, accounts, regions, or source configuration are incomplete.
Phone Agent is offline, missing permissions, or outdated.
Phone Agent installation notes
APK files must only be distributed through an authenticated admin API or short-lived enrollment code.
Do not download APKs from public static links.
After installation, confirm device online status, foreground service permission, notification permission, and network connectivity.
If a device fails, check enrollment and device status in Rshift admin.
When contacting support, share monitoring task id, platform/source account name, device id or enrollment code suffix, and visible status or error code. Do not send APK files, vendor credentials, raw monitoring data, or sensitive device logs.