Apple internal
CE Request
At Apple, customer requests passed between account executives, sales engineers and consulting engineers in Slack threads and email. I designed CE Request, an internal iPhone app that gave every AE, SE and CE in the United States one shared place to keep up with them: every request, where its conversation stands, and how long it has gone without an answer.

Requests had no shared home
A customer asks their account team for help. The account executive or sales engineer takes it to Consulting Engineering, in a Slack message or an email. From there the request lives wherever it landed.
That works for one request. Across a team it doesn’t. Nobody could see, in one place, which requests had an owner, which were waiting on the customer and which had simply gone quiet.
Beside Slack, not instead of it
People already talked in Slack, and they were going to keep doing that. But some of these conversations didn’t belong in a channel: customer details too sensitive to post there. So CE Request sat alongside Slack. It gathered the requests, kept the state of each one, stayed in sync with Slack where a conversation could live there, and kept the rest in the app.
So the app answers three questions, one per screen. What needs an answer? What was asked? What has been said?
How long it has waited
Each row in the inbox starts with who asked, their organisation and the category, one to a line. Under them is the start of the message, then one line about the reply. When someone has answered, it says when, with the faces of the people in the thread and how many replies there are. When nobody has, it says for how long, in red: No reply for 3 days. Age is the signal, so age gets the colour, and everything else stays grey.
The rows show the latest response, never the thread. Reading a request takes a tap. Seeing which ones need attention doesn’t. Anyone in Consulting Engineering could take a request by tapping “I’ve got it”, so the account team could see it had an owner.

Two ways into the conversation
A request opens to the message as it was written. Under it are the two ways into its conversation. Open in Slack is the one filled button, because it is the one that leaves the app. View Discussion stays in the app. Below those are the three things an account executive checks: the status, when someone last responded and when the request came in.
The discussion repeats the request at the top, so a reply is never read without its question. Each reply shows who wrote it and when, and the reply itself sits behind a grey bar, quoted as it came in. That is where the conversations too sensitive for Slack lived, and an account executive could read where a request stood without opening a channel.


Where it landed
CE Request shipped as an internal iOS app, synced with Slack, and every account executive, sales engineer and consulting engineer in the United States used it. I was the only designer, working with one engineer. The accounts, requests and people on this page are samples, not Apple’s. The same year at Apple I also redesigned Delta’s app for its flight attendants and led the design of Abbott’s Patient Controller for iPhone.
- Role
- Sole designer
- Team
- One designer and one engineer
- Year
- 2019
- Platform
- iPhone