Help the conversation move
An acknowledgement, a requested file or a reminder can remove repetitive admin. Begin with what the person expects to receive and give the message a clear stopping rule. The guide follows these patterns without assuming that every reply needs to be drafted or sent automatically.
Describe delivery honestly
A saved request, a message accepted by a provider and a message received by a person are different states. Keep enough information to investigate an uncertain result before sending again. Test the repeated-request case and make the recovery text understandable to someone who has never seen the workflow.
Keep separate choices separate
A resource request is a request for a resource. A newsletter subscription is a separate choice. The guide links to current ICO guidance and the provider documentation so you can check the rules and behaviour relevant to your own message. Use invented addresses and controlled recipients while developing the process.