Skip to content

Settings and activity

1 result found

  1. 733 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Hi community, we appreciate your continued feedback on having different default email addresses for various transaction types in Xero contacts, and the manual steps involved to ensure you're communicating with the right person for different purposes.

    Currently, one way of managing this in Xero would be to include every additional person on a contact record in emails, and then removing those that aren't required when sending each transaction. However we totally get this isn't the ideal solution.

    While being able to set different email addresses for differing transaction types is something we want to address longer term, like the idea for multiple addresses work for this feature requires cross-collaboration between teams in order to achieve.

    Once the multiple addresses feature is live this is something we'll be able to consider more closely and provide further updates on. 

    We do regularly review all ideas here, and your input is vital. We'll…

    An error occurred while saving the comment
    Lisa Kingdom commented  · 

    @lorinotman Yes, so ridiculous that my idea has 731 votes so far.

    Suggesting users “just include everyone and manually remove recipients each time” ignores how these workflows actually work.

    Purchase orders, remittances, invoices, and statements are often sent in bulk, by different staff, and at speed. Expecting people to manually audit email lists every time is inefficient and increases the risk of sending the wrong document to the wrong department.

    Suppliers don’t want remittances, AP doesn’t want POs, and users shouldn’t need to memorise who gets what. That’s exactly what defaults are for.

    Good software removes repetitive decisions and reduces human error. Requiring manual fixes every time isn’t a workaround. It’s evidence of a missing feature.

    An error occurred while saving the comment
    Lisa Kingdom commented  · 

    Putting forward a feature request to be able to have a contact for the initial email sent out, then all future contact (email chasers) sent to a different email address.

    We have several companies who want this process and we have to remember to do it manually.

    All quite fiddly and time consuming.

    Lisa Kingdom supported this idea  ·