Skip to content

TalkwardBildschirmansicht LogoTalkward × Bildschirmansicht

See where the customer is stuck right now

See live the store page your customer is stuck on, with scrolling and clicks. Instead of asking “where exactly are you?”, you see it as soon as the customer clicks “Allow” in the chat window. Inputs stay masked, nothing is stored, and they can stop at any time.

HaferhainAI assistant replies instantly
Web chat

My voucher code AUTUMN10 does not work. I am in the cart and nothing happens.

Screen view started · Mira · page: cart · inputs masked

Mira

Code sits in the “order note” field. The voucher field is below it, collapsed.

Mira

I can see it: the code is in the note field. Please click “Redeem voucher” below it, that is where it goes.

Oh! Yes, now it takes 10% off. Thanks!

Write a message

Sound familiar? Three moments where describing is not enough.

The customer sees something your team does not. So they describe it, and your team guesses what they mean.

  1. “The voucher does not work.”

    Wrong field, expired code, minimum order not reached or a typo? Your team asks four times and the customer abandons the purchase.

  2. “There is no continue button.”

    On which page, in which browser, with which cart? Your team clicks through its own store and finds nothing, because on their side everything looks fine.

  3. The configuration is off.

    Size, colour, accessories, engraving: the customer picked the wrong option somewhere and asks why the price is wrong. Without seeing the page, it is guesswork.

With screen view your team asks, the customer allows with one click, and your team sees their page live and tells them where to click. Inputs stay masked throughout.

Three cases from the chat

Where looking saves the sale.

Your team member asks in the contact profile, the customer allows in the chat window. The view only runs while somebody is watching, and the customer sees a notice with “Stop” the whole time.

  1. Voucher in the wrong field

    Your team sees: the code sits in the “note” field. One message, “please put it in the field below”, and the order goes through. What the customer types stays masked.

  2. Button off the screen

    On the phone the continue button is hidden under the cookie bar. Your team sees it in seconds and tells the customer instead of searching the store itself. And a hint for your store developer on the side.

  3. Wrong option in the configurator

    The price is off because engraving is ticked. Your team sees the selection live, explains it, and the customer orders with confidence.

How the view worksLive image of the page, inputs masked.

The chat widget already tells Talkward which page a visitor is on. When a team member requests screen view, the chat window shows the customer who wants to see what and why, with “Allow” and “No, thanks”. Only after allowing does the widget transmit the page structure with scrolling and clicks, like a live image, not as video. Everything the customer types into form fields is masked. Areas of your store nobody should see, you exclude entirely. The view only runs while your team member is watching; the data is deleted after ten minutes at the latest.

  • Inputs stay masked

    Everything the customer types into fields is masked: name, address, payment details, passwords. Your team sees where they type, never what.

  • Exclude areas

    Account area, checkout or other parts of your store you take out of the view entirely. There your team only sees a grey area.

  • Nothing is stored

    The view only runs while your team member is watching. There is no recording; the transmitted data is gone after ten minutes at the latest.

  • Only with consent, stop any time

    The view only starts once the customer clicks “Allow” in the chat window. While it runs they see a notice with “Stop”; closing the chat ends it. Request, consent and end are logged as lines in the conversation. To inform your customers you get a template paragraph for your privacy policy.

Connection
Live view of the customer’s store page from the chat widget, after their consent in the chat window
Access
Page structure, scrolling and clicks; inputs masked, areas excludable, nothing stored
Processing
Nuremberg (ISO 27001), Cologne, Paris. “Europe only” option. Credentials stored encrypted, orders only cached briefly.

In the contact profileWho is in the store right now, and where.

For web chat customers the contact profile shows whether they are online right now and which page is open. One click on “Request screen view” sends the request into the chat window; once the customer allows, the live view runs next to it. Request, consent and end sit in the conversation, what your team saw it records as a note.

  • Online now
  • Open page
  • Recently visited
  • Requested by
  • Duration
  • Note
LH
Lena HoffmannCustomer since 2025 · Haferhain
Screen view
Online now
Yes, cart
Recently visited
Home, Peanut Crunch 12-pack, cart
View
Requested by Mira, allowed, 2 minutes
Note
“Voucher was in the note field”
Orders
#1043Ordered25 Sep 2026

Set up in three steps.

From Basic, €19 per month. Nothing to install, the chat widget brings everything.

  1. Enable the extension

    In Talkward under Extensions switch on “Screen view”. You get the template paragraph with which you inform your customers in your privacy policy.

    Screenshot to follow
  2. Exclude areas

    Define checkout, account area or other pages that are never transmitted. Input fields are masked everywhere without any setting.

    Screenshot to follow
  3. Request the view

    In the web chat with a customer who is in the store right now, click “Request screen view” in the contact profile. The customer clicks “Allow”, then the view runs. Closing ends it, on your side or theirs.

    Screenshot to follow

“Screen view” extension

€19/ month, from Basic, provisional, net

€19 per month, from Basic, cancel monthly. Web chat only.

All plans and prices
  • Live view of the customer’s store page with scrolling and clicks
  • Inputs masked, areas can be excluded
  • No recording, data deleted after ten minutes at the latest
  • Only with the customer’s consent in the chat window, stop any time, logged in the conversation
  • Servers in Nuremberg (ISO 27001)
  • Data processing agreement
  • AI replies labelled (EU AI Act)
  • Extensions cancellable monthly

Questions about screen view

Question not listed? Write to us at hey@talkward.app.

Does my team see what the customer types?

No. Everything the customer types into fields is masked: name, address, payment details, passwords. Your team sees where they type, never what. Whole areas such as checkout you exclude in addition.

Is the view stored?

No. It only runs while your team member is watching. There is no recording; the transmitted data is deleted after ten minutes at the latest.

Does the customer have to consent?

Yes. Your team member asks, the customer sees in the chat window who wants to see what and why, and clicks “Allow” or “No, thanks”. Only then does the transmission start. While it runs they see a notice with “Stop”; closing the chat ends it. Request, consent and end are logged as lines in the conversation. You additionally inform about it in your privacy policy; you get a template paragraph when switching it on.

Does it work on WhatsApp or email?

No, only in the web chat, and only when the customer is in the store right now. Other channels have no page that could be viewed.

What does screen view cost?

€19 per month, from Basic, cancel monthly. All prices are provisional and net.

Secureyour seat.

Three details, no commitment. We will get back to you personally within two working days.

hey@talkward.app

What would you like?

We use your details only to reply to you. More in the privacy policy.