> For the complete documentation index, see [llms.txt](https://user.netmera.com/netmera-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user.netmera.com/netmera-user-guide/omnichannel-engagement/widgets/build-a-widget.md).

# Build a widget

Build the widget before setting its audience or launch rules.

### Step 1: Create the starting point

Choose a template, a blank widget, or an existing design.

[Create and manage widgets](/netmera-user-guide/omnichannel-engagement/widgets/build-a-widget/widgets-dashboard.md)

<figure><img src="/files/wrrMrWrt7br2ATceJWWp" alt=""><figcaption></figcaption></figure>

### Step 2: Configure widget-level settings

Set the widget type, placement, overlay, and close behavior.

[Configure widget settings](/netmera-user-guide/omnichannel-engagement/widgets/build-a-widget/configure-widget-settings.md)

<figure><img src="/files/YkDDMfVnTMjHyk5ClH8N" alt=""><figcaption></figcaption></figure>

### Step 3: Design the experience

Build views, add elements, and set clear identifiers.

[Design widget layout](/netmera-user-guide/omnichannel-engagement/widgets/build-a-widget/design-widget-layout.md)

<figure><img src="/files/YXveeFR8bKtSqEwWGFYY" alt=""><figcaption></figcaption></figure>

### Step 4: Add behavior

Configure actions, conditions, and input validation. Test every path.

[Configure widget actions and validation](/netmera-user-guide/omnichannel-engagement/widgets/build-a-widget/configure-widget-actions-and-validation.md)

<figure><img src="/files/00jKMPytIfxCB9WJhKu7" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Use [Widget elements reference](/netmera-user-guide/omnichannel-engagement/widgets/build-a-widget/widget-elements-reference.md) when choosing an element.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://user.netmera.com/netmera-user-guide/omnichannel-engagement/widgets/build-a-widget.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.