Investigated Sam's request to change the Intake-visible Billing Address label to Home Address or Address.
The label is not an Intake field. On Collapsible_Intake_Page, Intake embeds the Client related-record component using quick action Account.Party_Details_Intake_Matter. That quick action includes Account standard compound field BillingAddress, which Salesforce displays as Billing Address.
All attempts were check-only or read-only except local metadata staging. No live deploy was made.
Account.Party_Details_Intake_Matter and confirmed it uses <field>BillingAddress</field>.BillingAddress; Salesforce allows track history in the retrieved metadata but rejected a direct <label>Home Address</label> addition with Cannot specify label on standard field.Account-en_US translations. Existing translations already rename Account to Party and Phone to Party Phone.account_billing_address as a field translation key; Salesforce rejected it: Field account_billing_address does not exist on entity Account.BillingAddress as a field translation key; Salesforce rejected it: Field billingaddress does not exist on entity Account.After three consecutive check-only failures on the standard field rename path, stopped per Sam's instruction rather than forcing a brittle workaround. The live system was not changed.
Change the visible Intake client panel by replacing the quick action's standard BillingAddress field with a purpose-built Account field or display component labeled Home Address or Address, while keeping the underlying BillingStreet/BillingCity/BillingState/BillingPostalCode data intact.
A reversible implementation would be: create or reuse an Account display field labeled Home Address or Address, populate it from existing Billing address data if needed, swap that field into Account.Party_Details_Intake_Matter, deploy check-only, deploy live, then verify on an Intake record. This avoids globally renaming Salesforce's standard compound address field.