The first follow-up usually gets sent. The second depends on someone's task list. By the fourth, nobody is quite sure what the prospect has received.
A good follow-up strategy needs a way to carry it out consistently. Ariyel Sequences gives your team scheduled email steps, a controlled sending window, and a view of what happened for each enrolled contact.
You decide the message and cadence. Ariyel handles the scheduled steps when the sending requirements are met.
Give each email a job
Imagine a prospect has asked about your service and had an initial conversation. Your next few emails could answer a common question, explain what getting started involves, and offer a clear next step.
Build that journey in Sequences → New sequence. Add each email's subject, body, and delay. Use the supported email variables for personal details, and review the wording around them so the message still reads naturally.
Make every step useful on its own. An email that only says “checking in” asks for attention without offering much back. A short explanation of a common concern gives the recipient a reason to respond.
The sequence supports the plan you put into it. Choose contacts for whom that plan makes sense, and keep the message connected to the conversation they are actually having with your business.
Prepare the sender before enrolling contacts
Sequence mail uses your workspace's verified default sending domain. An owner or admin configures that domain under Settings → Sending domain and completes the displayed verification steps.
You also need the intended sender's connected Google mailbox. Choose that member under Replies go to, so responses reach the person responsible for the conversation.
The sending domain and reply mailbox serve different purposes. Sequence messages leave from the workspace domain; replies go to the connected mailbox. Sequence sending is separate from writing a one-to-one Gmail message inside Ariyel.
Choose a deliberate cadence
Review the sending window, timezone, weekday restriction, sender, and exit settings before publishing. These settings determine how the sequence fits around the delays you wrote into it.
A day delay is a calendar-day delay adjusted into the allowed sending window. It is not automatically a count of business days. Check how your chosen cadence behaves around weekends before using it broadly.
An owner or admin publishes the sequence, then turns on Enable sequence when it is ready to send. Publishing and enabling are separate steps.
Follow the recipient, not just the sequence
In Recipients, choose Enroll recipients and select an eligible existing contact. Someone already active in the same sequence is excluded, and suppression or blocklist rules can prevent enrollment.
Open a recipient's journey to review confirmed sends, future steps, and hold or exit reasons. “Active” describes their enrollment; it does not guarantee that an email is currently delivering.
If a sender mailbox or domain becomes unavailable, a recipient can be held. Read the reason and inspect the journey before taking action. Repeatedly enrolling someone is not a substitute for understanding the hold.
Change the plan with care
Each enrollment keeps the published steps and settings it started with. Publishing an improved version changes the journey for new enrollments, while existing recipients stay on their original version.
You can exit an individual recipient or switch the sequence off to block further sends. A message already handed to the mail provider can still complete.
Start with a short, relevant sequence and review real recipient journeys as you use it. For domain setup, publishing, enrollment, and hold details, read the Sequences documentation. To connect enrollment to a record event, explore Ariyel Workflows.