Context: B2B Enterprise Sales - we have a list of target accounts and there expected contract renewal dates, where we would look to engage the customer well ahead of the renewal date. Sometimes there are multiple dates (seperate contracts for territory or service type/scope).
Intended Outcome:
1. To create a list of accounts ordered by renewal date (to drive sales and marketing engagement activity and plan capacity).
2. To automate marketing and sales tasks, campaigns, sequences etc in the run up to the contract renewal date - this would be to a number of people in the organisation, not just one person.
So… how best to store these key dates? Can I create a table of dates?
e.g:
Date1 | ServiceType | Description
Date2 | ServiceType | Description
Date3 | ServiceType | Description
Or how else could this be achieved? Would it best to log this kind of information against the account, or against a contact record? How could I use these dates to create tasks and trigger activity / workflows?
Hi @ojobson I’m wondering if it might be worth creating a custom object for the service types/scope so that you can associate multiple contracts with different dates to a company record that is the target account (or contact record depending on how you’re managing sales deals vs. target accounts).
With a custom object, you open up additional reporting opportunities and can create the custom properties you need to use for automation, triggers, etc.
Curious to see what the others suggest, there are quite a few ways I think you could handle this
Thanks @TitiCuisset for the mention, I’ve been stewing on this one all day… and hoping @jolle was going to beat me to it
Happy to help here, this can be fairly straight forward.
First off, no, it’s not possible to create a table of dates. You would create separate date properties for each purpose on the company record. (You can place properties in groups, the property creation menu asks you which group the property should go into.) For any actions you’d like to automate on the contact record, you would create properties with the same names on the contact object as well.
Once you have these properties, you can create workflows based off these dates, e.g. this one:
You can then use the contact date property for re-enrollment in marketing workflows. (If you reference the company property directly instead of copying it to the contact record, re-enrollment is not an option.)
You can specify which contacts should receive these emails based on buying role, job title, persona – wherever you’ve stored the information that they should be a recipient of these emails.
