What your teams have to do
| Team | What we need | Effort |
|---|---|---|
| Device management / endpoint | Nothing. KnockAtlas installs from the browser — no app-store distribution, no MDM enrolment, no managed-app configuration. | None |
| Identity | SAML or OIDC metadata, and a group-to-role mapping, once SSO is enabled for your tenant | ~1 hour |
| Sales operations | A lead export, and the territory structure — regions, teams, and who owns which cities or ZIPs | Half a day |
| Security | Review the security page and the questionnaire response we return | Your normal process |
The endpoint row is the one that usually surprises people. Because there is no app to distribute, deployment does not queue behind a device-management change window.
Bringing your existing data
An organisation replacing a field-sales system is not starting from an empty map, and should not be asked to.
- Standard CSV exports import directly — business or resident name, address, contact details, disposition, owner, and history.
- Column names are matched flexibly. A file with
Business Name,company, orAccountlands in the same field without you renaming anything. - Address-only files work. Records without coordinates are geocoded on ingest.
- Large files are uploaded in resumable parts and processed as a background job — a six-figure import does not require a held browser tab.
- Every import is reversible. A load that goes wrong is undone as a unit, not row by row.
We will run your actual export through the importer before you commit to anything, and tell you what mapped, what did not, and what needs a decision. That is a pre-sales step, not a paid engagement.
Territory setup
The structure mirrors how field organisations already work, so it is a transcription exercise rather than a modelling one.
- Organisation owner creates regions and names a director for each, then assigns states.
- Region director creates teams inside the region, names each team's manager, and assigns cities.
- Manager distributes leads to representatives — by ZIP, by drawn area, or by percentage split of a city as contiguous turf.
- Vendor organisations sit alongside in-house teams in the same structure, so program-wide reporting does not require stitching two systems together.
Rollout
| Stage | What happens | Typical |
|---|---|---|
| 1 — Data | Your export is loaded into an isolated environment. You review coverage and field mapping. | Days 1–3 |
| 2 — Structure | Regions, teams, and territory ownership are configured with your sales-operations lead. | Days 3–5 |
| 3 — Managers | Managers are onboarded first, and assign turf before any rep signs in — so representatives arrive to a populated map rather than an empty one. | Week 2 |
| 4 — Field | Representatives are invited by email. Sign-in to first logged door is minutes; the interface is the map. | Week 2–3 |
| 5 — Reconcile | First reporting cycle is checked against what the field says happened. This is the step that decides whether a pilot succeeded. | Week 4 |
Training
- Role manuals are current and versioned — provided during onboarding, and always available inside the application.
- Administrator training is a single working session, included in the seat price.
- Representatives are not trained in a classroom. If a door-to-door seller needs a course to log a knock, the product has failed.
Support
- Email support, one-business-day response commitment.
- A named contact for the duration of a pilot.
- Incidents affecting the field are handled ahead of everything else, including sales.