Claims and boundaries
What we claim, and what we do not
Every capability on this site carries a state: live, closed beta, in verification, manual handling or on request. A state describes one named action against one named system, on a date. Where the evidence is incomplete, the page says so instead of rounding upward.
How a capability is labeled
The state attaches to an action, not to a platform. Supported, on its own, hides the difference between reading availability, writing an appointment, canceling one and taking payment.
| Live | Observed and supported for the named action. |
|---|---|
| Closed beta | Built and exercised in a controlled setting, not generally available. |
| In verification | Work is underway. Public capability is not established. |
| Manual handling | A person completes the work outside the automated path. |
| On request | There is no connector for that system yet. A request can be handled by hand, labelled as manual. |
Claims we do not make
We do not claim that WhatsDo works with every booking system, that booking is fully autonomous, that payment or cancellation runs through the agent path, or that an MCP connector is public or installable.
We publish no uptime, latency, rate-limit or certification figures, because none have been published for anyone to hold us to.
What a claim has to carry
A capability statement names the action, the system, the state and the date. A measurement carries its method, its sample and its limits.
When a vendor flag and our own product record disagree, the page says the status needs verification.
Customer proof
There is no named public case study, testimonial or merchant outcome on this site. The controlled merchant used for closed-beta work is a test account, and businesses that appear in research are research subjects.
When a case study exists, it will arrive with written permission and a provider-side record it can be matched against.
What to ask us
Four questions cut through most of it: which action, against which system, in which state, and what record proves it. If any answer is missing, treat the capability as unverified.
Sources
- Local record: WhatsDo capability states, product copy pack
- Local record: WhatsDo product lexicon and claim ladder
Proof before promise. A result is not claimed until there is a receipt.