NR Consent Letter: email content update about entity HOT 19 CLOSED

Oge used to get two emails, one after the consent letter was sent. we need to determine the logic of this process. lets not remove the line for this ticket. lets prove that 2 emails need to be sent, and figure out why only one is being sent.

from entity.

Oge provided samples of three emails in TEST and the order they were received, can we confirm this happens in prod.

from entity.

Steps to investigate and fix:

1. Determine if we have ever sent two emails in PROD, one email after consent email sent. (you might have to ask home team if they have any logs of this before September 2023). Andriy proved in January 2024 we only send one email in prod (refer to ops ticket)
2. If we have sent two. we need to figure out why in TEST, sometimes it sends two emails and sometimes it just sends the consent email. (why we were asked to remove wording)

from entity.

@ozamani9gh are there any further updates on this one? The teams are getting quite a few calls about this one.

from entity.

I spoke with the business and they advised that:

• The output be modified and the line "You will receive another email notification with the result of the review.” be removed

• The sentence preceding this be amended to read "The consent letter for your name request NR####### has been received and processed". Adding the words “and processed”.

from entity.

More updates on this request.
Based on feedback from the users, “consent received” letter (appropriately amended to reduce confusion: see my earlier comment above) is sent. Also see a sample below

Then a second is sent confirming approval of the NR and outlining next steps. This would be the existing approval letters sent when an NR is approved. Both letters should be triggered when the consent status is set to “Received” on NameX. This would help reduce confusion about what to expect and next steps.

from entity.

Had a meeting with Jeff Zukowsli and Kathryn McAllister and they confirmed that there is only 1 email required once the consent letter has been received and the correct text of that message is located above whith the "and processed." text added.
Nothing else is required of this ticket.

from entity.

@rarmitag if only one letter is to be sent, then that letter should contain the next steps. The next steps as with normal approval mails, should be based on business types. (with links to Colin, BCROS, Forms etc.). This had been discussed earlier.

from entity.

@oanyahuru - Thanks Oge, yes the existing email seems not as thorough as it could be.
Could you get a finalized version of the single email so that we can implement that.
Thanks.

from entity.

@rarmitag i discussed this with someone from the design team. I will follow up today

from entity.

@oanyahuru - Thanks.
Don't forget to ask about ticket 20788 if you can.

from entity.

Updated design from the design:

https://www.figma.com/file/GI7PXPo7sn5hG3JkgKvvc0/Name-Request-Emails?type=design&node-id=1-2&mode=design

from entity.

For the Modernized

For COLIN and Societies

for the non-modernized:

from entity.

@oanyahuru we had to apply one quick change, we will move back to ready for QA very shortly

from entity.

@oanyahuru this ticket is ready for testing, please ensure that the PDF attachment with the emails contains accurate information.

from entity.

@semmatti the "Consent Received" letters should not have pdf attachments. please remove it

from entity.

@oanyahuru can you let Meng and Steven know when this is ready for release. this is the only ticket holding up release tommorow morning

from entity.

I am having some issues with NR letters for societies. I will finish up before 4

from entity.

@ozamani9gh the issue has been resolved and the letters all have the right links

from entity.