Thank you Derek for posting this, and Sam for merging it with the existing idea! In order to get MessageBee to send these reminder notices, we have had to do some weird workarounds that are not desirable. Including these in the export file so that all vendors could use them would be great.

Two quick comments. First, because the integration leverages our existing export notices feature, I would expect adding reminder notices to the export files would apply to any vendor the library is using that consumes those files.

Second, there was another idea related to reminder notice exports which I have merged into this idea. The original idea comments can be seen below. It mentioned duplicate notices if exporting to a vendor, but that is not possible through supported channels for exporting notices. Since Polaris currently does not export these notices, they will not be included in the export file we provide and Polaris will continue to send them. (I can confirm MessageBee does not receive or send reminder notices and it is a desired enhancement for them).

We've run into this issue as well, and it's a bit of a pain to explain to people that autorenewals aren't included in the FTP export.

If you use a third-party service like MessageBee or Shout Bomb to deliver your text notices, Polaris must FTP export your notices to the third-party (or something similar).

Polaris considers auto-renewals "reminders" not "notices" so they are not included in the FTP export that you set up through SA. This means there's no good way to shut off their export from System Administration. Patrons wind up with double auto-renewal notices - one from the third-party and another from Polaris.

I'd like the ability to include auto-renewals in FTP export from System Administration to prevent sending double texts to our patrons.