Email corrections@fieldservicescout.com and it reaches Neil Lokare, Founder & Editor, who edits every page on this site. Corrections, platform submissions, press enquiries, licensing questions, and API support all go to the same address. We answer people, not tickets.
- One address for everything: corrections@fieldservicescout.com.
- Pricing and feature corrections are verified against the vendor's own published page, then the page is updated with a new verification date.
- We do not sell software, broker quotes, or pass your details to a vendor.
- For data access, use the free public API rather than emailing for an extract.
How to reach us
Email: corrections@fieldservicescout.com
Editor: Neil Lokare, Founder & Editor. Everything published here is edited by a named human — see about and methodology for who that is and how the scoring engine works.
We aim to reply within two business days. Corrections that come with a vendor URL are handled fastest, because verification is the slow part.
Reporting a wrong figure
Every price on this site is modeled from a vendor's own published plan page, and vendors change those pages without notice. A correction is most useful when it names three things:
- The page — the URL on this site showing the figure you believe is wrong.
- The figure — what we show, and what it should be.
- The source— the vendor URL that contradicts us. We verify against the vendor's published page, not against a claim, so this is what lets us act.
The same applies to capability rows. Field-service platforms ship features continuously, and a matrix cell that was accurate last quarter can be stale today. Tell us which capability, which platform, and where the vendor documents it.
Vendors and partners
Adding a platform.We consider any field-service management platform that sells to trade contractors and publishes its pricing. A public pricing page is a practical requirement, not a preference: this site models true cost, and a platform that quotes privately can only be represented as “custom quote”, which helps nobody reading a comparison.
What we will not do. We do not accept payment for placement, for a higher score, or for removal of an unflattering row. The scoring engine never reads commission status, which is why platforms we earn $0 from routinely outrank ones we earn on — see the affiliate disclosure for both lists in full.
Data, press, and API support
Figures on this site are citable with attribution. If you are writing about field-service software and want the underlying numbers, you do not need to ask: the whole catalog, the scoring engine, and the true-cost model are exposed through a free, unauthenticated API. See the developer and agent documentation, or fetch the OpenAPI document directly.
Email us if you hit a rate limit that blocks legitimate research, if an endpoint returns something the schema says it shouldn't, or if you need a bulk export the API cannot produce.
Privacy requests
To ask what data is associated with your session or email address, or to have it deleted, write to corrections@fieldservicescout.com and we will action it. What we collect and why is set out on the privacy page — the short version is first-party analytics with hashed IPs, and no selling or sharing of personal information.