Value estimates

Value estimates is the daily job behind the Value tab in Governance. It estimates the time and money saved by your Coworkers' conversations recorded the previous day. See Value.

The switch#

Open Settings, then the Administration tab, and select Manage on the Features card. Value estimates has an Off and On switch under Behaviors. It is on by default.

Turning it off stops the daily estimates for your company. Estimates already made stay on the Value tab, and the tab remains available to people with the executive ability.

The daily schedule#

A job checks hourly and starts a run for a company when the previous UTC day is due. A run waits until two hours past midnight UTC so that late activity has been recorded, then handles exactly one day: every conversation exchange recorded that day that has no estimate yet. An exchange is recorded when its conversation moves on or is archived, so it may have started earlier than the day it is handled; its estimate counts toward the day it started. The last exchange of an archived conversation is included. Conversations started by automated runs are left out. A conversation whose text has been removed by conversation retention is recorded as skipped and shows in coverage as not estimated.

A company is skipped when Value estimates is off, Coworkers is off (see Features), or no usable model is set. A day that is interrupted, or that leaves some conversations with errors, is retried by a later hourly check. Exchanges recorded before the first run, or on a day that was missed because the deployment was down, are not caught up automatically; coverage on the Value tab shows the gap.

Each run also updates the stored totals the Value tab reads, and once a week records the recurring work types for the rate card.

Which model it uses#

Each conversation is classified with one small-model call, using your Default small model, or the company default model if that is not set (see Default models). With neither usable, the job skips your company until one is set. The conversation text is sent to your configured model provider, as in chat.

What it costs and the spending limit#

The cost appears under the system job value-attribution in the System jobs table of Usage and cost.

The job has no spending limit by default. To set one, turn Value estimates on in Settings > Administration > Features and enter an amount in Monthly spend limit (USD). Leave it empty for no limit; clear the field and save to remove a limit you set earlier. The amount is in US dollars, above 0, with at most 2 decimal places, and is counted over the UTC calendar month.

When the month's cost reaches the limit, the job pauses, the remaining conversations stay unestimated, and the Value tab shows "Estimates are paused: monthly spend limit reached. An administrator can raise the limit.". A call already under way when the limit is reached may take the total slightly over it. The pause clears at the start of the next month, or as soon as you raise or clear the limit. The right limit depends on how many conversations your people have each month, since there is one model call per conversation.

Environment variable#

One optional variable; see the Configuration reference. The spend limit is a setting on the Features page, not an environment variable.

Variable	Default	Meaning
WI_VALUE_ATTRIBUTION_SCHEDULER	dbos	dbos runs the hourly check. none removes the schedule entirely for every company, regardless of the switch.