When creating new customers from the call handler, it would be fantastic if the tax code could be added at the time the customer is created.
Brian Mangan
| Company | Dave Jones Inc. |
| Job Title / Role | IT Manager |
| I need it... | Yesterday...Come on already |
Dear Viewpoint Suggestion Box contributor;
We at Viewpoint sincerely thank you for your contribution to Suggestion Box on how we can improve Viewpoint products. While we can’t do everything at once, we rely upon your feedback to help guide the prioritization of our product improvements, and Suggestion Box is a critical tool for us to understand and prioritize our customers’ needs.
Viewpoint reviews Suggestion Box regularly for all of our products and updates statuses, adds comments, and performs various house-keeping (including deleting) as needed to ensure that Suggestion Box is maintained as a productive environment for product enhancements requests.
© 2023 Trimble Inc. All Rights Reserved. Viewpoint®, Vista™, Spectrum®, ProContractor™, Jobpac Connect™, Viewpoint Team™, Viewpoint Analytics™, Viewpoint Field View™, Viewpoint Estimating™, Viewpoint For Projects™, Viewpoint HR Management™, Viewpoint Field Management™, Viewpoint Financial Controls™, Vista Field Service™, Spectrum Service Tech™, ViewpointOne™, ProjectSight® and Trimble Construction One™ are trademarks or registered trademarks of Trimble Inc. or its affiliates in the United States and other countries. Other names and brands may be claimed as the property of others.
Perhaps there should be a way to "Setup Site" from this window wherein the user can create the site, add the taxcode, contacts, default items, and other stuff.
Either VP will need to expand this "Call Handler" window, or provide a slightly different workflow so additional info can be added to the site/customer for NEW site/customers.
Ideally this would also add the tax code to the site that is being created.
Another item that you should be able to add from here is the customers email address.
This is unacceptable that this issue has not yet been corrected, as it worked correctly prior to the latest version update. Please revolve quickly!