New Customer Account "Contact Us" link goes to wrong email address

Topic summary

Problem: In the “new customer accounts” return-request flow, a “Contact Us” link at the top routes to the Store Details “store email,” while the site-wide/footer Contact Us links route to the Notifications “sender email.” This misroutes return inquiries when the store email must be kept separate from customer service.

Findings:

  • The top link appears hard-coded to the Store Details email.
  • Other contact links across the site default to the sender email.
  • The Liquid templates (theme templating code) for new customer accounts are not exposed in the theme, so the link cannot be edited there.

Ask: How to change the mailto target for the top Contact Us link within new customer accounts so it uses the customer service address (consistent with other contact links).

Artifacts: A screenshot is attached to illustrate the UI location of the link.

Status: Unresolved; no guidance or workaround provided yet.

Summarized with AI on January 7. AI used: gpt-5.

In the new customer accounts, when someone clicks through to start a new return request, there is a “Contact Us” link that shows up near the top of the page. This link is hard coded to a different email address from the “Contact Us” link that is in the footer. See the attached screenshot:

From what I can tell, the contact link at the top goes to the email address in the “store email” field under the Store Details admin settings. ALL the other contact us links across the rest of the website default to the Sender email address I have put in under the notifications section of the admin settings. We need the store email to be separate from our main customer service email (we don’t want the customer service team getting emails about billing, etc.), so we need to be able to direct return requests to the correct email address.

How do I change the mailto: link for the top Contact Us link? The liquid code for the new customer accounts seems to be hidden and I don’t have access to them in my theme code.