Skip to main content
bradley
bradley
Expert ⭐️
June 3, 2026
New Idea

Allow Label Changes for System Fields

Related products:Staircase AI
  • June 3, 2026
  • 3 replies
  • 43 views

This has been asked for CS, but this is specifically about Staircase. There are some OOB fields that the tool really relies on, and it would be great to be able to customize the labels based on our business usage/nomenclature.

For example, Tier is something we use to describe product tier, and we would like to be able to rename it “Segment” or something else so it has the same name as the source field in the CRM. 

It might be a bit smaller of an issue if folks move more towards interacting via LLM, but any way we can reduce context switching, or having to instruct LLMs to refer to it differently each time, would be great.

      3 replies

      bradley
      bradleyAuthor
      Expert ⭐️
      June 22, 2026

      Added a related request here too: 

       

        dcassidy
        dcassidy
        Helper ⭐️⭐️
        June 25, 2026

        The OOB fields in Staircase that drive core functionality really need their own solution.

        The Tier/Segment example demonstrates it well. When your CRM, CS platform, and Staircase are all using different labels for the same concept, you're either eating that friction manually or baking translation instructions into every LLM prompt - neither is great.

        Even a simple admin-level label override for OOB fields would make a meaningful difference.

          mobrien14
          mobrien14
          Helper ⭐️
          August 6, 2026

          This would be a great change for our users & shouldn’t be that difficult. CS already has the solution in place with custom fields between a field display name vs. the backend/API name being untouched and still retrievable by the tooling.

          Terms & ConditionsAccessibility statement