Support

Install on a phone

On Android, install only the publisher-verified Fetch StormOps Google Play listing or use Install app from a supported browser. On iPhone, install only the publisher-verified App Store listing once it is available; until then, add the web app from the browser menu. Sign in with the exact invited email and its Fetch StormOps password; any email provider works. Google or Apple may also appear as optional sign-in methods for separately approved identities, and accounts are not linked merely because their email addresses match.

Location is not appearing

Fetch StormOps requests a one-time precise location when the authorized field map opens. If it does not appear, tap the location control and confirm that Location Services are enabled for the browser, installed web app, or Android Fetch StormOps app. Live tracking follows the device only while Fetch StormOps is open. Turning it off clears the saved team-presence coordinate, and stale live presence is cleared after approximately two minutes without an update. The Android app does not request background location or continuous background GPS; closed-app storm alerts work through Web Push instead.

Storm data is empty

Move or search the map to the area you want to inspect and make sure Storm pins is on. The map shows hail events at 0.75 inch or greater and wind events at 50 mph or greater from qualifying NWS reports and NOAA historical radar-hail signatures in the rolling 365-day window. Records automatically disappear after they age beyond that window. NOAA radar signatures at 1 inch or greater receive a hard one-mile geodesic qualification boundary. The star marks the episode's maximum-size radar-signature center, and the fill gets lighter with distance until that boundary. This fade is a distance guide, not a measured damage or hail-intensity swath. Address reports include hail at 0.50 inch or greater and wind at 50 mph or greater, and every point report, radar signature, and archived swath must be 1.0 mile or closer to the saved property coordinate. CoCoRaHS hail is scanned across the rolling year. Texas reports also check nearby TWDB TexMesonet 10-meter gusts using the limited recent history exposed by its public direct API; TexMesonet is wind evidence only. Preliminary point reports appear only when the NWS received and published an observation, while radar sizes remain estimates.

A pin or address needs correction

For a new property, search the address and choose its suggestion. Fetch StormOps automatically opens Satellite view and exact-pin mode because free address sources can return an approximate street position. Zoom if needed, then tap the exact roof. A directly dropped roof is saved without attaching a nearby-house guess; use the selected address or edit the property label to confirm it. Use Multi-pin mode when you need to mark several roofs: each point is queued and saved separately without reusing an address across homes. For an existing property whose dot is on the wrong roof, open it and choose Move exact roof pin. Confirm it is the same property and add a correction reason. Fetch StormOps moves the same record without changing its address, notes, photos, CRM history, follow-ups, or route references; coordinate-based storm evidence is cleared for a fresh scan. To correct only the label, edit the suggested address without moving the pin. In Fetch StormOps Settings, choose Automatic, Apple Maps, or Google Maps under Preferred maps app. Directions always target the exact saved coordinate—not the address text—and the pre-navigation safety check warns when the label resolves materially away from that roof point.

Download an address storm report

Open a saved property, run its Address storm report, then tap Download PDF. When a qualifying event is present, the report includes a satellite-street map with separate Property and Storm evidence markers, a measured connecting line, the straight-line distance in miles and feet, the bearing, and both endpoint coordinates. The measurement runs from the exact saved roof pin to the published point or nearest qualifying geometry used by the most-supported event; it is not a driving distance or proof that hail struck the structure.

Create a drone report

Open a saved property and look directly below Address storm report for the blue-topped Drone report card. Run and save the address report first, then open Build drone report and add JPG or PNG aerial images. Enter only observations you personally reviewed, confirm the inspection statement, and generate the company-branded homeowner PDF. The first report asks for the name the homeowner should contact; Fetch StormOps saves that name to the signed-in user and reuses it on that user's later reports. Every completed report freezes its selected photos and address-storm snapshot, includes the satellite-street map with a measured property-to-event line, and remains downloadable from the property record.

Navigate and work a door route

Build a route from Operations or Today's best doors. Knock mode shows the current stop, completed and skipped counts, remaining stops, and the next property. Tap Navigate to open the selected maps app. With live location on, Fetch StormOps exposes the doorstep actions automatically when the device is within the arrival area; otherwise tap I'm at the door. Record the required field note and outcome, and Fetch StormOps advances the route immediately with a Navigate next action for the following property.

Pin status colors

