FinWellU Registration Form — Company Website Field Help Text

Overview

The registration form on the FinWellU website includes a required Company Website field that was causing user confusion. Users (including client contacts John and James) were unclear why the field was required and what it was used for. The agreed solution is to add help text beneath the field explaining its purpose in the portal routing workflow.

This change was identified during the ^[1] Phase 2 review meeting on 2026-03-16 and assigned to Karly Oykhman (Asymmetric) for implementation.

Problem

• The "Company Website" field displayed only a "Required" label with no explanation.
• Users did not understand why their company website URL was being collected.
• Without context, users risked entering incorrect or generic URLs, breaking the portal routing logic that depends on this field.

Solution

Add help text directly beneath the Company Website field on the registration form. The help text should communicate, in plain language, that the field is used to route the registrant to their company-specific portal.

Suggested Help Text (Draft)

"Your company website helps us direct you to the correct portal for your organization."

Exact wording should be finalized by Karly in coordination with the FinWellU team. The text should be brief, friendly, and make the routing purpose clear without exposing technical implementation details.

Edge Case: Companies Without a Website

Some smaller companies onboarded to FinWellU may not have a public website. In these cases:

• A placeholder name or internal routing code can be used in place of a real URL.
• This placeholder serves as the routing key in the same way a real domain would.
• FinWellU (Peter/John) will coordinate with Asymmetric to establish the placeholder value when onboarding such a company.

This approach was confirmed as viable during the 2026-03-16 meeting.

Implementation Notes

• Assigned to: Karly Oykhman (Asymmetric)
• Field location: Registration form → "Company Website" field
• Change type: UI copy / help text addition — no structural form changes required
• Status: Pending implementation (as of 2026-03-16 meeting)

Related Context

• The Company Website field is a core input for the portal routing system — it determines which company-specific portal a registrant is directed to after signup.
• Parent company / subsidiary relationships (e.g., a brand name vs. its parent corporation) should use the most specific identifier that maps to the correct portal. Peter noted the example of Insincorator (subsidiary) vs. Emerson (parent).
• This fix is independent of Phase 2 development, which is paused pending the GVA partnership meeting. See ^[2].

References

• Meeting: ^[3]
• Client: ^[1]