Customer Bill of Rights
Six things we will not do to you.
Most of these exist because somebody in this market does the opposite, and it works on people who did not read the contract closely enough. Publishing them costs us the option of changing our minds quietly, which is the only thing that makes them worth reading.
- Unlimited users on every plan. We never charge per seat, per tech, per truck, or per portal user.
- Your data is yours. Export everything, any time, in open formats — including for 90 days after you cancel.
- An open, documented API and MCP server on every plan. Connect the AI and automation tools you already use.
- Payments are optional. Processing never unlocks a feature, and you choose the rail.
- Month-to-month by default; contracts only ever lower your price.
- Support response times in hours, not business days, published per edition, with a public changelog and status page.
Why this is a page and not a paragraph
A commitment buried in a pricing footnote can be moved. This list is the same list the application publishes to its own pricing surfaces, it is versioned with the product, and the sections below say where we currently fall short of it. If a right disappears from this page, that is a change you can point at.
What each one means in practice
Unlimited users, and nothing else counted per head
Elaborates: “per seat”
No charge per seat, per technician, per service truck, or per portal contact. This is the one that changes daily behaviour: when a login is free, the new hire gets one on day one, the tech clocks in properly, and the customer's dispatcher gets their own account instead of sharing the owner's.
Your data is yours, including on the way out
Elaborates: “Export everything”
Exports are in the core pack on every edition, in open formats, and they stay available for ninety days after you cancel. There is no fee for retrieving your own records and no retention conversation in front of it.
- Not shipped
Open access for your own tools
Elaborates: “API and MCP server”
A documented, permission-scoped API and a remote MCP server, on every edition rather than as an enterprise upsell, so the tools and AI your team already uses can work against your data with your rules applied.
Not shipped. There is no public API and no MCP server available to customers today; both are in build. Exports cover the same records in the meantime, and this right is why access will never be priced as an add-on when it lands.
Payments are optional and never a lever
Elaborates: “Payments are optional”
Processing through us never unlocks a feature, and you choose the rail. Keep your existing merchant account and record the payment if that suits you better — nothing in the product behaves differently.
Month-to-month by default; a contract only lowers your price
Elaborates: “Month-to-month”
There is no annual commitment required to get the published rate. Contracts exist, and they exist to reduce what you pay in exchange for volume you were going to do anyway — never to raise the cost of leaving.
Published support targets, a changelog and a status page
Elaborates: “Support response times”
Response targets stated per edition rather than described as fast, and public records of what changed and what is currently broken — so both are checkable by someone who does not work here.
Where these are binding
This page is the plain-language version. The commitments that carry contractual weight live in the Master Services Agreement, and where the two differ the agreement governs. If you find a place where the product contradicts this page, that is a bug report we want. Read the Master Services Agreement, or see what this costs.
Hold us to it.
These are easier to publish than to keep. If you find somewhere the product does not match this page, tell us and we will either fix the product or change the page.