Design Agent · JLL

Service Agent

Corrigo's customer portal is where people outside the facility team report a building problem and follow it up. Most of them have one or two requests open at a time. Reporting one meant a form and a lot of clicking. The first chat assistant in the portal cut the clicking, but it asked for things it should already know, like which building you are in, showed its own reasoning, and sent people to special instructions they did not understand. So I did not add a chat to the old portal. I rebuilt the portal around one agent.

Company
JLL
Product
Corrigo
Role
Design Lead
Period
2026

Decisions

01

The agent asks only what is missing.

A person describes the problem in their own words. The agent fills the rest from their profile, asks for the location only when they have more than one building, reads the request back in one sentence, and submits on a yes. Nothing is created or cancelled until the person says so.

02

The landing page is the person's own requests.

Most people have one or two open, so I dropped the layouts built for many. The page is a greeting, one input, and their requests, each with five steps from submitted to verified. A request opens in place to add a note, send a message, or cancel, so nobody goes looking for a separate page.

03

Special instructions are something to read.

I tried them in a window with an Okay button, and a reviewer pointed out it looked like accepting terms. They went back into the agent's reply with one button to say they were read, and closing anything never cancels the request.

04

A scanned tag needs no login.

Anyone who sees a problem can scan the code on the room or the equipment, and the codes already printed keep working. The code already says what and where, so the agent asks two questions, reads the report back, and first shows what is already reported there, so one leak is not reported five times.

05

The prototype is the specification.

Every part is a design system component as it ships, and the scripted demo and the live assistant run on the same events, so what reviewers see is what gets built. Earlier versions stay in the same build behind a switch, so I show a change instead of describing it.

Outcome

In progress. I designed and prototyped the new portal in code with Claude Code as Design Lead, and the team agreed the prototype and its decision files are what engineering builds from, with no separate mock-ups. Each finding from the usability sessions on the first chat maps to a decision in the design or an open question. Invoice approval is the next area.

Screens

The landing page with a greeting, one input, and the person's requests, and a request opened in place with its five steps. Creating a request with the special instructions inline, the read-back, and the submitted card, then rating the work and cancelling from the card. The no-login report from a scanned tag on a phone, the earlier versions next to the current one, and two decisions that were built and then reversed.

The screens are behind a password

The screens for this and the other case studies are shared with the people I am talking to. The password is in the resume I sent with my application. If you do not have it, ask me for it.