> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/intercom/configuration/wire-a-video-intercom/configure-tk74-touch-screen.md).

# Configure TK74 Touch Screen

Set up the touch screen display on your TK74

The TK74's touchscreen lets users customize brightness, display language, wallpaper themes, and the logo that appears on the standby, wake, and calling screens. Users can also customize display text, choose a 12- or 24-hour time format, and set the inactivity timer that determines when the screen goes to sleep.

***

## General display

Control the overall look and behavior of the touch screen, including brightness, language, and time format.

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Intercom.**
{% endstep %}

{% step %}
**Select your intercom and click Settings.**
{% endstep %}

{% step %}
**On the left navigation, select Screen.**

* Click Preview at the top to view your current display setup.
* Select Display appearance, then choose Automatic, Dark mode, or Light mode.
* Turn on Automatic Brightness to let the device adjust screen brightness based on the detected lux value, or use the slider to set the brightness manually.
* Select your preferred display language from the Display language dropdown.
* Turn 24-hour time on or off to choose your preferred time format.
  {% endstep %}
  {% endstepper %}

***

## Aesthetic customization

This section lets you brand the device with your own visuals, including a logo and wallpaper, so the intercom matches your site's look.

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Intercom.**
{% endstep %}

{% step %}
**Select your intercom and click Settings.**
{% endstep %}

{% step %}
**On the left navigation, select Screen.**

* Under **Logo**, click **Add logo** to upload a custom logo for the Standby, Wake, and Calling screens.
* Under **Wallpaper**, select a theme: Default, Bokeh, Liquid Glass, Silk Satin, or Waves.
* Click **Add** next to Wallpaper to upload a custom wallpaper image.
* In the Device text section, enter a short title in the Text field. The title can contain up to 20 characters.
* Enter additional detail in the Subtext field. The subtext can contain up to 20 characters.
  {% endstep %}
  {% endstepper %}

***

## Standby mode

Standby is the idle state the device shows when it isn't actively being used, and it determines what appears on screen while the intercom sits inactive.

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Intercom.**
{% endstep %}

{% step %}
**Select your intercom and click Settings.**
{% endstep %}

{% step %}
**On the left navigation, select Screen > Standby.**

You can enable any of these options to customize the standby display screen:

* Toggle on **Show date & time** to display the current date and time.
* Toggle on **Show text** to display custom device text.
* Toggle on **Show logo** to display your uploaded logo.
  {% endstep %}
  {% endstepper %}

***

## Wake mode

Wake mode is the transitional display shown when the device is triggered out of standby, such as when someone approaches or interacts with it, before a call or unlock screen appears.

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Intercom.**
{% endstep %}

{% step %}
**Select your intercom and click Settings.**
{% endstep %}

{% step %}
**On the left navigation, select Screen > Wake.**

* Use the **Display** dropdown to select a layout for the wake screen.&#x20;
* Under **Screen > How long before device goes to sleep mode after inactivity,** select a timeout value. The default value is 1 minute.&#x20;

{% hint style="warning" %}
Wake is triggered by person detection, a call, an unlock action, or screen/button/reader interaction.
{% endhint %}
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.verkada.com/intercom/configuration/wire-a-video-intercom/configure-tk74-touch-screen.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
