Skip to main content

Make first and last name optional fields for account creation when it's a company profile

🔍 Problem Statement

When creating an account for a company or organisation, Pelcro still requires first and last name fields. This is unnecessary for corporate accounts and creates friction during onboarding — admins must enter placeholder values, which pollute customer data.


💡 User Story

As a Pelcro admin, I want first and last name to be optional when the account is a company, so that corporate accounts can be created cleanly without placeholder name data.


🎯 Definition of Done (DoD)

A feature is done when:

✔️ Given account creation for a company, when the admin omits first and last name, then the account is created successfully using only the company name — and the customer record displays correctly in the dashboard and API without placeholder values.

Status: In Planning2 comments

Log in to comment and vote

Comments2

  • Sarah Graham

    •

    Sep 17

    •

    Merged request

    •

    2 votes

    Middle Name/Initial

    🔍 Problem Statement

    Pelcro's customer profile has no dedicated field for a middle name or initial. Users currently append it to the first name field, which leads to inconsistent data, unreliable name-based searches, and formatting issues in communications and exports.


    💡 User Story

    As a Pelcro admin, I want a separate Middle Name/Initial field on the customer profile, so that middle names are stored consistently and don't pollute the first name field.


    🎯 Definition of Done (DoD)

    A feature is done when:

    ✔️ Given the customer creation or edit form, when an admin enters a middle name or initial in the dedicated field, then it is stored separately from the first and last name, and appears correctly in the customer profile, exports, and any name-formatted communications.

    • Rana Haleem

      Team•

      Dec 18, 2025

      Alot of customers have initials and middle names, if we can add a new input field for the middle name