Add company name to consultant leader approval email subject
Jira: BIF-9093 · Epic: BIF-8695
Overview
Follow-up to the Consultant Mode New Approval Flow (PRD, Epic BIF-8293). In the Trial Path, an approval email is sent to the Internal Approver / consultant leader to grant a consultant access to a client's environment. The subject line is currently generic, so an approver with several pending requests in their inbox cannot tell at a glance which client a given request is for — they have to open each email to disambiguate.
Add the client company name to the subject of that approval email so the approver can identify the client directly from the inbox, reducing the risk of approving access to the wrong environment.
No Product Intelligence Hub checkout was available during authoring; sources: [] records
that evidence gap explicitly.
Scope Changes
- Backend — inject the client company name into the subject template of the consultant leader (Internal Approver) approval email only. No body/CTA changes; no change to the client or consultant receipt emails.
Goals
- Surface the client company name in the Internal Approver approval email subject so the approver can identify the client without opening the email.
Non-goals
- Changing the email body, layout, or approval CTA/buttons.
- Changing the subject of the client-facing or consultant-facing receipt emails.
- Changing routing, approver selection, or the approval logic itself.
8. User Stories + Acceptance Criteria
| User Story | Importance | Mockup / Technical Notes | Acceptance Criteria |
|---|---|---|---|
| [CONEMAIL-S01] — Company name in the approval email subject As a consultant leader (Internal Approver), I want the client's company name in the approval email subject, so that I can identify which client an access request is for straight from my inbox without opening each email. | Should Have | Subject template of the Internal Approver approval email only (Trial Path — see PRD "Email Approval to Internal Approver"). Source the company name from the request's client record. Keep the subject concise; place the company name where it reads clearly (e.g. [Company Name] — Consultant access approval request). | — Happy Path — • AC-1: Given a consultant access request routes to the Internal Approver, when the approval email is sent, then the subject line includes the client's company name. • AC-2: Given the company name is included, when the approver reads the subject, then the remainder of the subject stays clear and the email body and approval CTA are unchanged. — Error / Unhappy Path — • ERR-1: Given the company name is missing or unavailable for the request, when the email is sent, then it still sends with a safe fallback subject (no crash, no blank subject, no exposed placeholder token). — Guard-rail — • NEG-1: Given the other consultant-mode emails (client receipt, consultant receipt), when their triggers fire, then their subjects are unchanged — only the Internal Approver approval email subject changes. |
Open questions
- Exact subject copy and placement of the company name (prefix vs suffix) — confirm final wording.
- Which field is the authoritative source for the displayed company name (billing account name vs Modpanel client name)?
- Fallback subject text to use when the company name is unavailable (ERR-1).