Skip to main content

Vitally Email Service

Send emails at scale using your own domain

Written by Laura Bedoya
Updated this week

Vitally Email Service Overview

The Vitally Email Service enables customers to send emails at scale from Vitally using their organization's verified domain, increasing sending capacity by removing standard email send limits (annual limit of 10 million emails per year) to ensure reliable, consistent delivery of emails, Docs, surveys, and more. Try it for a 30-day free trial with full access!

The Vitally Email Service add-on for sending transactional emails can be managed by admins in Account Settings.

Key functionality:

  • Allows sending transactional emails through Vitally from a verified domain

  • Requires email domain verification and matching Vitally user email addresses

  • Email analytics

💡 Tip: Keep your contact lists up to date by removing churned users from mailing lists and removing invalid email addresses before syncing them into Vitally. There are paid list validation services available if manual cleanup isn't feasible. Our recommendation, talk to your marketing team on best email practices!



How to Set Up Vitally Email Service

  1. Go to Settings -> Email

  2. Select Add a Domain (add as many as you need)

  3. Enter your domain

    1. You should get a successful banner

    2. The domain will initially appear as Unverified

  4. To verify the Domain, select the settings wheel to find the DNS records that will be auto-generated

  5. Share these DNS records with your IT team for implementation

    1. The domain must be verified within 72 hours or the process times out

    2. If that happens, click “Re-Start” to retry verification

  6. Once successful, the domain status updates to Verified in Vitally


  7. Now you can start sending emails! Every Vitally User, that is not an observer, will automatically get a Vitally email to be able to send transactional emails

    1. NOTE: At least one Vitally user must have an email that matches the verified domain (e.g., j.smith@vitally.io for vitally.io).

Adding Alias Addresses for the Vitally Email Service

  1. Go to Settings -> Email

  2. Select the domain

  3. Select the plus (+) sign or the settings wheel

  4. Add your aliases here

  5. Additionally, you can send test emails in this window by select Send Test Email

    1. Input a Send From, Send To, Subject, and Message then select Send


How to Use the Vitally Email Service

  1. Start a conversation like you normally would (learn more here) via a playbook or manually

  2. In the From section, search your name to find your email under the "Vitally Email" section and select your email

    1. Select a fallback sender. This is ensure that emails are sent if for whatever reason the sender email is not working. This also automatically chooses the sender channel (sendgrid, gmail, vitally email service, etc)

      1. For example, if you choose to send from a key role (e.g.g, CSM) and then choose a fallback sender from the Vitally Email section, the email will be sent from the CSM as a transactional email. *Important note to ensure that you're sending correctly when choosing a key role

  3. Select a "reply to" email address that is a real email inbox if you want to receive emails if you're sending from an alias. If you don't do this step, you will not receive responses

  4. Continue sending your emails as you would!


How to make use of the Analytics

To make use of the different analytics we have available, you will need to either create or update an existing Conversations view. The analytics are available as properties that can be added as Columns.

They can be found under Vitally Data:

First Message

These are also available to use for any conversations created within Vitally. See here.

Bounced (boolean)

This indicates whether the first message bounced at any addresses it was sent to.

Opened (boolean)

This indicates whether the first message was opened.

Opened (count)

This indicates the number of times the first message was opened.

Replied (boolean)

This indicates whether the first message was replied to.

Unsubscribed (boolean)

This indicates whether any recipients of the first message unsubscribed.

Unsubscribed Emails

This contains a list of the addresses that were unsubscribed

Vitally Email

These are only available for conversations created using the Vitally Email Service

Bounced Emails

This contains a list of addresses that bounced.

Clicked (boolean)

This indicates whether any links in the first message of the conversation were clicked.

Clicked (count)

This indicates how many times any link in the first message was clicked.

Clicked links (urls)

This contains a list of strings representing the URLS of links that were clicked in the first message.

Spam Reported Emails

This contains a list of email addresses that reported the first message as spam.

Spam Reported (boolean)

This indicates whether there were any spam reports for the first message.


Bounce Rate Management & Sending Suspension

High bounce rates directly impact your email deliverability — meaning fewer of your messages reach your customers' inboxes. To protect your sending reputation and ensure your conversations continue to land where they matter, we pause email sending until list hygiene is addressed.

To protect email deliverability for all Vitally customers, Vitally automatically monitors hard bounce rates and will suspend Service Email messages from sending if:

  • your rate exceeds 8%

  • over the last 7 days

  • and more than 250 emails sent in that period

When suspended, you'll see a banner on your Vitally Email settings page and will be unable to select SES senders. Before you get to this point, you'll receive a warning email if your bounce rate reaches 3% so you have a chance to address the issue proactively.

How to Avoid Email Service Suspension

When an email hard bounces, that user is automatically flagged with a Permanently Bounced trait in Vitally, and no further emails will be sent to that address.

You'll see a banner on the User 360 for any affected user. To re-enable sending, update the user's email address — this will reset the Permanently Bounced field and allow the user to be targeted again. The field itself is not directly editable.

The Permanently Bounced field is filterable and sortable across User lists and Widgets. Note that this cannot be updated in bulk — each user's email address must be updated individually.

Only hard bounces count toward the suspension threshold — these are permanent delivery failures where the email address doesn't exist or is otherwise undeliverable. Soft bounces (e.g., a full inbox) do not count. The suspension will clear once your rolling 7-day hard bounce rate returns to a healthy level.



Vitally Email Service FAQ

Why can’t I send emails after adding a domain?

Your domain may not be verified yet. Check the DNS record status and ensure it's verified within 72 hours.

My domain is verified but no sending address shows up—why?

There may be no Vitally user with an email that matches the domain. At least one is required.

Is there a sending limit?
Yes. The Vitally Email Service supports up to 10 million emails per year.

Is this service free?
No, the Vitally Email Service is a paid add-on. Reach out to am@vitally.io to ask about pricing, or manage the add-on within your Account Settings.

I'm not seeing any responses to emails, why?

If you're sending from an alias and did not select a reply-to email that is a real inbox, you will not receive responses.

Why are my emails not sending through Vitally Email Service? Your account may have been suspended due to a high hard bounce rate. If your bounce rate exceeds 5% over the last 7 days with more than 200 emails sent, SES sending is automatically paused. Check your Email settings page for a suspension banner.

How do I fix my emails not sending due to high bounce rate? Clean up your email list by removing invalid addresses and churned users, then contact Vitally Support to request an override. The suspension will also lift automatically after 7 days once your bounce rate normalizes.

Did this answer your question?