Check out Oracle NetSuite upcoming events and conferences here
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
Update your Profile with your Support type to get your Support Type badge.
Don't miss out on our Pop Quiz ! You only have until February 29, 2024, 2 PM ET to comment your answers and earn rewards! Click here for more details.
Discover NetSuite's potential! Join our webinars, learn from experts, and optimize your operations. Whether you're experienced or new, secure your spot today and stay ahead in NetSuite!
Share with colleagues and friends who could benefit from our webinars too!
Don't miss out on our Question of the week! You only have until tomorrow, February 29, 2024, 2PM ET to comment your answers and earn rewards! Click here for more details.

Trying to understand advantages of jobs vs sub-customer and access limitations

edited Nov 22, 2019 10:33AM in CRM 2 comments

I'm trying to decide on the best approach for handling customers with multiple implementations of my clients product. In some cases they are evals or betas, in other cases they are multiple installations using for different reasons.

I see that Jobs may work for betas and evals since these have a beginning and an end to them, whereas multiple installations are permanent and may make more sense to be treated as sub-customer.

I like the fact that I can assign different contacts access to the customer center using the sub-customer record approach. This would be great for evals where I may want to setup a Eval Customer Center role to handle evals separately from the main customer support cases (eval cases route to sales, production cases route to support).

Howdy, Stranger!

Log In

To view full details, sign in.


Don't have an account? Click here to get started!


Community Whiz

Quarter 1 (Jan-Mar 2024)

This Week's Leaders

This Month's Leaders

All Time Leaders