New pins start charcoal. Updating a property changes its map pin automatically: appointment set is green, follow up is amber, no answer is blue, not interested is red, and renter is purple.

Background alerts

Install Fetch StormOps from its verified Android release or add the web app to a supported Home Screen, then open Settings inside Fetch StormOps and enable Background alerts. Fetch StormOps uses host-browser Web Push on the web and in the Android Trusted Web Activity. Once the scheduler is connected, Fetch StormOps performs an unattended server sweep every five minutes for qualifying NWS warnings, recent hail and wind reports, radar hail signals, and due follow-ups—even when the app is closed. Lock-screen wording stays generic and does not reveal homeowner names, property addresses, notes, claim information, or a saved alert coordinate; open Fetch StormOps for full details. The 24/7 health card confirms the connection, shows the last successful sweep, and includes Check now and Send test alert controls.

Today's best doors

Tap See today's best doors on the map summary, then choose Route best doors. Fetch StormOps ranks eligible canvassing properties using saved storm results, confidence, roof age, follow-up urgency, and distance. Do-not-knock, renter, declined, appointment, and active pipeline records are excluded automatically.

Lead CRM and automatic follow-up

Open CRM in the mobile navigation or tap Lead CRM from the Opportunity Board. Every property marked Appointment set enters the CRM automatically, and inspection, claim, approval, contract, build, completion, and closed-lost stages remain together in one searchable record. Fetch StormOps creates the next workflow task as the lead advances, keeps overdue work at the top, and clears the active task only when the lead moves forward or is closed. A homeowner name and phone number are required before a new appointment can be set.

Create a professional evidence case

Open a saved property, run its Address storm report, then tap Evidence case. Fetch StormOps freezes the saved public-weather report together with the mapped point, most-supported event distance, source lineages, CRM position, inspection outcome, checklist, photo index, field notes, and activity history. The downloaded PDF carries a case ID and SHA-256 integrity reference that Fetch StormOps verifies before each download. It is an internal investigation record—not proof of roof impact, storm causation, coverage, or payment—and should be paired with a documented physical inspection.

Pilot proof and evidence calibration

Owners and administrators can open Analytics to review storm-scan reliability, median response time, report and evidence-case use, routes, appointments, and completed inspection outcomes. The black, green, and gold calibration cards compare each evidence tier with actual recorded roof findings. Homeowners who decline an inspection are shown separately and never counted as inspected. Early samples are labeled early; the results prioritize field learning and do not turn a weather event into a damage claim.

Company workspaces

Open Team to create, rename, or switch companies and branches. Each workspace has a separate roster, property database, storm settings, evidence cases, analytics, routes, and private photos. A signed-in account can join or own up to eight workspaces during the pilot. Owners and administrators create a single-use invitation link bound to the intended email. The link expires after seven days, stores no raw secret in Fetch StormOps, and rechecks the workspace seat limit when accepted.

Offline work and photo uploads

Pins, status changes, notes, doorstep outcomes, and compressed field photos can queue on the device while offline. Fetch StormOps uploads them after the connection returns and remaps photos to a newly synced property automatically. The Sync center shows anything that needs a retry or review. Removing a property or photo moves it to Recently Deleted for owner/admin recovery; permanently deleting the workspace removes its private photo objects and field records.

Account and data help

If a Fetch password is forgotten, use the Support page for operator-assisted identity verification and recovery. No automatic password-reset email is promised. Google or Apple account recovery remains with that provider when one of those optional methods is used. Account controls delete the member's complete Fetch StormOps identity across all companies, including its Fetch password credential and outstanding recovery records, memberships, saved presence, notification registrations, consent records, and direct identifying attribution. Retained company business records are deidentified, and a separate Google, Apple, or email-provider account is never deleted. An owner must transfer every owned workspace to an active administrator or permanently delete it after securing the required archive. Owners should keep a second active administrator on the roster. The account-deletion page explains the exact self-service and verified-support paths.

Contact Fetch StormOps support

Submit a request below if the documentation does not resolve the issue. The request is recorded in Fetch StormOps's private operator queue. Include the invited email and company name for access questions, but do not include homeowner or claim data.

Publisher and contact

Fetch StormOps is operated by The Cross & Company LLC.

Support: support@getfetchroofing.com · (470) 652-0023
Privacy and security: privacy@getfetchroofing.com