HelloTracks

@HelloTracks show me the current locations of all field technicians on the downtown team with battery levels below 20%

Found 3 members matching your criteria: • Sarah Chen (Technician) - 37.7749°N, 122.4194°W (Mission District, San Francisco) - Battery: 18%, last updated 4 minutes ago • Marcus Johnson (Technician) - 37.7858°N, 122.4064°W (Financial District, San Francisco) - Battery: 12%, last updated 2 minutes ago • Elena Rodriguez (Technician) - 37.7699°N, 122.4469°W (Haight-Ashbury, San Francisco) - Battery: 15%, last updated 7 minutes ago All locations include elevation and movement telemetry. No device pings were sent to retrieve this data.

This example demonstrates real-time GPS tracking without draining field workers' batteries. Requires read access to member locations. Location freshness depends on the HelloTracks mobile app's background sync cadence—timestamps show when coordinates were last reported, not when they were requested. Useful for dispatch decisions but not for emergency response where second-by-second accuracy matters.

@HelloTracks create a new job for installing fiber at 450 Market Street, assign it to the next available technician on the North Bay team, and set the deadline for end of business Friday

Job created successfully: • Job ID: JOB-8472 • Title: Fiber installation - 450 Market Street • Assigned to: David Park (North Bay team, currently available) • Deadline: Friday, January 17, 2025 at 5:00 PM PST • Status: Scheduled • Place: 450 Market St, San Francisco, CA 94111 (matched to existing HelloTracks place) David will receive a mobile notification. The job is now visible in the team dispatch board.

This write action creates a job record and triggers a push notification to the assigned worker's device. Requires write permissions and assumes the place address exists in your HelloTracks account or can be geocoded. Assignment logic ('next available') is interpreted by the AI based on member status—verify the assignment matches your dispatch rules before the worker starts travel.

@HelloTracks pull all jobs completed in the last 7 days, group them by team, and draft a weekly summary highlighting any jobs that took longer than their estimated duration

Weekly Job Summary (Jan 8-14, 2025): **Downtown Team** (18 jobs completed) • Average completion: 2.3 hours per job • 3 jobs exceeded estimates: JOB-8401 (HVAC repair, 4.5h vs 2h est), JOB-8429 (electrical audit, 3.2h vs 1.5h est), JOB-8445 (plumbing emergency, 5h vs 3h est) **North Bay Team** (12 jobs completed) • Average completion: 1.8 hours per job • 1 job exceeded estimate: JOB-8438 (fiber install, 3h vs 2h est) Overall completion rate: 96.7%. Recommend reviewing scope estimates for HVAC and emergency jobs—actual durations consistently run 50-80% over plan.

This synthesis example pairs HelloTracks job data with AI reasoning to surface operational patterns. The AI calculates duration deltas and identifies trends across the raw job list. Accuracy depends on workers logging start/end times consistently in the mobile app. Use this for retrospective planning, not real-time dispatch—job status updates may lag by several minutes.

When HelloTracks wins for same-day service routing

A 12-person HVAC company runs three trucks doing emergency calls and scheduled maintenance. The dispatcher uses Switchy to pull current locations every 20 minutes, check job progress against the day's list, and route the next call to whoever finishes first. HelloTracks' Get Current Locations returns GPS plus battery and elevation without pinging devices, so the crew isn't interrupted. The dispatcher creates new jobs in HelloTracks through Switchy when a customer calls, assigns them to the nearest available tech, and archives completed work at end-of-day. This works because the team is small enough that one person can see all members and the job churn stays under 40 per day. If you're running 8+ trucks or need automated dispatch logic, you'll outgrow the manual coordination model fast. For teams at this scale, HelloTracks through Switchy turns location context into faster response without adding dispatcher overhead.

When real-time location sharing closes the customer loop

A landscaping crew of six handles residential jobs across two counties. The office manager uses Switchy to check job progress mid-morning and again at 2pm, then proactively texts clients whose appointments are running late or ahead of schedule. She lists today's jobs filtered by progress state, grabs current locations for the assigned members, and cross-references the job's place address to estimate arrival. HelloTracks doesn't auto-notify customers, so this manual check-in loop is the bridge. It works because the crew size is manageable and the manager already owns customer communication. If you're doing 20+ jobs a day or need automated ETAs, the twice-daily manual pull becomes a bottleneck. For small crews where personal client touch matters and job count stays predictable, this gives you location-aware customer service without building custom integrations or paying for a heavier platform.

When HelloTracks supports post-job documentation requirements

A four-person environmental consulting firm does site inspections that require timestamped location proof for regulatory filings. At month-end, the admin uses Switchy to list completed jobs, retrieve each job's details including timestamps and assignee, then pull the member's location history for that window to confirm on-site presence. HelloTracks keeps the GPS breadcrumbs; Switchy assembles them into a report the firm attaches to compliance submissions. This works because the job volume is low—maybe 30 inspections a month—and the audit happens in batch, not real-time. The API-key auth and archive-not-delete workflow mean the data persists for the required retention period. If you need live geofencing alerts or automated compliance flags, HelloTracks won't trigger them. For small teams doing periodic location-dependent work where the proof comes after the fact, this turns field tracking into defensible documentation without custom dev work.