Generic field-service software gets radon wrong in the same four places.
Every one of these is a rule in RadonCRM, not a note in the appointment description. The booking is refused before it reaches your calendar.
- A test is two appointments
- Book a short-term test and the placement and pickup visits are both created, linked to one job. Nobody has to remember the second half.
- 2 visits
- The kit needs time to sit
- Pickup cannot be scheduled inside the minimum exposure window — from the public form, the widget, the API or the office.
- 48 h
- An install eats the day
- Mitigation runs at a fixed start with a per-day cap per crew. Two crews mean two installs; one crew means one.
- 1 per crew
- A result is a decision
- Readings are compared to your action level and the job lands in Mitigation needed or No mitigation needed. No spreadsheet in between.
- 200 Bq/m³
142 Bq/m³
Under the action level. Closed as no mitigation needed.
410 Bq/m³
Over. Flagged for mitigation, quote started from the same job.
Moving off a general-purpose tool
| The task | Generic scheduling software | RadonCRM |
|---|---|---|
| Short-term test | Two unrelated appointments, booked by hand | One job, both visits, linked |
| Exposure window | A sentence in the notes | Enforced before the booking is accepted |
| Install capacity | Any number of all-day jobs per day | Fixed start, capped per crew, per day |
| Test result | A number in a custom field | Measured against the action level, bucketed for follow-up |
| Signed quote | Download, re-enter into accounting | Signed PDF, draft invoice, install link, automatically |
| Website booking | A contact form in your inbox | A real job on the crew's calendar |