Understand how to productise service messaging

[MJFaucherFolie]

Context

• We are currently manually emailing 10 LPAs regarding the status of their data. As the volume of LPAs with data quality issues grows, we will need to automate this process
• We have proven the impact that service messaging can achieve, so we need to understand how to implement it into our service as a feature

Acceptance criteria

• Clear understanding of what is required to implement this feature

Tasks

• Pow-wow with Dilwoar
• Understand the requirements
• Draft tickets

[MJFaucherFolie]

On the 13th November, I had a chat with Dilwoar to understand the requirements to implement this as a feature. Below is a summary of the conversation:

To productise this, we will need substantial infrastructure support, as the Providers team does not own or maintain databases, nor do they have the capability to implement a subscription mailing service.

The process will require:

• Authentication: Users will need to authenticate in order to manage their mailing subscription, with a “magic link” mechanism to confirm the accuracy of their email address.
• Automated Email Scheduling: A Cron job will likely need to run nightly, checking which emails need to be sent based on the user’s selected frequency.

Actions:

• Double check with Charlie that this is the right approach,
• Liaise with the Infrastructure team to understand their requirements and any necessary steps for implementation.