Show Me

Agents should show, not tell.

The task“My checkout button is broken on phones. Fix it.”

Same task. Same agent. Two ways to talk. Tap the cards as you go.

Sample data. Fern Coffee is made up. Read the principles

1. Point at it

You point. The agent doesn't quiz you.

Chatbot

My checkout button is broken on phones. Fix it.

I'd be happy to help with that! To fix it, I need a little more information first.

Which button do you mean? There are several on the checkout page, including the Pay button near the bottom, the Apply coupon link next to the total, and the OK button on the cookie bar.

Could you describe where it sits on the screen, what it looks like, and what happens when you tap it? It would also help to know which phone and browser you're using, and whether this happens every time or only sometimes.

If you're able to, please share a screen recording too. The more detail you can give me, the better I can help!

Show Me2 taps

2. Tap-through map

The whole system at a glance. The problem is already lit up.

Chatbot

Thanks! I looked into it, and here is what I found. Your checkout works in four steps.

First, the Cart step adds up the items and shipping. This step works correctly on every screen size. Next, the Address step saves where the order should go, and it also works on every screen size.

Then comes the Payment step, and this is where the problem is. On phones, the cookie bar is fixed to the bottom of the screen and its z-index puts it on top of the Pay button. Most of the button is covered, so people can't tap it.

Finally, the Receipt step confirms the order. However, phone customers never reach it, because they can't get past the Payment step.

Let me know if you'd like more detail about any of these steps, or if you'd like me to go ahead and fix it.

Show Me1 look, 1 tap

3. Tap to decide

See each option. Tap one.

Chatbot

Great question! There are a few ways we could fix this. Here are your options:

Option 1: Sticky Pay button. We could stick the Pay button to the bottom of the screen and rest the cookie bar just above it. The advantage is that the button is always in reach. The downside is that the bar and button together take up more of the screen.

Option 2: Cookie bar on top. We could move the cookie bar to the top of the page. This is the smallest change. However, it can push the page content down and may cover your header.

Option 3: Cookie pop-up. We could replace the bar with a pop-up in the middle of the screen. The Pay button stays clear afterwards, but the pop-up blocks the page until it is dismissed.

Overall, I would recommend Option 1. Let me know which one you'd prefer and I'll get started!

Show Me1 tap

4. Work board

Long jobs count real steps. No guessed plan.

Chatbot

I'll start by opening checkout.css to see how the Pay button is positioned.

Now let me look at cookie-banner.css to see how the bar is placed.

Next I'll search the project for z-index, because this looks like a stacking problem.

Let me check checkout.test.js to see what is already tested.

Now I'll load the page at phone size to confirm what's happening.

Okay, I can see the issue. I'll edit checkout.css first.

Now I'll update cookie-banner.css as well.

Let me run the phone tests to make sure this works.

Hmm, one test failed. It looks like a spacing problem. Let me fix that.

I've adjusted the spacing. Running the phone tests again.

The tests pass now! Let me commit the change.

Next I'll merge the pull request.

Finally, I'll deploy this to the shop.

Show Me1 look

5. Drag to compare

Don't read about the change. Drag across it.

Chatbot

All done! Here is a summary of the changes I made:

In checkout.css, I changed the Pay button to stick to the bottom of the screen and made it full width, so it is now always within reach on phones.

In cookie-banner.css, I made the cookie bar shorter and moved it up so that it rests just above the Pay button instead of sitting on top of it. I also adjusted the z-index so the two no longer overlap.

Before this change, the cookie bar covered most of the Pay button. After this change, both are fully visible. The order details look the same as before, and the page layout is otherwise unchanged.

All phone tests pass. Is there anything else you'd like me to change?

Show Me1 drag, 1 tap

6. Motion clip

If it happens over time, play it.

Chatbot

Here's what was going wrong. When a customer opened checkout on a phone, the page loaded and the Pay button appeared at the bottom of the screen.

A moment later, the cookie bar slid up from the bottom edge and landed on top of the Pay button. The customer tapped where Pay had been, but the tap went to the cookie bar, so no order was placed.

After the fix, the cookie bar moves up and rests above Pay. Pay stays clear, the tap reaches it, and the order goes through. Would you like me to add this to the release notes?

Show Me1 look, 1 tap

7. Flipbook

A few real screenshots under one scrubber. Motion without a video pipeline.

Chatbot

Here is how full screen works now. The diagram sits in the chat as a plain figure with a small icon in its corner. Tapping that icon opens the diagram over the whole screen, with a short toolbar of icons at the top: zoom out, the current zoom level, zoom in, point, open in a new tab and close.

Tapping zoom in takes it to 125 percent, then 156 percent. Tapping the zoom level resets it to 100 percent. Tapping close returns you to the chat exactly where you were, with the diagram card still in place.

Show Me1 look, 1 drag
to read as a chatbot
6 taps, 2 dragsand 4 looks with Show Me

Use Show Me with your agent

Your draftTap a card. Its answer lands here.You still press send