OpenAI Dots 真实工作流演示：从出差行程规划到用户反馈闭环

Presenter: Yesterday's launch demo didn't go as planned. A bit unfortunate because I was really, really looking forward to showing you all what Dots are capable of. So today we're gonna play it back, and the whole point of the demo was to show you how Dots can be used for real work, real launches, real stuff. Dots actually did launch, and I actually do have a lot of stuff to do, so we're just gonna show you it here, unfettered, unfiltered, how I use my Dot. Starting with the phone call, the the infamous phone call to Dot. I need to go to LA tomorrow. It's kind of a last minute thing. I'm gonna see if my Dot can just like unblock a bunch of stuff for me because I'm a bit stressed out about it.

Dot: Hey, good to hear from you. What's up?

Presenter: Hi. Okay, so tomorrow I have an important meeting in LA. I need to be in Hollywood around like 3 p.m. Can you figure out, then? I think the latest I can leave the office is probably 10 a.m. Can you get me a flight that's like on policy and everything for the company, and then also some, it's got to be refundable, and also some hotel options in like East LA, and I want to see screenshots of them so I can choose, and also screenshots of like where they are on like Google Maps, you know, so I can see if I can hang out with anybody while I'm there.

Dot: Okay. Yeah. Let me align that up for you.

Presenter: Awesome. Thank you.

Dot: Yeah. And I'll make sure the flight is both in policy and refundable.

Presenter: Okay. Cool. What are the top options looking like right now?

Dot: Pulling that together now. So the leading flight I saw earlier was Southwest at 11:30, landing at 12:55, refundable around 3:26. I still need to verify the checkout total and policy.

Presenter: Okay.

Dot: Hotels, Silver Lake Pool and Inn looks like the best Arwan fit, and Kara is the other front runner, closer to Hollywood.

Presenter: Okay. If I land at one, do you think I can get to East Hollywood by three? I don't know what LA traffic is like.

Dot: Let me check that.

Presenter: Okay. And send me screenshots of those hotels. I want to look at pictures.

Dot: Probably if the flight's on time and you head straight over, I'd roughly budget 30 to 45 minutes to get out of LAX, and then maybe 45 to 75 for the drive. And regular ride shares mean getting to LAX. It. I'd feel better about it if you landed closer to noon.

Presenter: Okay. Yeah.

Dot: I'm grabbing those screenshots.

Presenter: Yeah, yeah. Let's get me in closer to noon then.

Dot: Okay. I'll recheck with that in mind.

Presenter: All right. One of my favorite things to do, just while I'm muted here, is to take a look at my Dots browser.

Dot: Also, that earlier Southwest option I'd seen landed at 11:20, which would give you a nicer buffer. I'm checking if it's still available with an in policy refundable fare, and I'll send the hotel photos and maps in chat so you can look at both.

Presenter: Whoa. Okay. Cool. Um, Silver Lake Pool and Inn looks fun. I like Kara too. Am I muted? Sorry. Okay. Let's just do Silver Lake Pool and Inn.

Dot: Okay. Locking onto Silver Lake. I'll prepare a one night booking and verify the full price and cancellation terms.

Presenter: Okay. Great. Thank you. Um, hey, while you're doing that, some other stuff. Um, our user feedback channel just has so much stuff going on in it, and I know. Uh, I think I would feel better if we just had a more kind of concrete workflow to capture all of that. Um, I think the biggest things I just need to know are like, what are the biggest themes of feedback, and do we have like solutions to the most pressing issues, and if not, what are the outstanding things that maybe none of us are paying enough attention to? Can you maybe like pull together that analysis?

Dot: Yeah, I'm on it. The last dashboard we had was baseline only, so I'll pull together the main themes, fixes, and gaps, and make the capture workflow concrete.

Presenter: Okay. What is our capture workflow right now? Right. Let's make that explicit. What is the capture workflow?

Dot: Checking. Right now, it's a manual new channel batch. We read the channel reports and replies, put each item in the master list, classify and group it, and then link actual issues to verified linear tickets. We also match tickets to PRs and track fixes in flight, shipped or retested. The dashboard summarizes that work. It doesn't auto capture new messages. That's fine. And ticket reconciliation is still incomplete.

Presenter: Cool. Yeah. I I think it's fine for us to run the feedback manually. Um, I guess the bigger thing I want to make sure of is that we understand what kind of large issues that we don't have uh solutions for right now, and then that B when a PR lands and we expect it to have addressed some big theme of user feedback that we actually go into Slack and have you respond and link out to the PR and like, you know, tell the user to try again.

Dot: Got it. That gap and reply loop is clear. I'll sort for biggest issues without a credible fix, and then close the loop with PR-linked replies asking people to retry.

Presenter: Awesome. Okay. And then let's just um. Yeah. What's the and the retest confirms the retest. Go ahead.

Dot: No, you go. The retest is what confirms we actually close the loop. That's the part that's been inconsistent. I'll make the no fix themes a priority and follow up in threads with the PR link asking folks to try again once it's rolled out to them.

Presenter: Okay. Yeah. That makes sense. Um, what's maybe the biggest theme right now, just in the last 24 hours?

Dot: The clearest issue looks like reliability. When a dot looks active but doesn't reply or can't access tools, I'm checking the full ranking before I call that the largest by volume. My strongest read so far is people can't tell whether their dot is actually working. That includes missing replies, tool access failures, and unclear progress. Some real, some visibility.

Presenter: Okay. Actually, Drew, can you focus in on this for a second? I just want folks to see the really cute dot animation up here as it's searching for repositories. Very cute. Okay. Awesome. Yeah, that makes sense.

Presenter: And then, hey, lastly, um, I know there's just been a ton of uh go-to market movement. Folks are wondering about the relationship between Dots and some of the other things we launched, like ChatGPT and Slack and Teams. Um, can you maybe pull together the top unanswered Slack messages I have and just uh maybe draft a response for me?

Dot: Let me get that together for you.

Presenter: Okay. Thank you. Um, that was actually really awesome. It's uh still booking my flight. It found the hotel. I like these pictures. I picked one of them. Um, and it uh you know knows about the feedback flow that we are implementing, and it's gonna go, you know, prioritize my latest um things that I need to go work on. It's messaging me now um about what the top categories of feedback are. Looks like it is reliability, which we're working on, um, and some like UX polish that we need to do around mobile and notifications. And then you know what? I'm actually just gonna say like run the feedback flow again, and we'll see.