Discussions
Read on for the latest updates including:
• Agenda Builder launch
• SuiteWorld On Air registration
• New NetSuite Prompt Studio Contest
• And more!
Check out this thread to learn more!
Don’t miss your chance to meet our SuiteGurus—NetSuite Support professionals and subject matter experts with extensive experience in select product areas, including OneWorld, Advanced & Basic Accounting, Supply Chain Management, Receivables & Payables, CRM, Account Administration, and the SuiteCloud Platform. Full Conference attendees can prebook exclusive 30-minute one-on-one sessions for your product questions.
Spots are limited! Register through your Agenda Builder and find SuiteGuru under Agenda Enhancements.
Trying to understand advantages of jobs vs sub-customer and access limitations
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).