EyezOn Forum

I have some comments that I think can improve alarm reporting capability by email and SMS. Please consider these for your service.

1. Why not call a "closing" an "authorized arm" and an "opening" an "authorized disarm?" While the contact ID standard may agree with your terminology, "arm" and "disarm" are more easily understood by end-users.

2. Why not have all email reports be sent from a single address? Currently some come from "noreply@eyezon.com" and others come from "noreply@envisacorp.com." The current operation causes two separate message threads on my smartphone rather than one.

3. Why not suppress additional recipients in the "to" field by using BCC? Your current way of doing things causes multiple address message threads in a smartphone when some messages are sent to multiple recipients and others are sent to a single recipient or to a different "to" list.

4. It would be nice to suppress "location" and "partition" fields in the emails and especially text messages when only a single location and partition are in use in the account.

5. When I receive a text message, the subject line and first line of the alarm text message duplicate each other. It would be nice to see this information only once (in the subject) for text messages and not repeat it in the body text.

6. A zone bypass and zone bypass restored are both reported as "Security Event: <zone name> Bypassed."

7. A "manual trigger test" is reported as a "periodic test report." It would be nice to report a "manual trigger test" as a "manual trigger test."

1. We only use standard security industry terminology. We don't dumb-down anything.

2. All automated reports/alerts from Eyezon come from noreply@eyezon.com. If you see anything from Envisacor then it must have something to do with the bounce header and your mail client shouldn't show this.

3. This came up before and the reason I'm told is that all alerts are sent as one single message to the mail queues. To do BCC you would need to split into multiple messages and that currently isn't how the system works.

4. You can. Just select SMS style of notifications instead of FULL, when you set up your contact.

5. See above

6. Ok, I'll email the developers for you.

7. See above

Thank you for your quick response.

2. The sms messages from envisacorp.com stopped on Friday. All since that time are from eyezon.com. I'll see if any future ones come from envisacorp.com. These were not bounce messages to my phone.

3. I just checked this and there multiple SMTP RCPT commands, but the data is only transferred once and this is just a single email. Even if multiple emails were required, it seems that a property owner may not want all recipients to know who all the other recipients are and what their email/sms numbers are. Please consider this change.

4. The contact is set up as "SMS Style w/o Partition." Location and partition fields are still shown.

5. Based on your response it sounds like when "SMS style w/o partition" is selected, I should not see the same phrase in subject and body of the SMS. Since I started with this service, this is not what I am observing on my smartphone with "SMS style w/o partition" selected for my contact type.

6. Thank you.

7. Thank you.

hokie21 wrote:Thank you for your quick response.

2. The sms messages from envisacorp.com stopped on Friday. All since that time are from eyezon.com. I'll see if any future ones come from envisacorp.com. These were not bounce messages to my phone.

Nothing to do with us. It must be a change with your cell provider. When I say "bounce", I mean where the bounce from you would go if your account didn't exist anymore. This is transmitted to your ISP in a seperate header called the REPLY_TO header.

hokie21 wrote: 3. I just checked this and there multiple SMTP RCPT commands, but the data is only transferred once and this is just a single email. Even if multiple emails were required, it seems that a property owner may not want all recipients to know who all the other recipients are and what their email/sms numbers are. Please consider this change.

Out of my hands my friend. This is just the way the back-end gurus do things. If you are a landlord there are many extra features available to you in our Envisalerts+ service that might be of interest to you.

hokie21 wrote: 4. The contact is set up as "SMS Style w/o Partition." Location and partition fields are still shown.

You may have fallen into a trap relating to your 3rd question. There is a FAQ about this too. If you select multiple contacts for an event, the event will be transmitted in the most "wordy" version selected for each contact. That is, if you have one contact selected as Full Style and another as SMS, the alert will go to both as Full Style.

hokie21 wrote: 5. Based on your response it sounds like when "SMS style w/o partition" is selected, I should not see the same phrase in subject and body of the SMS. Since I started with this service, this is not what I am observing on my smartphone with "SMS style w/o partition" selected for my contact type.

Look at my response for #4. I think it's the same issue.

Thanks for the feedback and Enjoy your Envisalink!

Regarding 4 and 5...

As you said, when I made all contacts "SMS style" it did shorten the message. Location is still included, although with only one location on the account, it doesn't add value in my case.

I view the SMS/email setting implementation as a fault, not "working as designed" based on standard GUI design practices. If a common style is required for all contacts there should be a separate global setting that sets the email/sms style for all contacts. When each contact is allowed to be set to "SMS" or "Email" independently, you expect them to actually operate independently.

I realize you are not the product designer or product manager for this and that you simply support what that team produces. Would you please send this thread by them however? I signed up for envisalarm service today and would like to at least get my comments in front of the product team.

Thanks