|
Skye
|
March 29, 2022 at 4:32 pm
Hello – we have been unsuccessful getting Ticket Notices, Registration Approved, and Payment Received notices formatted and delivered to the desired end point. It’s difficult to track what messages are actually being used by the system, and as a longtime user, have some legacy documents that I’m frankly not even sure what they do! I believe we’ve solved our e-mailing mystery, but still are failing epically getting copies of useful messages sent to us. Even using CC functions doesn’t work for us – dropping the ticket information so we know what a payment is for. So we could really use some help.
|
|
Tony
|
March 31, 2022 at 8:30 am
Hi there,
There’s a bit of conflicting info in your opening post so I’m not sure I follow.
For example:
we have been unsuccessful getting Ticket Notices, Registration Approved, and Payment Received notices formatted and delivered to the desired end point.
But then:
I believe we’ve solved our e-mailing mystery, but still are failing epically getting copies of useful messages sent to us.
Are you getting the above messages but just need to find a way to send copies?
—
It may be best if you can layout the issue itself, what is happening and what you want to happen with the emails and then we can go from there 🙂
|
|
Skye
|
April 1, 2022 at 6:26 am
Hi – I really did a poor job on this post – apologies. We have struggled since moving to the Office 365 cloud software, getting message notifications from EE. I’m not a coder, nor all that familiar with short codes and the like, so when we went looking for both which specific messages were generated by which activity (ticket notice and registration approved) it took a fair bit of poking around to find where we could update a cc e-mail so accounting folks got copies of ticket & payment information. It didn’t end up being all that difficult, once we found the places where we could input a direct e-mail as a cc. So User error/lack of understanding here, but we stumbled around and found a way to make it work. Apologies again for the disjointed initial post. Cheers.
|
|
Tony
|
April 1, 2022 at 8:23 am
No apology needed 🙂
Just glad you figured it out.
|
