Jump to content

Search the Community

Showing results for tags 'contacts'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • The latest WHMCS Release
    • WHMCS 8.1 Release Discussion Board
  • WHMCS Beta Program
    • WHMCS Mobile App Technical Preview Feedback
  • The Latest from the WHMCS Team
    • News, Announcements & Blogs from WHMCS
  • WHMCS.Community
    • Community Announcements
    • Introduce Yourself
  • Using WHMCS
    • Pre-Sales Questions
    • Admin & Configuration Questions
    • Installation, Upgrade, and Import Support
    • Using WHMCS
    • Troubleshooting Issues
    • Vendor Discussions
  • WHMCS Showcase
    • Showcase Your Site
    • Share Your Best Practices & Tips
  • Developing & Extending WHMCS
    • Third Party Add-ons
    • Service Offers & Requests
    • Developer Corner
    • Building Modules
    • Share Ideas for WHMCS Modules
  • Community Competitions
    • Competitions
  • General Discussions
    • General Discussion
  • General Feedback & Assistance
    • Feedback
    • WHMCS.Community Tips & Tricks
  • Third Party Developers's Topics
  • Turkish International Discussions's Topics
  • Russian International Discussions's Topics
  • Spanish International Discussions's Topics
  • Portuguese International Discussions's Topics
  • French International Discussions's Topics
  • Italian International Discussions's Topics
  • German International Discussions's Topics
  • WHMCS Brasil's Topics
  • WHMCS Brasil's Tópicos
  • ModulesGarden Club's Topics
  • Hungarian International Discussions's Segítség
  • ThemeMetro Club's Topics
  • WHMCS Services Club's Topics
  • SwiftModders Club's Topics
  • WHMCS Global Services Club's Topics
  • Katamaze's Free Scripts
  • Katamaze's Modules
  • Zomex Club's Topics
  • 0100Dev Club's Topics

WHMCS Version

  • V8.1.x Hotfixes
  • V8.0.x Hotfixes
  • V7.10.x Hotfixes
  • V7.9.x Hotfixes

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



About Me

Found 5 results

  1. I'm glad WHMCS finally came around to introducing this, however is there a way to convert our years and years of contacts/sub accounts into users?
  2. If more than one contact exists, when logged in as a contact, the name of the first contact is the one displayed on the header bar (next to logout link). How can I resolve this issue? We're using version 7.10.2
  3. Whether adding a new contact or editing an existing one, I get the validation error seen on the image. Validation ErrorThe email address entered is already in use by another client account and must be unique for each client
  4. Hi all, I think it's time to solve once and for all the problem with the ticket system and email templates - regarding the main contact / master account holder receiving all the emails - even the ones regarding a ticket that was opened by a sub account or a contact person from his organization. The current state creates an overburden on the "master account holder" and causes misunderstandings who opens the ticket and so on (not to mentioned the spam to unnecessary participants). Please follow this scenario: - We have a company (let's name her "Macrosoft Ltd"). - We have in our WHMCS 4 contacts: 1. The master account holder - let's say his name is Tom Cruise and his rule is purchasing manager. 2. The support manager - Matt LeBlanc. 3. The sales manager - John Oliver. 4. The CEO - Elizabeth Tudor Problem #1: - When Matt opens a ticket he get an automated mail stating: Tom Cruise (Macrosoft Ltd), Thank you for contacting our support team. A support ticket has now been opened for your request and you will be notified by email when a response is made. - Please note that the ticket was opened by Matt LeBlanc - not by Tom Cruise!! Matt ask himself - WTF... I opened this ticket not Tom... - The same mail is sent also to the "master account holder" - Tom Cruise. Tom ask himself - WTF... I don't recall opening any ticket lately.... Problem #2: - In our WHMCS we see under the submitter field - Tom Cruise (Macrosoft Ltd) (although the ticket was opened by Matt LeBlanc) - only when looking inside the ticket we can see that is was submitted by "Matt LeBlanc (Macrosoft Ltd) Contact" Problem #3: - Any reply we make to Matt LeBlanc's ticket is also sent to Tom Cruise Tom ask himself - WTF... why do I keep getting this mails? (now take under consideration that Tom gets such an emails for all the tickets opened by Matt, John and Elizabeth - it can accumulate to lots of mails that's spams Tom mailbox!!!) Problem #4: - Let's say we want to sent a new quote to Elizabeth Tudor the CEO of Macrosoft Ltd Again the quote is sent to Tom (and any other contact that have the relevant Email Notifications setting) and to Elizabeth. and again - the name in the mail and on the quote is Tom and not Elizabeth!! Actually any email template that have the {$client_name} merge fields will be of Tom regardless who is the relevant contact that should receive such a mail / notification / quote etc. To sum it all up - there is a huge mix-up and confusion while using the Clients Information / master account holder information/ {$client_name}merge fields not to mentioned the amount of spam received to the email address registered under the Clients Information / master account holder. This is something relevant to any customer with more then one contact - so I'm sure that lots of WHMCS users face the same problem. If those problems weren't enough let's have few more: Problem #5 - Sometimes John Oliver sends a mail to Matt LeBlanc and add us in this mail in CC. A new ticket is opened with John Oliver set as the relevant contact. - Like stated before - Tom get's the email (and his name in the mail) - There is no way for us to see we are not the ones this mail is sent to (we are only in CC on the original mail). - If we reply to this ticket - only John (and Tom) will get the answer - nothing will be sent to Matt (unless we manually add his mail to the CC of the ticket - but there is no indication for us to do so). To sum it all up, I can't see the logic or advantages in the current situation - It create lots of problems and spam in any company that have more then one contact. I think that creating a clear and strict use of the relevant contact across WHMCS ticket, email templates and any other part of WHMCS - is mandatory. Every act we do should be related to a specific contact and only him. In the Feature requests system I found several relevant request: 12 votes - Client Contact Ticket Management https://requests.whmcs.com/responses/client-contact-ticket-management 7 votes - Disable Email to the main account e-mail https://requests.whmcs.com/responses/disable-email-to-the-main-account-e-mail 4 votes - Support ticket notifications - limit to contact participating https://requests.whmcs.com/responses/support-ticket-notifications-limit-to-contact-participating 4 votes - Improve email personalisation https://requests.whmcs.com/responses/improve-email-personalisation Total of 27 votes regarding the problem with the contact management. I think that WHMCS team should read this post and see the problems stated here and find a solution A.S.A.P But If from some strange reason it's not obvious this issue should be fixed - please please please add your votes. Thanks! Ram Thanks, Ram
  5. Hi All, Is it possible to associate historical support tickets in WHMCS to Company, i.e. *after* you add the submitter as an additional contact record for a company in WHMCS? Or does this happen automatically? We've just noticed/realised that lots of tickets have been received by a client who was not recognised by WHMCS because the client's email address was not recorded as a contact in WHMCS. So we've now added the contact using the email address that matches all the tickets he's been sending, but there's no sign of any linking of historical tickets to that newly added contact record. Thanks, Ross
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated