- Get started
- Best practices
- Capabilities
- Skills
- CLI
- Examples
- Examples overview
- Recipe: build an agent
- Recipe: automate with RPA
- Recipe: enter data into a web app
- Recipe: extract data from a desktop app
- Recipe: refactor and test a workflow
- Recipe: a queue-based process with REFramework
- Recipe: build a Maestro Flow
- Recipe: build a Maestro Case
- Recipe: coded app and API workflow
- Recipe: build a coded function
- Recipe: verify a release with Test Manager
- Recipe: extract data from documents with IXP
- Advanced
- Help
Build and publish a Maestro Case that manages a customer dispute through intake, investigation, and resolution, with an escalation if it runs long.
This recipe builds a Maestro Case that manages a customer dispute from intake through resolution, with stages for investigation and an escalation if the case runs too long. It shows the full loop from your prompt to a case you can publish and run.
Prerequisites
- The
uipCLI and skills installed, and an authenticated session (see Install and set up). - An empty working folder.
Build the case
-
Open your coding agent in the empty folder.
-
Describe the case:
"Set up a dispute-resolution case with stages for intake, investigation, and resolution. Escalate to a supervisor if the case is in investigation for more than three business days."
-
Review the design packet the agent proposes — the stages, the tasks inside each one, the escalation rule, and every resource decision it made. Correct anything that's off before approving.
-
Approve the design. The agent builds and validates the case definition.
-
Ask the agent to publish the case to Studio Web so you can preview it visually.
-
Refine in conversation — for example, add a stage for appeals, or change who the escalation notifies.
Result
A validated, published Maestro Case that takes a dispute from intake to resolution, with an escalation if investigation runs long.
Next steps
Before running the case against real data, ask the agent to walk through a debug session with a sample dispute so you can confirm the routing and escalation behave as expected. See Maestro Case.
The generated stages, tasks, and commands depend on your agent and prompt. Use the escalation and routing behavior, not the exact files, as your signal of success.