Skip to content
← Ideas and Feedback

Have an idea for a new feature?

Ideas and Feedback: Customers

Categories

(thinking…)

Customer Contact

The same customer contact should be able to be assigned to several customers.
We have contacts which need to be assigned to multiple customers. At the moment, a contact (because of the email address) can only occur with one customer.

70 votes

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Bernhard Reber shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Under Review  ·  Nir Gilbert responded  · 

Nice! The feature you requested is being considered for development. We’ll keep an eye on the number of votes, and let you know if a decision is reached to implement. Thank you for being a partner in our process!

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Andrew.Beardman commented  ·   ·  Report

    This is a must have for me as well. I am starting a new MSP business after working in the Point of Sale industry for over 10 years, and I'm bring on a ton of restaurant clients that all have their own contracts. Sometimes I have 1 contact for anywhere from 2 to 10 restaurants and this will be a deal breaker.

    They also should be able to log into the customer portal and see every business they are assigned to.

  • SmarterDesk Tech (ProtoLogic) commented  ·   ·  Report

    Although I do agree it is essential, it will open up a big can of worms and expose problems with the Atera data structure. I'll provide one simple example here but there are many others. When you create a ticket (#1012) and you work on Workstation #1 for the contact bob@acme.com and then subsequently create another ticket (#1013) to work on Server #1 for bob@acme.com, the computer (Agent) you worked on in the first ticket (Workstation #1) will be changed to Server #1 that you worked on in the second ticket. The Agent follows the user so that unrelated tickets are changing the agent in other tickets as you are working.

    I really do need bob@acme.com to be a contact for more than one Company and have upvoted this. People have been asking for this for several years. ***BUT*** the way it is now, if we do this, my ticket working on Workstation #1 over at Wonder Pool Cleaning is now going to show that I worked on FrontCounter #4 over at the Ford dealer ship if the next thing bob@acme.com asks me to work on is at Ford instead of Wonder.

    I'll leave it at that but if you think about the way this is currently designed and expand your thoughts a bit into billing and auditability of the work records and other considerations many of us have to deal with, I think you will see that any simple solution to let us do this will be opening one giant can of worms in many, many ways.

    Like most development, if you get the data structure right at the foundation level, things are just magically possible as your user base helps you move forward. If you don't, it is almost inevitable that you will need to make foundational changes and do data conversions to a live system with a lot of legacy information recorded in it.

  • Scott Tindall commented  ·   ·  Report

    Agreed. I have company owners with multiple businesses and I can only assign them to one and then create alias emails for every business.