Skip to main content
Send settings control the pace and shape of a sequence’s sending. They live on the Settings tab of each sequence, and you configure them after connecting an inbox.

Send settings

How daily volume actually works

Starbridge allows you to place limits on your daily send volume to protect your sender reputation and distribute email sending across multiple sequences. Each inbox has its own daily limit, set in its inbox settings. Every inbox starts at 20 emails per day. Anyone can raise their own inbox’s Maximum daily send, and admins can raise it for any org inbox. You can set a limit as high as 300, but we recommend keeping it at 50 or below. 20 to 50 emails per day is the safe range for most inboxes, and anything above 50 is at your own risk. Only emails sent from Starbridge count toward the daily limit. That means sequence emails, one-off emails, and emails sent through Ask Starbridge. Emails you send directly from Gmail or Outlook, or from other tools connected to the same inbox, don’t count toward it.
Sending more than 50 emails per day from one inbox is risky. It’s highly likely to get your inbox flagged as spam.
Each sequence has a customizable limit on maximum emails per day. Use this to distribute load across multiple sequences.
Use a lower number when you want to throttle deliberately. Two good reasons: capping outreach at the volume of replies your team can actually handle, and splitting an inbox’s capacity across several concurrent sequences rather than letting one consume it all.

Choose an email format

HTML-heavy email is a strong signal to spam filters that a message is bulk marketing rather than a person writing to another person, so plain text lands in more inboxes. Plain text strips HTML, including images, tracked links, and formatting. Email format lets you control that tradeoff for each sequence. Automatic is the default. Starbridge sends plain text unless the sequence contains rich text, such as a link, bold text, or a list, and then sends rich text, so a sequence never goes out with its links and formatting flattened. Plain text always sends plain text. Choose it when deliverability matters more than formatting, and check first that none of your messages depend on links or formatting, because Starbridge flattens them. Rich text always sends rich text. Choose it when your messages need links, images, or formatting to arrive as written.
Not sure which to pick? Leave it on Automatic. You get the deliverability of plain text whenever your copy doesn’t need formatting, and you can’t accidentally send a message with links as plain text.
Unsubscribe links mark a message as bulk mail in much the same way. Rather than including one, add a plain opt-out line to your copy: something like “if now isn’t the right time, just let me know.” It reads as human, and it gives the recipient the same out.
Starbridge honors unsubscribes regardless of this setting. Turning the link off doesn’t remove anyone’s ability to opt out, and it doesn’t affect how Starbridge handles opt-outs it detects.

Sending inboxes for Team and one-off sequences

Team and one-off sequences send from the inbox of the rep who enrolled each contact, rather than a pool you assign. For Team sequences, the sequence controls Max emails per day, step prioritization, unsubscribe link, and email format. The rep’s own inbox controls the schedule: their days of week, times of day, and timezone. For one-off sequences, the rep’s personal send settings prevail.

Keeping the wrong people out of your outbound

Starbridge suppresses sending in four ways. Blocklists, unsubscribes, and CRM opt-outs are absolute. Exclusion lists are your org’s default position, which a builder can adjust for a specific sequence.

Blocklists

Admins can add individual addresses or domains in Settings → Sequences → Blocklist, or bulk upload a CSV. Adding someone removes them from any sequence they’re active in and prevents future enrollment.
Screenshot 2026 10 15 At 2 14 11 PM 1

Exclusion lists

An exclusion list is a list of accounts whose contacts shouldn’t receive outbound. Admins set org-wide defaults, and those defaults apply to every new sequence automatically. Exclusion lists are buyer lists, so anything you can build as a buyer list can serve as an exclusion. The most common use is current customers, but the same mechanic covers partners, accounts owned by another team, and accounts with an open opportunity you don’t want cold-touched.

Set your org’s default exclusion lists

Admins select exclusion lists in Settings → Sequences → Exclusion lists, choosing from your existing buyer lists. Anything you select applies as a default exclusion on every sequence going forward. The most common setup takes four steps:
1

Define the accounts in your CRM

In Salesforce or HubSpot, build a view of the accounts you want excluded. For current customers, that’s however your org marks a customer: account type, lifecycle stage, or a custom field.
2

Sync it to Starbridge as a buyer list

Create a CRM-synced buyer list from that view. It stays current as your CRM changes, so accounts that become customers are excluded without anyone maintaining a list by hand. See CRM-synced buyer lists.
3

Add it in Settings → Sequences → Exclusion lists

Under Buyer lists, use Choose buyer lists to exclude to select it. Starbridge asks whether to apply it to existing sequences as well as new ones, or only to new sequences going forward.Applying to existing sequences removes contacts at those accounts from sequences they’re already in. See What happens when exclusions change.
4

Check it on your next sequence

Build or open a sequence and confirm the list appears pre-selected in its exclusions.

Adjust exclusions on a single sequence

When a builder creates a sequence, your org’s defaults are pre-selected. Builders can remove any of them for that sequence, or add others from your buyer lists. This gives you the flexibility to run a play that your org defaults would otherwise block, like promoting a new product line to existing customers. Removing an exclusion on one sequence has no effect on any other sequence or on your org defaults.

How exclusions behave when reps enroll contacts

Exclusions work differently depending on who’s acting. A builder constructing a Bridge-based sequence can remove an exclusion list from that sequence. Contacts at excluded accounts are then eligible. A rep enrolling a contact into a Team or one-off sequence can’t override an exclusion. If the contact’s account is on an exclusion list applied to that sequence, the enroll action is disabled.

