Impact and methodology

How WelaOS counts AI impact.

The public counter uses source-complete production reports: booking records can come from COMPLETE or REVIEW_PENDING reports, while individual successful answers require COMPLETE status plus current report-metrics and assessment policies. Unavailable values stay unavailable.

01 / Impact and methodology

What qualifies as a successful AI booking record

The Analytics report counts a booking record only when all of the following evidence is present:

Canonical audit evidence attributes the booking record to AI creation.
The customer confirmation is accepted as a signed postback or verified typed confirmation.
The creation status is PENDING, AWAITING_DEPOSIT, or CONFIRMED. The recorded creation status takes priority over a later booking status.

What the booking metric leaves out

Staff-created or manual bookings, requests without direct AI creation evidence, bookings without accepted customer confirmation, unknown evidence, and creation statuses outside PENDING, AWAITING_DEPOSIT, or CONFIRMED do not count. A qualifying record can count while it is still pending deposit or approval.

Public aggregates only

The public endpoint returns only aggregate totals, coverage counts, and sparse UTC-day metrics. The landing counter shows these allowlisted aggregates without clinic or customer identifiers, cases, traces, or source details. Booking and answer metrics can be unavailable independently.

See the booking workflow