Hi, we get a lot of overseas enquiries, the process to enrol an overseas student is quite complex & labour intensive. We get many many enquiries, the conversion rate is very low. The first email is a response to their enquiry.
I have setup a sequence, the
1st is the email with all the details, the
2nd in the sequence is a follow up a week later, the
3rd is another follow up & the
4th is a final one saying I've sent u a few emails with no reply, so thank you & a link to our website.
I want to CC another colleague in the sequence who will manage the enrolment if it happens. I am now forced to forward the email to them so they can make contact with with the prospective customer as I cannot CC them in the sequence. Often there is no reply, I send a follow up & often there is no reply. I have found myself getting bogged down with setting up numerous contacts with no result, so..... Hope this helps?
Upvote. As an Account Executive, I'm almost always communicating with 2 or more stakeholders in a deal. It's critical that my follow-up sequence includes all stakeholders. For 4 years I have been manually sending 3-4 emails that should be automated in a sequence. This can cause communication to fall through the cracks and is becoming a large bottleneck as I need to allocate valuable time to these manual email sends.
This message is explicitly intended for you HubSpot team. The first request for this feature was in 2018 and Glen in February 2021 wrote that you were working on this solution. Now, almost 4 years after Glen's response and 7 years after the first request, is there any news you would like to communicate to your users? As far as I am concerned this is a key feature.
While I'm looking forward to our family's Thanksgiving turkey, its crisp, buttery skin, the juicy meat, the hints of garlic and onion, the drizzle of that velvety gravy, I know I'll be thinking, in the back of my head, "wow, this meal would be perfect, if only Hubspot would address the cc in sequences issue frequently requested since 2018, a basic email functionality." Maybe next year.