What happens when exclusions change

The governing principle is that adding an exclusion reaches backward, and removing one only reaches forward. Adding an exclusion sweeps contacts who are already Ready or Enrolled at those accounts into Removed status, stopping their remaining steps, and keeps new contacts out going forward. Removing an exclusion never re-enrolls or restores anyone. It only stops gating new contacts. This is deliberate: removing an exclusion never silently restarts outreach to someone your team decided to stop contacting.
Removing a default exclusion in Settings doesn’t remove it from sequences that already have it applied. Those sequences keep the exclusion until a builder edits them.

Using a HubSpot list as an exclusion list

In HubSpot, an exclusion list can come from a company list, so a “current customers” company list works. Deal lists and pipeline stages aren’t directly supported.

Deleting a buyer list in use

You can’t delete a buyer list that’s currently serving as an exclusion list. Remove it from your org defaults and from any sequence using it first. This prevents accidentally removing exclusion coverage by deleting the underlying list.

CRM opt-outs

Starbridge honors opt-outs recorded in Salesforce and HubSpot, so contacts who have opted out stay out of your sequences without anyone checking records by hand.

Prerequisites

  1. Enable the opt-out fields in Objects & fields for your CRM integration:
    1. Email Opt Out (HasOptedOutOfEmail) and Do Not Call (DoNotCall) for Salesforce
    2. Unsubscribed from all email (hs_email_optout) for HubSpot
  2. Set up Contact sync so Starbridge can match its contacts to your CRM contacts and know which of them have opted out.
You don’t need to sync any Starbridge contacts to your CRM for this to work. Contact sync still has to be configured so Starbridge can confirm which CRM contact matches each Starbridge contact and look up that person’s opt-out status. Configuring it doesn’t write anything to your CRM. Contacts only sync if someone from your team explicitly chooses to sync them. Starbridge reads these fields. A contact who unsubscribes from a Starbridge email isn’t written back to HubSpot’s email opt-out field. See Unsubscribes. Starbridge reads only the standard opt-out fields on the Salesforce and HubSpot Contact objects. Custom opt-out fields aren’t read, so use the custom field approach below for those.

What happens when a contact opts out

A contact marked as opted out of email isn’t enrolled in a sequence, and the Send sequence button on their contact card is disabled. If a contact opts out while they’re already in a sequence, Starbridge removes them before their next step sends, whatever channel that step uses, and marks them Removed: opted out of email. Reps can’t override a removal, and a contact who opts back in later isn’t re-enrolled automatically.

See it in the Blocklist tab

Screenshot 2026 10 15 At 2 14 11 PM 1
The Blocklist tab in Settings → Sequences reflects opt-outs from your CRM, labeled Do not email and Do not call. Check it to confirm Starbridge is picking up your opt-outs.

Filtering by a custom do-not-contact field

If you track do-not-contact status in a custom field on the Contact record in Salesforce or HubSpot, you can use this field to exclude DNC contacts from your Bridge-based sequences.
  1. Add a CRM lookup column to your source Bridge for the Contact object.
  2. Make sure the do-not-contact custom field exists as its own column in the bridge. To pull the field out as its own column, in the source Bridge click Add enrichment → Reference existing data → Reference a column.
  3. In your sequence, use Filter by signal when building the sequence to exclude anyone where it’s set.
This works on existing sequences too: add or edit the filters on any sequence, either in the Settings tab or the left side panel for Draft sequences. If editing a Generated or Paused sequence, when you save your changes, apply them to existing recipients to make sure any current DNC contacts are immediately removed from your outbound.

What else Starbridge handles automatically

Unsubscribes

A contact who unsubscribes is removed from sequences they’re in and won’t be enrolled again. Unsubscribes go into Starbridge’s own org-wide do-not-contact list, which blocks that person from being added to any sequence again. Unsubscribes aren’t written back to your CRM. For example, Starbridge doesn’t update HubSpot’s email opt-out field. It only reads that field from HubSpot. See CRM opt-outs.

Replies

A contact who replies to an email Starbridge sent stops receiving the rest of the sequence, and moves to Completed. Only replies to Starbridge emails stop a sequence. A reply to an email you sent directly from Gmail or Outlook, or from another tool such as Outreach or Salesloft, doesn’t stop it.

Bounces

Starbridge marks a contact as bounced when their email provider reports a bounce. That contact stops receiving the rest of the sequence and moves to Completed, and the bounce shows on their recipient status in the sequence. Bounces are viewed in each sequence.

Inbox disconnection

If every inbox assigned to a sequence disconnects, the sequence moves to Paused rather than failing silently.

Protecting your sending domain

Starbridge protects your sending reputation in three ways. Volume limits. Each inbox starts at 20 emails per day, keeping you below the thresholds that get an address flagged. You can raise it, but sending more than 50 per day from one inbox is highly likely to get it flagged as spam. Address verification and bounce checking. Sequence emails are verified and bounce-checked before and during sending, so you’re not burning reputation on invalid or out-of-date email addresses. Personalized copy. Every message body and subject line is generated for the individual recipient, which is far less likely to be flagged by spam filters than generic cold outbound. Your GTME can recommend third-party tools for provisioning and warming secondary inboxes, if you want to scale sending outside of your primary domain, the one your company runs its business email on.

Where to go next

Connect your inbox

Connect Gmail or Outlook and set your personal send schedule.

Managing sequences

Pause, resume, and monitor sequences once they’re live.