TL;DR: A workflow partial send batch lets insurance agents send messages to a controlled subset of leads — not the entire pipeline at once. This staged approach reduces deliverability risk, prevents calendar flooding, and gives you precise control over who gets contacted and when, without rebuilding your entire automation.
Most agents set up a workflow and let it rip — every lead in the pipeline gets hit at the same time. That works fine when you have 20 contacts. It becomes a serious problem when you have 200, 2,000, or a reactivation list of dormant leads you’ve been sitting on for six months.
A workflow partial send batch solves this. Instead of blasting your entire list in one go, you send messages to a controlled subset — a defined number of contacts per day, per hour, or by a specific segment — and let the rest queue behind them. This approach is a cornerstone of insurance workflow automation that keeps your operations scalable.
This guide covers how partial send batching works inside CRM workflows, the four real scenarios where insurance agents need it most, how to set it up, and what to do when things go sideways.
What Is a Workflow Partial Send Batch?
A workflow partial send batch is a configuration within an automation sequence that restricts how many contacts receive a given message step within a defined time window. Rather than triggering every enrolled contact at once, the system meters contacts through the workflow in smaller groups — a batch.
This matters for three reasons:
Deliverability. SMS carriers and email providers flag sudden spikes in outbound volume from a single sender. A batch of 1,500 SMS messages sent in two minutes is a spam signal. Batching those messages over 24-48 hours keeps your sender score healthy and your texts landing in inboxes — not getting blocked. If you’re running A2P-registered campaigns, this is especially important. Setting up A2P correctly is a prerequisite — batching on top of a misconfigured sender profile won’t save you.
Calendar capacity. If your AI books appointments and you blast 500 leads at once, you may generate 60 appointment requests in 90 minutes. Most agents can handle 8-12 appointments a day. Batching the send controls inbound appointment volume so your calendar fills at a pace you can actually service.
Testing and risk management. Sending to 10% of your list first tells you whether the message is converting before you commit the other 90%.
4 Real Scenarios Where Insurance Agents Need Batch Control
1. Database Reactivation Campaigns
You’ve got 800 aged leads from the past 18 months — people who filled out a form, got a few follow-ups, and went cold. You want to re-engage them with a fresh sequence.
Blasting all 800 at once creates two problems: carrier filtering due to volume spikes, and a flood of responses your team can’t handle on day one. A workflow partial send batch lets you contact 75-100 leads per day. By day two, you know your response rate and can project your week. By day five, you’ve warmed up the sender domain and avoided any spam triggers.
Onyx’s database reactivation AI (available on Prime and Elite AI tiers) is built exactly for this scenario. The AI re-engages leads with conversational follow-up, but the batch configuration determines when and how many contacts enter that conversation each day.
2. Annual Review Outreach at Policy Anniversaries
If you wrote 200 policies in Q1 last year, all 200 policy anniversaries cluster in Q1 this year. Without batching, your annual review workflow fires 200 outreach messages in a tight window.
Batching spreads those anniversary contacts across the review window — say, 20 per day over 10 days — so your conversations are manageable, your follow-up is personal, and you don’t burn through your Twilio SMS credits in one afternoon. Tracking SMS usage and billing becomes much easier when volumes are predictable.
3. New Lead Batch Imports from Vendor Lists
You purchased a list of 300 mortgage protection leads and need to import them into your CRM and launch an initial outreach sequence. If all 300 enter the speed-to-lead workflow simultaneously, you get a simultaneous blast that may violate carrier guidelines and definitely overwhelms your capacity to handle replies.
The correct approach: import in batches of 50-75, staggered by two to four hours, so the workflow’s initial SMS fires across the day rather than in one spike. Importing leads and launching contact sequences is a documented workflow in Onyx — batching at the import stage is the cleanest way to control send volume.
4. A/B Testing Message Variants Before Full Deployment
You’ve written two different opening SMS messages for your Final Expense stack. Before you commit the entire pipeline to one version, you want to test each on a subset. Batch sends make this possible: send variant A to the first 50 contacts, variant B to the next 50, and measure reply rates before deploying the winner at scale.
This is one of the most underused applications of batch control among independent agents. The data you collect from a 50-contact test is often more valuable than the additional reach you gave up.
How to Configure Message Control: Workflow Partial Send Batch Setup in Onyx
Onyx CRM is built on GoHighLevel (GHL). Batch send control is managed through a combination of workflow enrollment filters, time delays, and contact limit conditions. Here’s how to configure it.
Step 1: Define Your Total List and Batch Size
Before touching the workflow builder, know your numbers:
- Total contacts to be sent this message: e.g., 400
- Desired batch size: e.g., 50 per day
- Desired cadence: e.g., once per day at 9:00 AM
This gives you 8 days to send the full list, with 50 contacts receiving the message each morning.
Step 2: Use Smart Tags to Segment Your Batches
Tag your contact list before enrolling them. Create batch tags such as batch-01, batch-02, through batch-08. Assign 50 contacts to each tag. Automated lead tagging in your pipeline is one of the most practical ways to manage this without manual sorting — use a filter condition on import or a bulk action in the contacts view.
Onyx’s tag taxonomy supports 351 unique tags across the platform, so adding batch-specific tags won’t create clutter if you name them consistently and remove them post-send.
Step 3: Configure Workflow Enrollment Conditions
In your workflow, set the enrollment trigger to: Tag Added — [batch tag name].
This means the workflow only fires for contacts who have received that specific batch tag. You control when each batch fires by controlling when you apply the tag — either manually, on a scheduled date, or via a parent automation that adds batch tags on a defined schedule.
For fully automated batch release, create a parent workflow that:
1. Fires daily at your target send time
2. Selects up to 50 contacts matching your base criteria (aged leads, upcoming anniversaries, etc.)
3. Applies the next batch tag to those contacts
4. This tag triggers enrollment in the message workflow
Step 4: Add a Daily Contact Cap Condition
Inside the message workflow, add a condition branch after enrollment:
- Condition: Contact was enrolled today (check against a daily counter custom field)
- If under cap (e.g., < 50): Proceed to message step
- If at cap: Move contact to a “Pending Next Batch” holding stage in your pipeline
This acts as a secondary safeguard in case your tag-based approach sends more contacts than expected.
Step 5: Set Send Time Windows
Always add a Send Time Window action before your SMS or email step. For insurance outreach, 9:00 AM–5:00 PM in the contact’s local time zone is standard. This prevents messages from firing outside business hours even if the batch tag is applied at midnight.
For SMS specifically, TCPA compliance requires adherence to time-of-day restrictions. Understanding real-time SMS response handling also becomes relevant here — if you’re batching 50 sends at 9 AM, your response alert setup needs to be ready to handle the inbound replies that will come back within the hour.
Step 6: Monitor and Adjust
After your first batch fires, check:
- Delivery rates (aim for 95%+)
- Reply rates within first two hours
- Appointment bookings generated
- Any bounce or unsubscribe spikes
If reply rates are strong, you may want to increase your daily batch size. If you’re seeing soft bounces or low engagement, reduce batch size and review your message copy before proceeding.
Troubleshooting Common Batch Send Problems
Problem: Contacts are enrolling in the workflow but not receiving messages.
Check your send time window. If contacts enrolled outside allowed hours, they’ll sit in the workflow and fire at the next available window. This is correct behavior — confirm your time window settings match your expectations.
Problem: More than your intended batch size is receiving messages.
Your batch tag is being applied to more contacts than expected. Audit the automation applying the tag and verify your contact filter conditions are specific enough. Add the daily cap condition in Step 4 as a backstop.
Problem: SMS messages are getting flagged or filtered by carriers.
This usually points to A2P registration issues, not batch configuration. Review your A2P setup guide before adjusting batch settings. Batching cannot fix a sender registration problem.
Problem: Workflow is firing duplicate messages to the same contacts.
Check for duplicate enrollment. Ensure the workflow has “Allow re-enrollment” turned off unless intentional. Also verify the same batch tag isn’t being applied multiple times to the same contact by a parent automation.
Problem: Message length is causing truncation or split-sends.
SMS messages over 160 characters split into multiple segments, which can distort your send volume tracking. Fixing SMS message length issues in automation workflows covers how to handle this specifically.
Best Practices for Workflow Partial Send Batches
- Start small. Your first batch should be 10-15% of your total list. Validate before scaling.
- Batch size scales with your response capacity. If you can handle 20 conversations per day, don’t batch 100 sends per day.
- Keep batch tags clean. Remove batch tags after the send is complete. Stale tags create confusion in future automations.
- Log your batches. Use a custom field or note to record which batch a contact was in and when they were sent. This supports troubleshooting and performance analysis later.
- Pair batching with pipeline stage tracking. Contacts who are mid-batch should sit in a dedicated pipeline stage — “Batch Queue” — so you always know how many contacts are waiting and where they are in the process. Tracking policy status with smart tags is a complementary discipline that makes your pipeline data accurate throughout a batched campaign.
According to the CTIA Messaging Principles and Best Practices, message senders should avoid high-volume sends that could be interpreted as spam — batching is one of the most practical ways to comply with this guidance.
The Insurance Information Institute also notes that policyholder communication quality directly affects retention rates, reinforcing why controlled, timely outreach matters more than volume.
Frequently Asked Questions
What is a workflow partial send batch and why does it matter for insurance agents?
A workflow partial send batch is a method of releasing messages from a CRM automation to a limited number of contacts at a time, rather than all at once. For insurance agents, this matters because bulk sends to large contact lists can trigger spam filters, overwhelm appointment capacity, and reduce reply quality. Batching lets you control the pace of outreach, protect your SMS sender reputation, and manage inbound responses at a sustainable rate. Agents running reactivation campaigns or annual review outreach benefit most — those use cases typically involve large, dormant lists where a measured release approach produces better results than a single mass send.
How do I decide what batch size to use for my workflow?
Batch size should match two constraints: your daily response capacity and your deliverability goals. A good starting point is to calculate how many conversations your team can actively manage per day — typically 15-30 for a solo agent — and set your batch size to 80% of that number to leave room for organic inbound. For deliverability, most SMS carriers recommend gradual volume increases rather than sudden spikes, particularly for newer sender numbers. Start with 25-50 sends per batch, monitor delivery rates for three to five days, and scale up only after confirming consistent delivery above 95%.
Does Onyx CRM support workflow partial send batching natively?
Onyx CRM, built on GoHighLevel, supports batch send control through a combination of workflow enrollment triggers, tag-based filtering, time delay actions, and send window settings. There is no single “batch size” toggle — the capability is assembled from these components. The tag-based batch method described in this guide is the most reliable approach for most insurance use cases. Onyx Prime and Elite AI tiers support more advanced conditional logic and custom workflows, which give you additional control over batch configuration. For detailed pricing and tier differences, visit onyx-crm.com/pricing.
What’s the difference between batching and drip campaigns?
Drip campaigns control the timing between messages for each individual contact — for example, send message one on day 1, message two on day 3, message three on day 7. Batching controls how many contacts enter or receive a message step at the same time. These are complementary, not competing. You can run a drip campaign that also uses batching: 50 new contacts enter the drip sequence each day, and each contact then receives the drip cadence individually. Using both gives you control over volume (via batching) and contact-level sequence pacing (via the drip schedule).
Can I use batch sends for email and SMS at the same time in one workflow?
Yes. If your workflow contains both SMS and email steps, the batch configuration applies to the entire contact’s path through the workflow — not to a single channel. When a contact enters the batch, they move through all steps in sequence, including both SMS and email touchpoints. The key is ensuring your send time window settings are configured for both channels appropriately. Email send windows are generally more flexible than SMS, which has TCPA time-of-day requirements. Configure both channel steps with appropriate time restrictions within the same workflow to keep all messages compliant regardless of which batch fires them.
Get Batch Control Without the Manual Work
Workflow partial send batching isn’t a workaround — it’s a deliberate strategy that protects your sender reputation, keeps your calendar manageable, and lets you test before you commit at scale.
If you’re running reactivation campaigns, anniversary outreach, or fresh lead imports and you’re not controlling your batch size, you’re leaving deliverability and response quality to chance.
Onyx CRM’s automation architecture is built to support exactly this kind of precision. The 441 pre-built workflows across 7 insurance verticals are designed to be configured for your capacity — not just turned on and forgotten.
Explore what the platform can do at onyx-crm.com/pricing.
