Resolving a GPS tracking issue may require the support team to review protected account information, such as device settings, status, or the data needed to diagnose why a tracker stopped reporting. To ensure that this assistance occurs only with the account holder's authorization, ALTAGAMA GPS added an identity verification step for support requests.
The new workflow uses a temporary six-digit code sent to the registered email address. The customer decides whether to provide it during the support session, and the support team can proceed only after it has been verified. This adds direct confirmation before protected information is reviewed.
How ALTAGAMA GPS support verification works
Verification begins when an authorized agent needs account information to handle a request. ALTAGAMA GPS does not open the data automatically. It first presents the authorization request and sends a code to the email address associated with the user.
- The customer starts or confirms a support request.
- The agent requests an authorization code for the relevant account through ALTAGAMA GPS.
- ALTAGAMA GPS sends a six-digit code to the registered email address.
- The customer checks the message and provides the code to the agent handling the case.
- The agent enters the code on the verification screen.
- If the code is valid, ALTAGAMA GPS grants temporary access so the diagnosis can continue.
If the code is incorrect, expired, or unrelated to the request, the information remains protected. Another code can be requested when necessary, but access always depends on successful verification.
What this security measure protects
A tracking account may contain locations, route history, device information, alerts, and operating settings. That information should not be reviewed during a support interaction without a valid reason and the account holder's knowledge.
Verification connects the support session with an action the customer can recognize in the registered inbox. Even if another person knows the username or tries to request information, that person still needs confirmation through the registered channel.
Authorization is temporary and limited to the support workflow. It does not reveal the customer's password, change account credentials, or make access permanent. After the authorized window ends, another review may require a new verification.
How it helps diagnose a GPS tracker
When a tracker goes offline, reports unexpected positions, or does not generate an alert, support must distinguish among several possible causes: device power, coverage, communication settings, account assignment, or interpretation of received information.
After receiving authorization, the agent can review the ALTAGAMA GPS elements related to the case and guide the customer with better context. This can reduce unnecessary screenshots and avoid diagnosing the problem from an incomplete description alone.
Verification does not replace physical tests. The user or installer may still need to check power, antenna, SIM card, coverage, and tracker commands. Its benefit is controlled access that lets support compare those checks with the information available in the platform.
A real-world authorized support case
A company notices that one vehicle has stopped updating its location. The manager opens a request and identifies the affected tracker. When the agent needs to review the account, ALTAGAMA GPS sends a six-digit code to the registered email address.
The manager confirms that the support session is legitimate, gives the code to the agent, and temporarily authorizes the review. Support can then verify the visible device status, review the necessary information, and guide the field technician through the next steps.
If checking power or adjusting the tracker configuration resolves the issue, the customer has a clear sequence: request, authorization, diagnosis, and action. If the case must be escalated, the collected context helps the next review begin with more precise information.
Benefits for companies and users
- Account holder control: the customer participates before support reviews protected information.
- Lower impersonation risk: knowing an email address or account detail is not enough to authorize access.
- Limited access: authorization is granted for a temporary period rather than indefinitely.
- Context-aware diagnosis: the agent can review the required ALTAGAMA GPS information after permission is granted.
- Traceability: the support request is recorded as part of the service process.
- Understandable workflow: customers know why they received the code and what it authorizes.
Recommendations for using the code safely
A support code should be treated as a temporary authorization. Before sharing it, customers should confirm that there is a support session initiated by them or by an authorized person in their organization.
- Confirm that the request matches the case you are handling with ALTAGAMA GPS.
- Check that the message arrived at the registered email address and refers to support verification.
- Give the code only to the agent participating in the official support conversation.
- Do not share the account password; verification does not require disclosing it.
- Reject unexpected requests and contact ALTAGAMA GPS directly if you receive a code you did not request.
- Request another code if the previous one expired, was exposed, or the session restarted.
A legitimate agent can explain why authorization is required and which part of the case will be reviewed. The code should not be used to pressure a user or request information unrelated to the support case.
Verification and permissions in an organization
Companies with several users should define who may request support and who controls the registered inbox. This prevents delays when a vehicle needs attention and helps ensure that authorization comes from a responsible person.
Account permissions still determine which devices and tools each user can access. Support verification adds a specific layer for customer service; it does not replace user, group, and permission management within ALTAGAMA GPS.
A useful fleet practice is to keep the account holder's email current, document who is responsible for support requests, and record the reason for each session internally. The organization can then respond quickly without reducing control over its tracking data.
ALTAGAMA GPS features related to technical support
ALTAGAMA GPS combines real-time maps, route history, alerts, geofences, reports, and compatible tracker status. When a question arises, the help center provides procedures, and the support team can assist when an additional review is required.
The new verification connects those support channels with explicit authorization. Its purpose is to let a technical case move forward without normalizing open or indefinite access to customer information.
Technical summary for security and IT teams
- A request to review protected information requires a verification action first.
- The code contains six digits and is delivered to the user's registered email address.
- Successful validation grants temporary authorization associated with the account and support agent.
- Invalid or expired codes do not grant access, and a new delivery can be initiated.
- The support request is recorded to preserve process traceability.
- Verification complements existing permissions and does not change the customer's password.
Explore GPS tracking, alerts, history, and reporting tools in the ALTAGAMA GPS plans and features.