Skip to content

Settings and activity

1 result found

  1. 148 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 everyone, there’s been a lot of thoughtful input shared on this idea, and we understand the efficiency and value this could bring for teams working with large or fast-changing contact lists.

    While this request is not in the pipeline, that does not mean the need has gone unnoticed.

    Your feedback continues to shape how we look at these gaps, and we appreciate you taking the time to explain what this would mean for your workflows.

    We know this might not be the outcome many of you were hoping for. This idea will remain open for votes so we can continue to capture support, and we'll make sure to post here if the status changes in future.

    An error occurred while saving the comment
    Scott Vaughan commented  · 

    Also, another feature missing related to account number is when you are doing a bulk import you cannot target the import based on account number. This should be treated as key field as it should be a unique number to then allow for data import.

    I find data import by customer name sometimes has issues with names being clipped and new accounts created due 3rd party system exports messing up the customer's name for longer entries, but when the list is huge no one is going to go through each one to check.

    Scott Vaughan supported this idea  ·