La fonction de suggestion automatique permet d'affiner rapidement votre recherche en suggérant des correspondances possibles au fur et à mesure de la frappe.
We are working with a custom object ("Projects") for our post-sales Delivery and onboarding process. Playbooks are available on all standard objects (Companies, Contacts, Deals, Tickets), but not Custom Objects. This would be such a game changer for our team to have access to Playbooks - all the users of our custom object have paid Service Enterprise seats to access other paid features like snippits and templates, but we're really missing Playbooks on this custom object.
WHO: users of custom objects, in our case - post-sales Delivery, for whom Deals and Tickets aren't quite suitable objects to use.
GOAL: leverage Playbooks to embed working instructions in a custom object, and standardize the collection of critical data properties during the various pipeline stages for the custom object
VALUE: easy onboarding of new team members, structured gathering of information and notes/documentation
EXAMPLES: literally the same way Playbooks can be used on Contacts, Companies, Deals, and Tickets 😁
This is exactly the feature I am looking for! We have Applications (a custom object) that are associated to Contacts.
Contacts can have multiple Applications. We are looking to use playbooks to store Application information that is asked during a call using a playbook.
We cannot save the information to a contact, as one contact can have different information for different Applications.
Any workaround for updating a record property on a custom object while using playbooks?
Yes this would be very beneficial, particularly as the original poster suggested, as a "how to" guide for the proper use and formatting of custom objects
Couldn't agree more! What's strange is you can now have playbooks with properties that write to custom object properties but somehow you can't display the playbooks on the right sidebar of a custom object. Seems a little backwards.
Yes please. The purpose of having a CO would be that there's a unique use case, such, there needs to be playbooks that help users walk through using that object.
Pour ajouter un commentaire ici, vous devez être inscrit. Si vous êtes déjà inscrit, connectez-vous. Dans le cas contraire, inscrivez-vous puis connectez-vous.