Apps · interfaces for working with AI
An interface to monitor, decide and intervene.
Apps put the process in the hands of the people who request, operate and supervise it. Starya designs portals, dashboards and workspaces connected to operations, so teams can see what is pending and how to act.
The team needs to see beyond the conversation.
A request can be answered in chat while remaining blocked by a missing document or approval. Switching between messages, spreadsheets and systems makes it hard to know who can unblock it. The interface needs to show the work’s state, the data used and each person’s next decision.
- Show what is missing
Connect the receipt, purpose and cost center in the same request.
- Offer the permitted decision
The responsible person checks the items and approves or requests more information.
- Track the handoff
Distinguish approval, submission to finance and confirmed receipt.
Illustrative workflow · the design depends on agreed rules and integrations.
Operations
The screen follows the responsibility.
Design starts with users and tasks. These interfaces are possible scopes of work, with features and integrations defined for each deployment.
Request portal
Let customers, beneficiaries or employees open a request, provide a missing document and check progress. Specific instructions help avoid another service interaction just to explain the same missing item.
- What needs to be available
- User identification, the relationship to the request and rules for viewing or changing information.
- How to verify the outcome
- People find the right request and identify the next step; other users’ data remains outside their access.
Operations and exceptions dashboard
Bring together queues, owners and reasons for interruption. The team can investigate an integration failure, correct an input or route a decision, while distinguishing an attempt from a completed action.
- What needs to be available
- Process states, signals available from integrations and owners for each type of exception.
- How to verify the outcome
- A pending item can be found, assigned and tracked to resolution, rather than disappearing when the screen refreshes.
Analysis and action workspace
In NebulaWorks, the team can bring together conversations, decisions and workflows included in the deployment. For a sensitive action, the interface needs to show affected items and required approval before routing execution.
- What needs to be available
- Query sources, permissions and the contract for each action available in the workspace.
- How to verify the outcome
- Decision makers can review the proposal and inspect the response. A new query must not appear as a change already executed.
Before you start
What needs to be settled before the final screen.
People and permissions
Describe requester, operator and manager tasks. Define actions, visible fields and boundaries between organizations for each role.
States and recovery
Design loading, missing data, denied access and failed submissions. People need to know whether retrying could duplicate a request.
Everyday use
Check keyboard access, focus, labels, mobile reading and resuming after an interruption. Track completed tasks and requests for help, alongside screen visits.
Examples and references
An expense decision
A fictional receipt and cost-center review. Explore how a choice changes the handoff without executing a payment.
Explore the expense reviewWorking in NebulaWorks
Explore ways to bring team queries, decisions and actions into the same workspace.
Explore NebulaWorks