All Members Community

 View Only
  • 1.  iLab disables Message Customers feature

    Posted yesterday

    Anyone who uses iLab and have more than 45 customers in the database  needs to be aware of this new policy.  

    iLab is supposed to be one complete customer database to meet our needs.

    Throttling emails contacts to any number smaller than our complete customer list removes a key function we rely on.  The appropriate size of a recipient group is based on each message.  Sometimes this is five.  Sometimes this is 300.

    They offered to determine the best setup for our use case and said that they would be happy to assist.  We already know this.  Being able to email up to the number of every customer who used any of our services in the last three years is precisely why we purchased iLab.

    Even worse, we were not notified of this change so we wasted hours with their service ticketing system, where you have to wait overnight for a response.  And then they lectured us on how to communicate with our customers.  What they really said here is that their product cannot email more than a few people at a time and they are not interested in correcting this.

    From Agilent:

    Hi Michael,

    As part of recent improvements to how system emails are handled, we have standardized the maximum number of recipients per message to 45. This change was made to ensure consistent delivery, better performance, and a more usable experience as message volume and platform usage continue to grow. From a practical standpoint, this brings a few benefits, as noted below:

    • Keeping recipient counts within this range helps avoid delays or dropped messages, especially during peak usage.
    • Messages are delivered more quickly and consistently when sent to appropriately sized recipient groups.
    • Targeted notifications reduce inbox noise and make it easier for recipients to act on messages.
    • This approach allows the system to scale without degrading performance for all users.

    For cases where you need to notify a broader audience, we recommend using a shared distribution list or group email address, which provides the same visibility while keeping delivery reliable.

    Please let us know if you would like help determining the best setup for your use case and we will be happy to assist.

    ---------------------------------------------------------------------------------



    ------------------------------
    Michael Cammer
    Sr. Research Scientist
    NYU School of Medicine Langone Medical Center
    New York NY
    ------------------------------


  • 2.  RE: iLab disables Message Customers feature

    Posted 2 hours ago

    Michael,

      Thank you for sharing this.  I have a current internal ticket from a core director that has been puzzling me, because in my testing (1-3 users) emails sent find, but his attempted usage during a recent outage did not work.  Now I know why.

    We have our weekly update call with our Agilent rep in a little less than an hour and I will bring this up as another example of changes being pushed without adequate notices, or any feedback or testing from the customers.

    My initial thoughts are in line with you, that this is a terrible change and effectively breaks the functionality/usefulness of the advanced messaging features. What is the use of custom date ranges and selecting/deselecting instruments if I then have no easy mechanism to export that groupings emails? 

    External email distribution lists won't have the usage/equipment data to narrow to the targeted group.

    *sigh*  



    ------------------------------
    Hugh Gardner
    iLab Coordinator
    Purdue University
    West Lafayette IN
    ------------------------------



  • 3.  RE: iLab disables Message Customers feature

    Posted 2 hours ago

    Thank you for sharing this information. I was unaware.

    I don't generally send messages to large lists of people from iLab as they are too easily banished to someone's Junk folder or simly easy to ignore.  Being that the communications come from Agilent or iLab and not my work email address.

    I typically use the reporting feature to set a date range, export to xls and then create a mailing list in OutLook or Constant Contact for emails to larger groups.  Again, because my emails from in the system weren't really reaching people as reliably as I would have liked.



    ------------------------------
    Tom McHugh
    Director, Research Cores Administration
    University of Maryland School of Medicine
    Baltimore MD
    ------------------------------



  • 4.  RE: iLab disables Message Customers feature

    Posted an hour ago

    I understand the problem with people ignoring the emails from Agilent.

    But this is a problem on the users' side.  We tell them that they need to pay attention to these emails.

    We provide notice of instrument shutdowns, service, new features, changes in billing, etc. via the iLab messaging system.  We tell users that they need to pay attention to these messages.  If  they miss something, it's their fault.  We give notice; if they refuse to read the notices, then this is their problem, not ours.

    Messaging is a key feature which led to the purchase of iLab here. 

    Every time we need to send  an group email, we are not going to create a report, move it to Excel, remove duplicates, concatenate a ";" on each email address, and then paste into Outlook.  We would need to do this every time we need to send a message because new users are constantly being added and sometimes we only need to send messages to people who used the equipment in the last two weeks and sometimes its two years.

    Also, we get tons of undelivered message errors back when we do this.  A feature sorely missing from iLab's database is a field and checkbox  called "Gone", a simple binary which would stop people who are gone from the institution or our core from being sent emails. 

    Cheers-

     

     

     

     

     

    Michael Cammer, Sr Research Scientist, DART Microscopy Laboratory

    NYU Langone Health, 540 First Avenue, New York, NY  10016

    Office: RB (formerly Skirball) 4-102  -- call if door is locked (phone near elevators)

    Office: 646-501-0567 Cell (voice only, not text): 914-309-3270  Michael.Cammer@med.nyu.edu  

    http://nyulmc.org/micros  http://microscopynotes.com/ 

    DO NOT SEND A REACTION.  IF YOU WANT ME TO SEE A REPLY, SEND A NORMAL EMAIL REPLY.
    Similarly, I do not monitor Webex messages, texts, Slack, or other channels.  Send all written requests and replies to this email address.

    Scheduling the time you want is far more reliable by phone call.  Why not provide your phone number?

     

    ______________________________________
    This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain information that is proprietary, confidential, and exempt from disclosure under applicable law. Any unauthorized review, use, disclosure, or distribution is prohibited. If you have received this email in error please notify the sender by return email and delete the original message. Please note, the recipient should check this email and any attachments for the presence of viruses. The organization accepts no liability for any damage caused by any virus transmitted by this email.





  • 5.  RE: iLab disables Message Customers feature

    Posted an hour ago

    Michael,

      I am being told that the info you were sent is not completely correct and reflect the current status (a limit of 45) while an issue is being worked on.  I suggested that they give your rep something official and more informative to send you.  Hopefully they send an update soon.



    ------------------------------
    Hugh Gardner
    iLab Coordinator
    Purdue University
    West Lafayette IN
    ------------------------------



  • 6.  RE: iLab disables Message Customers feature

    Posted 22 minutes ago
    Utoh, this is not good or helpful at all.  

    Can we all who have iLabs get together and work with iLabs to allow more/better email communications within iLabs? This is of course one of the reasons we are switching, also.  My instituation in in the middle of setting up iLabs and my core is in the first wave to move...
    We are still setting things up.

    I feel like functionality is being removed from iLabs (maybe we should have gone with Stratacore, but too late now). ��

    Thanks for any more info on this impact on other cores out there -
    Lisa Cameron
    Light Microscopy Core Facility
    Duke University