I'm trying to take advantage of the new Services Object that's been recently released, and I'm not sure how to go about it. I love the idea of a service created can be associated to a contact, a company and a deal. But if i have a standard service that i would like to provide a customer, and potentially have a pipeline or automations behind it, there are no way (unless I'm missing something) to choose from a library of set services. Let's say i have 3 services, and i want to have an onboarding process for each one. And i sell one, let's say Blog Post Writing. I'd want to associate the service to the client i sold it to, the contact I'm communicating with, and the deal it was sold from. From there i can use the pipelines to trigger certain communications and keep track.
but that scenario isn't straight forward, because there is no connection with the product library I'm using to sell Blog Post Writing in my deals/quotes line items.
Maybe I'm reading this all wrong, but I'm having a hard to wrapping my head around how to and when to best use it.
While there isn't a direct connection between Services Objects and the product library used in deals/quotes, here's a practical solution:
1. Create custom properties in the Services Object to define your standard services (like Blog Post Writing) 2. Use workflows to automatically create service records when deals close 3. Set up automations to associate the service with the relevant contact, company, and deal
For example, when a Blog Post Writing deal closes:
* A workflow creates a new service record * It automatically associates with the contact, company, and deal * This triggers your onboarding process
You can track this using service-specific pipelines and custom properties to maintain the connection with your product library.