Common questions.

Forager uses RF fingerprinting. During a one-time Survey, a tech walks each room and stands still for 30 seconds while the app captures the ambient Wi-Fi and BLE environment — the unique pattern of signal strengths, access point identifiers, and Bluetooth devices visible from that spot. No two rooms in a building share the same fingerprint. After the survey, Forager continuously compares the live RF environment against that database and identifies the current room automatically. The app shows a confidence level alongside the room name — high, medium, or low — so techs know how certain the classification is.

Survey Mode is a one-time setup step where a tech walks the building and captures an RF fingerprint for each room. Stand in the center of the room, stay still for 30 seconds, confirm the room name, and move to the next one. An experienced tech can survey 15–20 rooms per hour. A typical 30-room floor takes 2–3 hours including pinning rooms to the floor plan. The Coverage screen shows which rooms are ready (green), which have weak signal quality (yellow), and which haven't been surveyed yet (gray). Surveys don't expire — but Forager flags rooms that haven't been refreshed in 90 days in case the RF environment has changed.

When a tech scans a barcode and the asset's recorded location doesn't match the room Forager has identified, it flags the scan as a mismatch. The tech can confirm the new location — which updates the CMDB record — or dismiss it if the asset is temporarily out of place. Either way, the event is recorded in the Attestation Log with full details: asset tag, expected location, actual location, tech name, and timestamp. Mismatches are one of Forager's most valuable compliance outputs — they surface CMDB drift that would otherwise go unnoticed until an audit.

Forager is HIPAA-ready by design, and a Business Associate Agreement (BAA) is available for covered entities and business associates. The architecture was built for regulated environments from day one — not retrofitted for compliance after the fact. MAC addresses are hashed before storage so raw device identifiers are never retained. Row-Level Security enforces strict tenant isolation so no user or administrator can access data outside their own organization. No personally identifiable information is collected beyond the asset records your organization explicitly defines. Every confirmation carries a full audit trail: who confirmed it, when, and where. Auditable exports are available on demand for compliance reviews.

Fast. Day 0–1: the IT admin creates the organization, builds the location hierarchy (Site → Building → Floor → Room), uploads floor plan images, and invites field tech accounts. Days 2–5: techs walk the building with Survey Mode to capture room fingerprints. After that, Presence Confirmation is the daily workflow — open the app, scan barcodes, done. No hardware purchases, no AP surveys, no network changes required before any of this.

CMDB integration is entirely optional — all of Forager's location features work without it. Floor plan visualization, presence confirmation, survey mode, the attestation log, and compliance exports all function independently of any CMDB connection. If you choose to connect, every presence confirmation can trigger an automatic POST to ServiceNow or any webhook-capable CMDB within seconds of the scan. In ServiceNow, Forager updates three fields on the CI record: current location, last verified timestamp, and the name of the tech who confirmed it. Setup takes under an hour using the Scripted REST API guide in our help center. No middleware required, no batch jobs, no manual entry. The webhook can be toggled off at any time without losing attestation records — confirmations continue to be stored in Forager and you can re-enable delivery whenever you're ready.

Forager Mobile runs on standard Android devices (Android 10+) with Wi-Fi and Bluetooth enabled — the phones your field techs already carry. No proprietary hardware, no dedicated scanners, no beacons required. Techs need cellular or Wi-Fi data access to sync confirmations, but the app works fully offline and queues records for later sync.

No. Forager runs on any Android 10+ device over any internet connection — cellular, home Wi-Fi, or a hospital guest network. There is no VPN requirement, no MDM enrollment, and no corporate network access needed to start. Most teams are up and running on their personal phones the same day they sign up. When your organization is ready to deploy on IT-managed devices, Forager goes through your standard enterprise app approval process like any other Android app — there is nothing unusual about how it is distributed or what network access it requires.

Zero trust in Forager means protection is enforced at every layer — not just at the perimeter. Device data is hashed before it leaves the mobile app. The cloud backend enforces Row-Level Security so each organization's records are completely isolated, even within shared infrastructure. No data is transmitted in plaintext. Access is governed by role and organization at the database level, not just the application layer. This posture was intentional from day one because our target customers — healthcare providers, financial institutions — operate in environments where a data exposure is a regulatory event, not just a liability.

Yes. Forager Mobile stores confirmations locally and syncs reliably when connectivity is restored. Techs can run full Presence Confirmation sessions in basement equipment rooms, shielded areas, and loading docks without losing any work. Room classification also works offline — the RF fingerprint database is cached on the device.

Under five seconds. The tech opens Presence Confirmation — Forager has already been identifying the room in the background. They scan the barcode. The confirmation is written. That's it. The Attestation Log updates immediately. If a ServiceNow webhook is configured, the CI record updates within seconds.

Most deployments start on one floor or department over the first 4 weeks. Week 1: account setup, location hierarchy, survey. Weeks 2–4: field techs run Presence Confirmation as part of normal IT work. We track rooms surveyed, assets confirmed, mismatch rate, and — if ServiceNow is connected — CI record update fidelity. At the end of the first month you have real operational data: how many mismatches were caught, what the confirmation rate was, and how much time the workflow actually takes per tech per day. That data drives the case for scaling facility-wide.

The Attestation Log in the app shows the full confirmation history filterable by type (match, mismatch, new asset). The web dashboard Reports page provides date-range exports for auditors — every record shows asset tag, location, tech, timestamp, and confirmation type. Reports can be exported as CSV. The Signal Diagnostic feature generates a shareable HTML snapshot of the live RF environment on demand, useful for demonstrating classification accuracy to auditors or stakeholders.