For your fleet
Choose your setup path
Check tracker compatibility and the plan before you activate vehicles.
Workspace fit
Island supply notes keep SHP invoice, dashboard ownership, and first fleet units separate from device questions.
Account
- Name the workspace owner, summary recipient, approval currency, and first fleet group.
- Keep plan price separate from device model, SIM state, and field-service questions.
Device proof
Jamestown ladder routes, Saint Helena approvals, and Half Tree Hollow loops give support enough context to review model fit and SIM status.
Tracker
- Attach odometer photo, current provider, device protocol, and employee-notice language.
- Use public works mileage to avoid mixing dashboard labels with legal or HR advice.
Summaries to inspect
Airport ridge trips, harbor crane windows, and runway service ledgers should become trips, zones, summary labels, or exception notes after onboarding.
Reports
- Review trip history, geo-zone alerts, and activity summaries before expanding the fleet.
- Use radio room logs and cliff road cautions to spot recurring stops, delays, and exceptions.
Before you connect
Before you connect, note ship day exceptions and water bowser routes so you can compare them with trip history once your trackers report.
Checklist
- Have each tracker's IMEI and SIM ready. Traxelio checks the model from the IMEI.
- If you already own trackers, connect them before you compare the software plan.
Operating context
Common Challenges
-
Workspace scope
Saint Helena buyers should name the invoice owner, dashboard language, and first fleet group before connecting their trackers.
-
Jamestown records
Keep Saint Helena approvals, public works mileage, and radio room logs attached to vehicle records so support can read the operating pattern.
-
Support limit
Traxelio can review software fit and existing device proof; local stock, fitting, and carrier network reach remain unconfirmed.
Traxelio Solutions
-
SHP workspace assessment
Use island supply notes and cliff road cautions to decide who owns invoice, who receives summaries, and which fleet units should appear first.
-
Device proof
Connect each tracker by IMEI before onboarding; Traxelio checks the model, then you check the SIM.
-
Summaries to inspect
Map airport ridge trips, harbor crane windows, and runway service ledgers to trip history, zones, and activity summaries after the workspace is configured.
Cities
GPS Tracking in the cities of Saint Helena
Find GPS tracking services in the major cities of Saint Helena.
FAQ
Frequently asked questions
Start with Jamestown ladder routes, airport ridge trips, and harbor crane windows. Those records make the workspace question concrete before equipment or fitting is discussed.
Connect each tracker by IMEI; Traxelio checks the model, then you check the SIM. Plan employee notice before your trackers start reporting.
Compare plan price after island supply notes confirms the buyer, invoice currency, summary recipient, and first fleet group.
Keep cliff road cautions, ship day exceptions, and water bowser routes as notes for naming zones and reading trip history. They do not confirm network reach or emergency service.
Use Saint Helena approvals for route exceptions, radio room logs for service windows, and runway service ledgers for recurring stops before reading activity summaries.
Name zones from real operating labels such as Half Tree Hollow loops, ship day exceptions, and water bowser routes, then keep alert thresholds separate from payroll or discipline decisions.
Traxelio can review workspace onboarding, device compatibility, trip history, geo-zone alerts, and summary recipients once your trackers are connected.
For Saint Helena, connecting first shows whether Traxelio recognizes the tracker you already own: enter its IMEI, Traxelio checks the model, then you check the SIM.
Document the normal day in plain operational language: Jamestown ladder routes starts the shift, airport ridge trips explains the planned movement, harbor crane windows names the fleet group, and Saint Helena approvals shows where timing breaks down. Add public works mileage for employee notice, radio room logs for the service window, island supply notes for invoice ownership, and cliff road cautions for the first summary recipient. Keep Half Tree Hollow loops, runway service ledgers, ship day exceptions, and water bowser routes as supporting notes so the onboarding conversation stays about real fleet units, not a broad market assumption.
Read the first summary against the buyer's own labels. Jamestown ladder routes should show start time and return time; Saint Helena approvals should show delay reason; radio room logs should show whether the stop was planned; Half Tree Hollow loops should show the zone name; runway service ledgers should show recurring movement; ship day exceptions should show who approved the exception; water bowser routes should show whether the same issue repeats. If those fields are missing, collect them before adding more fleet units.
Each local detail here names your own records; none of them is a service promise. Harbor crane windows and public works mileage help name the dashboard and notice language, but they do not create legal advice. Island supply notes and cliff road cautions help name invoice and report owners, but they do not promise local support. Half Tree Hollow loops, runway service ledgers, ship day exceptions, and water bowser routes help you read routes once your trackers are connected.
Tracking employee vehicles? See if GPS tracking is legal for employee vehicles
Ready to track your fleet in Saint Helena?
Connect the GPS tracker you already own, or check GPS tracker availability.