Scope

Start after a person has reviewed the request.

Maya checks the original enquiry, current conversation, assigned salesperson and whether a meeting is already arranged. She confirms the proposed contact is appropriate under the team’s communication policies. A form submission alone is not the rule for putting every contact into this sequence.

Keep this separate from cold outreach, marketing nurture and delivery handoff. The example does not connect a form, change lifecycle stages or promise a response-rate improvement.

What a follow-up sequence carries

The definition explains scheduled steps and the need for stopping rules.

Automation for commercial operations

Decide which parts of the surrounding process should run automatically.

1. Check access and create a sequence

Use a manual first step.

HubSpot documents sequences for Sales or Service Hub Professional/Enterprise, with an assigned Sales or Service seat. Creating and editing require sequence permissions. Sending uses a connected individual work inbox, not the shared conversations inbox.

Open Sales > Sequences, using More if necessary. Create a sequence from scratch and name it Demo request / reviewed follow-up. Add a General task named Review the request before contacting Alex. Enable the task option that pauses the sequence until completion. Its notes should ask Maya to check the original request and any existing conversation.

Tasks belong to the user enrolling the contact. Assign the work deliberately; do not assume the contact owner receives this task. The review task is not itself a sent reply.

HubSpot: sequence creation and task controls

Check account eligibility, task assignment and pause settings.

2. Define the small sequence

One invitation and one reminder are enough for this example.

These are proposed local choices, not an optimal sales cadence or a HubSpot default. Configure each delay against the preceding step and review the resulting schedule. The internal team chooses its own coverage and timing.

Review task

Proposed action: General task; pause until completed

What Maya checks: Is the request current, appropriate and still unanswered? If not, stop the enrollment instead of completing the task just to clear it.

Invitation

Proposed action: Automated email after the completed review

What Maya checks: Request context, recipient, sender and booking link are correct.

Reminder

Proposed action: Automated email after two business days

What Maya checks: The previewed send time fits the team’s coverage; reply and meeting stopping rules are enabled and tested.

Final review

Proposed action: General task after three further business days; pause until completed

What Maya checks: Review any response elsewhere. If unanswered, record that outcome and end this attempt rather than starting it again automatically.

Fictional invitation

Alex, you asked to see how enquiries move between the two sales teams.

I can show that handoff in the demo. Is there a particular point where requests get stuck today? If you would rather choose a time now, use the booking link below.

This is sample copy for Cedar Studio’s stated request. Maya must replace the example and add her actual, checked booking link before enrollment. Do not paste a fictional customer detail into a real template.

Fictional reminder

Alex, are you still looking at the enquiry handoff?

If so, I can keep the demo focused on that part. If the timing has changed, let me know and I will leave it with you.

Keep the reminder specific to the unanswered invitation. Do not imply Maya has checked a system, prepared a bespoke demo or spoken to someone unless that actually happened.

3. Review one enrollment

Inspect the schedule before confirming it.

Use an authorised test contact and a mailbox the team controls for the first walkthrough. In Sales > Sequences, open this sequence and select Enroll contacts. Choose the contact, then review the starting step, sender and time zone. Manual enrollment uses one of your own connected accounts.

HubSpot allows only one active sequence per contact. If another is active, investigate its purpose rather than removing it merely to make this setup work. Review message content, required values and send times before confirming; enrollment can begin the first step immediately. Here that should be the review task.

Keep automatic form enrollment outside this pilot. Maya’s review is an operating decision, not a hidden filter to be assumed later.

HubSpot: manual enrollment and schedule review

Verify the sender, active enrollment and timing controls in your account.

4. Configure and verify stopping

A reply changes the work.

Review the sequence’s reply and meeting unenrollment settings. Decide whether an action stops only this contact or other contacts at the company; the example needs only Alex stopped. HubSpot documents meeting association conditions and out-of-office exceptions, so neither event should be assumed to behave identically through every channel.

If Alex calls Maya to arrange a demo, Maya checks the enrollment and manually unenrolls when appropriate. HubSpot cannot be assumed to infer an unrecorded call outcome. Unenrollment stops upcoming steps; it cannot recall an email already sent.

If Alex asks to wait, stop this attempt and record the requested next action. Do not mark the final review complete as a substitute for resolving the conversation.

HubSpot: automatic and manual unenrollment

Check the actual reply, meeting and out-of-office exceptions.

Before operational use

Try the paths that would make a reminder inappropriate.

Use controlled test records and inboxes only. Record what actually happened; these expected outcomes are acceptance criteria, not completed tests. Check the enrollment and pending steps as well as the received email.

Try	Expected result or review
Leave the first task open	No invitation should proceed while the configured pause remains active. If it does, stop and correct the sequence.
Complete the review for the test contact	Only the approved invitation proceeds on the reviewed schedule; inspect the rendered message and booking link.
Reply before the reminder	Verify the contact leaves the sequence and no reminder remains due.
Book through the team’s real meeting path	Verify the meeting is associated correctly and enrollment stops. If not, document a manual stop and investigate the settings.
Record a phone conversation	The salesperson checks and stops the enrollment rather than assuming the note did so automatically.
Leave the invitation unanswered	The reminder and final task follow the chosen schedule; the final task creates a decision, not an endless restart.

Handover

Keep the conversation attached when the salesperson changes.

Before another person takes over, record what Alex asked to see, which message was sent and the next agreed action. Inspect the existing enrollment and task assignment; do not start another copy simply because ownership changed.

After a small controlled walkthrough, decide whether this sequence helps the team. Review missed tasks and inappropriate messages before increasing volume. A completed setup is not evidence of more meetings or better conversion.

Preserve follow-up through a handoff

Carry the request and agreed action to the next owner.

Follow up on the demo they actually asked for.