---
title: "Clarifies join page fields"
summary: "New customers could not tell the pool address was required and the email was optional."
slug: join-page-fields
date: 2026-10-27T00:00:00.000Z
tags: ["onboarding", "customers"]
ref: "34"
status: published
url: https://updates.poolcloud.com/join-page-fields
site: "PoolCloud updates"
---

# Clarifies join page fields

## The problem

> "it's not obvious enough that the email field is optional, but the address is required."

- Four identical rows; "optional" hid inside the email editor.
- The address error appeared only after pressing Continue.

## What we considered

### A. Required and optional tags {chosen}

![A](https://updates.poolcloud.com/media/poolcloud/join-page-fields/34A.png)
- Every row stays put; a tag says what's needed.

### B. Address first and open

![B](https://updates.poolcloud.com/media/poolcloud/join-page-fields/34B.png)
- Hard to miss, but changes the page on arrival.

### C. Two labelled groups {chosen}

![C](https://updates.poolcloud.com/media/poolcloud/join-page-fields/34C.png)
- Needed and optional split cleanly, with a counter.

### D. Blocked continue button {chosen}

![D](https://updates.poolcloud.com/media/poolcloud/join-page-fields/34D.png)
- Says exactly what's missing before moving on.

## What we went with

- A Service details group with a counter, then an Optional group.
- Empty required rows show Required; email shows Optional.
- A missing address rings the row and disables Continue, with a hint.

New customers see at a glance what they must fill in and what they can skip. A missing pool address is flagged before they continue.