Assign a defined role
Introduce an AI worker for a specific operational responsibility. Explain its identity, permitted actions and the work it is expected to handle.
AI WORKFORCE
Put AI to work.
Keep people in control.
Delegate defined operational tasks to AI workers and keep human judgement where it matters. Follow a care worker handling a shared task queue, recording its actions and escalating cases that require a person.
Opens an editable email draft. No request is sent or meeting reserved.
AI WORKFORCE DEMONSTRATION
See an AI care worker handle the queue.
Watch an operator assign a care worker, follow three example cases and review task outcomes alongside measured AI model spend.
Demonstration environment with example care cases. The updated recording shows BSS-measured AI model spend separately from worker-reported cost. Time-saved figures remain estimates. Supported tasks, permissions and controls depend on the configured workflow.
Read the descriptive walkthrough
This descriptive walkthrough summarises the visible demonstration and on-screen captions. It is not a verified audio transcript.
00:00–00:25 — The operator opens AI Workforce. Three care cases are in the backlog. Measured AI cost and self-reported AI cost appear as separate counters.
00:25–00:55 — The operator names and hires a care worker. A crew ceiling of one and a worker spend ceiling of five US dollars are visible. The captions describe the worker’s identity, role permissions and use of the BSS for model calls.
00:55–01:35 — The worker processes the queue while measured AI model spend increases. The recording distinguishes completed work from cases escalated to people.
01:35–02:05 — One case is completed and two are escalated. The ledger records a customer-confirmed resolved issue, a fibre fault requiring human investigation and a duplicate-charge case whose payment is not identified. Time saved is labelled as an estimate.
02:05–02:20 — The screen shows measured AI model spend separately from self-reported cost. The captions describe BSS measurement call by call using the model provider’s reported usage, and a worker spend ceiling. The recording does not show the ceiling being reached or a worker being stopped.
02:20–02:40 — The duplicate-charge case requires a person to locate the payment. The care worker cannot view payments and does not guess or execute a refund.
02:40–03:01 — The customer support view shows the resolved issue with a note and the fibre and refund cases still awaiting further handling. The closing captions distinguish work delegated to AI from spending and financial decisions controlled by people.
Handle work and escalate
Follow the care example as the worker completes a supported task and escalates cases it cannot resolve or authorise.
Review the activity
See completed work and escalation reasons in the activity ledger. Review measured AI model spend separately from worker-reported cost, so the work and its model cost can be assessed together.
A CONCRETE OPERATIONAL EXAMPLE
Three cases. Different responsibilities.
The recording illustrates how different care situations can lead to different outcomes.
- A resolved issue
The customer reports that the issue is fixed and requests closure. The worker closes the example case with a note.
- A fibre fault
The worker escalates the case for human handling rather than treating the network problem as resolved.
- A duplicate charge
The worker hands the case to a person because the payment is not identified and its care role cannot view payments. A person must find the duplicate charge and decide any refund.
These are demonstration outcomes, not a guarantee that all care cases can be automated. Confirm the supported tasks, evidence requirements and escalation path for the selected workflow.
IDENTITY. PERMISSIONS. OVERSIGHT.
Define the responsibility before delegating the work.
Agree which tasks an AI worker may handle, which actions it may propose and when it must hand work back.
Role and access
Validate the worker identity, role permissions and data access needed for the intended task. A worker should operate within the agreed access boundary.
Checks and decisions
Agree task-completion checks and approval requirements. In this recording, the worker escalates the duplicate-charge case; finding the payment and deciding a refund remain human responsibilities.
Capacity and escalation
Set workload and worker spend ceilings alongside hand-off responsibilities. The recording shows these controls, but does not show a worker reaching a limit and being stopped.
MEASUREMENT WITH CONTEXT
Measure the result in your operating context.
Start with a defined task and establish the baseline, outcome data and review process before making productivity claims.
Task outcomes
Review completed work, reopened cases and escalation reasons. Check that the outcome meets the requirements of the task.
Operational effort
Compare the effort to handle the agreed workflow, including human review, exceptions and follow-up.
Measured model spend
Review AI model spend measured by the BSS, displayed separately from the worker’s own cost report. The recording describes call-by-call measurement using the model provider’s reported usage. Confirm the pricing, coverage and reporting for your deployment.
The worker spend-ceiling control makes budget part of the operating setup. The recording does not demonstrate the ceiling being reached. Model spend is one part of operating cost; estimated time savings and demo counters do not establish production savings.
CONNECTED TO RUN. GROW. LEARN.
Different kinds of assistance. One commercial platform.
Choose the form of assistance that fits the work.
Product Copilot
Helps a person describe and prepare an offering for review and creation.
Watch Product Copilot →Marketing & Sales
Helps prepare commercial initiatives around audiences, propositions and customer journeys.
Explore Marketing & Sales →AI Workforce
Handles assigned operational tasks within the supported workflow and escalates work that requires a person.
Capabilities and integrations depend on the adopted scope. Agree the applicable workflow and responsibilities before operational use.
START WITH A DEFINED TASK
Bring your operational use case.
Discuss the work, supported actions, approval requirements and measurement that fit your operating model.
Opens an editable email draft. No request is sent or meeting reserved.