Skip to main content
Connect your inbox once and every sequence you own sends from it, under your name. Replies come back to the same inbox and land in Salesfinity’s Inbox. A sequence with an email step needs at least one mailbox that can send, both to be turned on and to keep sending. This is the first thing to set up. The Sequencer is in early access, on Enterprise, Enterprise+ and Admin seats for teams in the early access program. Time: about 5 minutes. Where: Sequencer › Settings › Mailboxes.

​
Connect your mailbox

Click Add mailboxes and pick how you want to connect.
1

Click Connect Google

Sign in with the mailbox that should send. Salesfinity asks Google for one permission: sending and reading mail for that mailbox. Nothing else.
2

If Google says access denied, ask your Google admin

A Google Workspace admin may need to trust the app first. In the Google Admin console, they choose Configure new app, search for Salesfinity Sequencer by the Client ID the connect dialog shows, and set it to Trusted. The connect dialog walks them through it. It is a one-time change for your whole Workspace.
3

Connect again

Once the app is trusted, click Connect Google again and sign in.
If the connect is refused because Google did not hand back a long-lived token, remove Salesfinity from your account’s third-party access at myaccount.google.com/permissions, then connect again.
Whoever connects a mailbox decides where it goes. A mailbox a rep connects belongs to that rep, and only their sequences send from it. A mailbox the team owner or an admin connects joins the team’s shared mailboxes. Admins can turn off Let reps connect their own mailbox in Sequencer settings.

​
Send a test

Open the mailbox and click Send a test. It sends a real message to an address you choose, through the connected account. Check the from name, and that the message arrived. You’re done when: the test email lands in the inbox you sent it to, and the mailbox’s Domain authentication shows no failing records (see Fix deliverability).

​
Pool and assignment

Every connected mailbox is in one of three places:
  • Assigned to a rep: it sends only for sequences that rep owns. Assigning a mailbox takes it out of the shared mailboxes.
  • Shared with the team: it sends for any sequence whose owner has no mailbox of their own.
  • Not in use: connected, but neither assigned nor shared (Take out of use). Nothing sends from it unless a sequence picks it by name.
A sequence picks its mailboxes in this order:
1

The mailboxes picked in the sequence's own settings

If the sequence names mailboxes, it sends only from those.
2

The mailboxes assigned to the sequence's owner

Otherwise, the mailboxes assigned to the person who created the sequence.
3

The team's shared mailboxes

Otherwise, the team’s shared mailboxes.
The mailboxes belong to the sequence, not to each person in it. Every email in a sequence goes out from that sequence’s mailboxes, whichever rep owns the enrollment. If no mailbox can send, Enable is refused and the message says which of the three cases you are in. Select mailboxes in the list to Assign to…, Share with the team, Take out of use or Delete them. Before you save an assignment, the dialog shows which live sequences it changes.

​
Set limits and warmup

Open a mailbox to change its settings. The team owner and admins can change any mailbox. A rep can change the mailboxes assigned to them. The mailbox’s Warmup section shows warmup progress, how much warmup mail reached the inbox, and how much landed in spam.

​
Fix deliverability

The Deliverability column grades each mailbox’s domain on four DNS records: SPF, DKIM, DMARC and MX. These records prove to other mail servers that you are allowed to send from your domain. Open the mailbox and look at Domain authentication. It shows each record, the value it found, and the fix. Send the fix to whoever manages your domain’s DNS.
Publish one. Without it, receiving servers cannot confirm your domain allowed the send. This is the most common reason cold email lands in spam.
The standard treats two SPF records as an error, so checks fail. Merge them into one record.
These endings let anyone send as your domain. End the record with ~all or -all.
Publish a _dmarc record. Start with v=DMARC1; p=none; rua=mailto: followed by an address of yours.
Fine while you watch the reports. Move to quarantine once they are clean.
Salesfinity checks the common selectors. If your provider signs with a custom selector, this is fine. Otherwise, publish a DKIM key with your email provider.
Your domain cannot receive email, so replies have nowhere to go.

​
Take a mailbox out of use or delete it

  • Take out of use removes a mailbox from the shared mailboxes. It stays connected, and you can share or assign it again at any time.
  • Delete removes the mailbox for good. No sequence can send from it, it leaves the shared mailboxes and whoever it was assigned to, and its warmup stops. You cannot undo it.
If a sequence is left with no mailbox that can send, its next email step fails the enrollment, with the reason on its timeline. Connect or assign a mailbox, then click Retry on the enrollment.

​
Next steps

Build a sequence

Add your emails, calls and to-dos, then turn it on.

Handle replies

See how replies are sorted and what each one does.

Fix sending problems

Emails not going out? Start here.