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 currently assign an SQL to a salesperson once the contact has downloaded 3+ items or completes a contact us form.
The SQL is assigned to a salesperson who follows up. Depending on how that follow up goes, we might not hear from that contact for a few weeks, months, even a year.
I want to notify the salesperson when that contact next visits our website, or downloads a new item.
There are different ways of approaching this, here's how I'd start. (Sorry for the small font size, the forum seems to compress this automatically. Let me know if it's legible.)
You can wait longer or shorter (see Last activity date) before notifying sales representatives. Something to keep in mind about this setup is that the contact might engage in the 13 days after the last sales activity – but this workflow is currently not notifying the contact owner about it. Only when a certain threshold is met (Last activity date + number of days) will a sales person receive a notification. Without this wait time, you would be sending notifications all over the place whenever a SQL interacts with any content after talking to a sales person. The finetuning of how long you wait would be up to you.
The branches are also in hierarchical order: A form submission always goes hand in hand with a page view and likely a marketing email open, that's why it goes first. A marketing email open likely goes hand in hand with a page view. (You could by the way replace this with Last marketing email click date.) A page view on its own would be the least interesting in my opinion, hence it comes last.
Re-enrollment would probably look like this:
The notification body could look like this. (Replace "1234567" in the URL with your portal ID.)
Obviously, you want to test this workflow on a small scale before unleashing it on your sales team. You could pilot this with one sales rep (by adding an additional enrollment criterion in each of the OR buckets, "Contact owner is [sales rep for pilot]".
Hope this helps!
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer
There are different ways of approaching this, here's how I'd start. (Sorry for the small font size, the forum seems to compress this automatically. Let me know if it's legible.)
You can wait longer or shorter (see Last activity date) before notifying sales representatives. Something to keep in mind about this setup is that the contact might engage in the 13 days after the last sales activity – but this workflow is currently not notifying the contact owner about it. Only when a certain threshold is met (Last activity date + number of days) will a sales person receive a notification. Without this wait time, you would be sending notifications all over the place whenever a SQL interacts with any content after talking to a sales person. The finetuning of how long you wait would be up to you.
The branches are also in hierarchical order: A form submission always goes hand in hand with a page view and likely a marketing email open, that's why it goes first. A marketing email open likely goes hand in hand with a page view. (You could by the way replace this with Last marketing email click date.) A page view on its own would be the least interesting in my opinion, hence it comes last.
Re-enrollment would probably look like this:
The notification body could look like this. (Replace "1234567" in the URL with your portal ID.)
Obviously, you want to test this workflow on a small scale before unleashing it on your sales team. You could pilot this with one sales rep (by adding an additional enrollment criterion in each of the OR buckets, "Contact owner is [sales rep for pilot]".
Hope this helps!
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer