Share with colleagues and friends who could benefit from our webinars too!
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).