Good morning Tessiturians!
I have a question regarding scheduled reports in a Consortium Environment. Since we're sharing a database and report server we had our IT Vendor set-up a generic "reports@ticketssb.org" account rather than our previous use of "boxoffice@granadasb.org" to prevent any confusion with the various presenters across the consortium.
However, if anyone replies to a report with this generic account we're the only member that receives the reply. I can't help but think that there must be a better way to manage these.
How have other Consortiums dealt with this issue? Any suggestions on what we might be able to do?
Thanks!Short
Not sure there's a really good way around that. Not sure what circumstances would warrant someone replying to an automatically generated email. But you might be able to set up some forwarding rules in Outlook based on the domain of the person replying that would send the message on to someone else in that organization.
- Levi
We're not in a consortium, but we sometimes will just make an auto response message that says something like 'Oops. This isn't the email to mail to.' And then let them figure out who to actually mail it to.
- Heather
We could change the from address to a fake noreply@ address so that when they reply it bounces.....
Thanks, everyone. So far this is only the second time that this has happened in a year, so it's not a huge problem currently. Though we are planning to add more partners to the consortium so it may become a problem down the line.
I've been surprised by the number of presenters/agents/managers reply directly to the automatically generated report. Sometimes they reply to a previous report to let us know that they didn't receive the scheduled report for that day. Other times, like this one, they reply to say thanks!
Heather, is SRT a RAMP client? If so, I think that might be the way to go. My understanding is that the reports@ eaddress is a mask covering for boxoffice@granadasb.org but Jennifer would likely know more about this than me. :)
Jennifer, would there be a way to bounce a reply akin to Heather's suggestion? The only downside to that would be that we might need to add each Consortium Member's eaddress to the email, which may not be the best solution. :(
You can also train everyone who schedules a report to include a line of explanation in the body of the email. Something as simple as "This is an auto generated email. Please direct all replies to me@myorganization."
It doesn't stop them from clicking Reply, of course, but it does give them instructions for what they should do instead.
Jared