Interactive example · fictional data

The AI tried. The rule did not allow it.

A request for different payment terms meets its authority limit and reaches the person who can decide.

Conceptual demonstration. It does not represent a customer case or prove available features.

Video

Transcript

[Illustrative example · fictional data] [“Can I get different terms for this payment?”] A customer asks for different terms.

[NebulaOS · Starya builds and connects within the operation’s scope · Commercial policy] [Illustrative interface · Features and integrations depend on the deployment.] On NebulaOS, connected by Starya within the operation’s scope, the agent checks CRM, contract and policy.

[Proposal v1 · Payment in 45 days] [Authority check: Above 30 days requires the manager’s approval] [BLOCKED · Blocked · review required] It prepares a 45-day proposal. Before any change, NebulaOS verifies authority. Above 30 days, the proposal is blocked: a person decides.

[NebulaWorks · Waiting for the sales manager’s decision] [Proposal v1 · Payment in 45 days · Current terms: Payment in 30 days] [Approve proposal v1 · Decline proposal v1] [Authorized · not executed yet] [Commercial system] [Sent · awaiting response] In NebulaWorks, the sales manager sees the context and approves or declines that version. Approved. Approving does not execute. The change is sent afterward; without a response, nothing counts as done.

[CRM updated] [Confirmed · answer prepared] [The original block stays in the history.] The commercial system confirms, the CRM is consistent, and only then is the answer prepared.

[The rule did not let the AI decide alone.] [Starya · We accelerate your AI strategy. NebulaOS is the operating foundation.] The rule did not let the AI decide alone.

Talk about this situation

What confirms completion

The commercial system confirms the change and the CRM is consistent before the final answer to the customer.

What NebulaOS supports in this scenario

In this scenario, NebulaOS consults the CRM, contract and policy, runs the authority check before any change and takes the decision to NebulaWorks; the commercial system and the CRM confirm the result. These systems are connected within the operation’s scope. Which actions go through the check, and with what limits, depends on the deployment.

NebulaWorks Brings together the work, owners, pending items and process artifacts.
Starya / FDE Designs the flow, rules and integrations of the agreed scope with your team.

Try it yourself

Walk through the steps of this scenario and see what changes with each choice. Fictional data; no system is accessed.

Open the simulation

Illustrative simulation · no system is accessed

Goal Answer a request for payment terms without exceeding the agent’s authority.

Team Agent · Sales management · Sales operations

Terms requested by the customer

01Propose
02Check authority
03Decide
04Send
05Confirm response

What we know now · v1 · Proposal prepared · check pending

The agent prepared a proposal. Nothing was sent.

Proposal v1 asks for: Payment in 45 days. Before any change, the terms go through the authority check.

Who answers now Agent. Check authority before sending any change.

Preserved history

Every decision and every block stays here, in this session only. Starting over clears the simulation.

v1Proposal v1 prepared: Payment in 45 days.

Authority matrix

Illustrative matrix of this simulation. It does not represent a real policy.
Action	Limit	Who decides	What confirms
Change the due date	Term of up to 30 days	Agent, within authority	Commercial system’s response
Extend the payment term	Above 30 days	Sales manager, in NebulaWorks, for one version of the proposal	Commercial system’s response and updated CRM

Questions to take to your team

Systems and data Which customer, contract and policy data does the agent consult before the proposal?
Authority How far can the agent negotiate?
Owner Who approves terms outside the policy?
Result Which response proves the change in the system?

Use these questions with the guide What to ask about AI already in use

Steps

Owner, system, state and pending item of the experience’s 5 steps, with decisions and limits

Step 1 · Propose
Check the context and propose
The CRM, contract and policy are checked, and the agent prepares a proposal. Nothing is sent.
Owner
Agent
System
CRM, contract and policy
State
Proposal prepared
Pending
Authority still needs checking.
Step 2 · Check authority
Block the proposal
The requested terms exceed the authority limit. No change is sent.
Owner
Commercial policy
System
Authority check
State
Proposal blocked
Pending
An authorized person needs to decide.
Step 3 · Decide
Decide in NebulaWorks
The person responsible receives context, parameters and consequences to approve or decline a specific version of the proposal.
Owner
Sales management
System
NebulaWorks
State
Human review
Pending
The decision does not execute the change yet.
Step 4 · Send
Send the authorized change
Only the approved version is sent to the commercial system. Approving does not send; sending is a separate action.
Owner
Sales operations
System
Commercial system
State
Awaiting response
Pending
Without a response, the result remains unknown.
Step 5 · Confirm response
Check the response
The commercial system confirms the change and the CRM is consistent before the customer is answered. Without a response, the team checks before repeating.
Owner
Sales operations
System
Commercial system and CRM
State
Change confirmed
Pending
Payment is outside this scope.

Decisions to explore

Terms within the authority limit
Approval declined
Approval granted
No response from the system

Pending items and limits

The original block stays in the history.
Approval does not retroactively execute the blocked attempt.
Changed terms require a new check.
A missing response never counts as success.

Text version

The main content, without depending on the video or the simulation.

Initial request “Can I get different terms for this payment?”

The customer asks for different payment terms. The flow checks the CRM, contract and policy and verifies authority before any change. Outside the authority limit, the proposal is blocked and the decision goes to the authorized person. Only an authorized execution confirmed by the destination changes the record.

The customer asks for different terms for a payment. The agent checks the CRM, contract and policy and prepares a proposal. The authority check blocks the terms because they exceed the limit, and no change is sent. In NebulaWorks, the person responsible sees the context and consequences and decides on a specific version. Once approved, the team sends the approved version as a separate action and waits for the commercial system to respond before answering. The commercial system confirms, the CRM is consistent and only then is the answer to the customer prepared. Without a response, nothing counts as done.