Skip to content
The Design Office of Nick Sloggett
WorkWritingExperimentsResumeEmail
Back

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.

Role
Sole designer
Years
2019
Team
One designer and one engineer
Deliverables
Interaction Design, iPhone App
Three iPhone screens from CE Request, side by side, dark, with sample accounts and people. Left, the inbox: three requests, the first marked Response received 1 hour ago with 3 replies, the other two No reply for 3 days and No reply for 8 days, in red. Middle, Laura Benning's request for Alder Creek Unified School District, with a purple Open in Slack button, View Discussion, and its status, last response and created date. Right, the request's discussion: the request again, the date, then a reply set behind a grey quote bar.

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.

9:41
InboxInsights
Laura BenningAlder Creek Unified School DistrictDeployment & Management
Alder Creek has been trying to finish setting up their Federation, but they still can't get their domain released...Response received 1 hour ago3 replies
Kevin TranFernlightSecurity
On a recent visit, Fernlight raised concerns about security on their shared devices, and would like guidance on what they should be doing to lock them down...No reply for 3 days
Grant WhitleyRidgeline WirelessOther
The Ridgeline Wireless team is asking us to sign an NDA before they share more details about their plans for...No reply for 8 days
The inbox. When someone has replied, when and how many replies. When nobody has, how long, in red.

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.

9:41
BackRequest
Laura BenningAlder Creek Unified School DistrictDeployment & Management
Alder Creek has been trying to finish setting up their Federation, but they still can't get their domain released. They have now missed a rollout date and the district's leadership is not happy. There's an open AppleCare case #200417735218, and I'm hoping someone can help us find out where it's stuck, so the district can move forward with its rollout.Thanks, Laura
Open in SlackView Discussion
StatusWaiting on SubmitterLast Response1 hour agoCreated DateOctober 17, 2019
The request: the message in full, Open in Slack, View Discussion, and where it stands.
9:41
RequestDiscussion
Laura BenningAlder Creek Unified School DistrictDeployment & Management
Alder Creek has been trying to finish setting up their Federation, but they still can't get their domain released. They have now missed a rollout date and the district's leadership is not happy. There's an open AppleCare case #200417735218, and I'm hoping someone can help us find out where it's stuck, so the district can move forward with its rollout.Thanks, Laura
October 17, 2019
Megan OrtizOctober 17, 2019 at 4:14 PM
Hi Laura,This AppleCare case looks like it was opened on Monday. aldercreekusd.org is on the domain blocklist, which is why the release can't go through. Engineering cleared about 600 of the ~1,800 blocked domains last night, and the rest will be processed next week. For now they can check whether theirs was in the first 600. If not, they just need to wait.
Daniel Reyes
Its discussion: the request on top, then each reply, quoted, with who wrote it and when.

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

Next case study

Rippling AI →Designing an AI that can change a paycheck, and making every change visible before anyone approves it.

Contact

Want to talk about CE Request? Email me.

© 2026 Nick Sloggett

EmailLinkedIn (opens in new tab)ResumeRSS