If you’ve configured Send As aliases in Gmail — for example, sending mail as [email protected] from a personal Gmail account, or sending from a team alias like [email protected] — MyVideo.Email respects those aliases and lets you choose which one to send from on a per-email basis.
This article explains how Send As works in MyVideo.Email and how to use it.
What “Send As” means #
In Gmail, you can configure additional Send mail as addresses under Gmail settings. These are verified addresses you’re allowed to send from — typically:
- Your work email (sending through a personal Gmail account)
- Group/team aliases like
sales@,support@,hello@ - Branded domains routed through Gmail
When you connect your Google account to MyVideo.Email, we automatically detect your verified Send As addresses and offer them as options when you compose.
Setting up Send As in Gmail first #
If you haven’t already set up Send As in Gmail, do that first:
- Open Gmail.
- Click the gear icon → See all settings.
- Go to the Accounts and Import tab.
- Under Send mail as, click Add another email address.
- Follow the verification steps (Google will email a verification link to the address).
Once Gmail confirms the address as a verified Send As, MyVideo.Email picks it up automatically the next time you compose.
Choosing a Send As address in MyVideo.Email #
Once you have one or more verified aliases:
- Start composing a video email as normal (web or extension).
- On the send screen, look for the From dropdown above your subject line.
- Click it — you’ll see your primary address plus all verified Send As aliases.
- Pick the alias you want to send from.
- Send.
The recipient sees the email arriving from the selected address. Replies route to whichever Reply-To MyVideo.Email is configured for, and your Reply Inbox still works the same way.
Send As and signatures #
If Send As is paired with Gmail signature insertion, MyVideo.Email automatically switches to the signature associated with that alias when you change the From dropdown. So if your work alias has a fancy HTML signature and your personal address has a simple plaintext one, the right signature follows the From address.
See Gmail Signature Insertion for how signatures work.
Send As and CRM integrations #
Send As applies to Gmail-based sends only. If you’re sending through Keap, HighLevel, or HubSpot, those integrations use their own sender configuration (typically set at the CRM level by an admin). Send As is unavailable in those flows.
See Sender Domains for Org Integrations for how to configure org-level sender addresses on Keap and HighLevel.
Mobile #
Send As works in the MyVideo.Email mobile app the same way it does on the web. When you compose with Gmail, the From picker shows your verified Send As aliases — choose one before you send.
The first time you use Send As on mobile, you may need to reconnect Google from the app’s Settings → Integrations so Google can prompt you for the Send-As permission. After that, your aliases appear in the From picker on every compose.
Troubleshooting #
My alias doesn’t show up in the From dropdown.
First verify the alias is fully set up and confirmed in Gmail (Settings → Accounts and Import). If it shows as verified there but not in MyVideo.Email, disconnect and reconnect your Google account in Settings → Integrations — the OAuth scope refresh will pick up the new alias.
The recipient sees the email from my primary address even though I picked an alias.
This usually means Gmail rejected the Send As alias at send time, often because:
- The alias’s verification has lapsed (Gmail re-verifies periodically)
- You don’t have permission to send as that alias (group/Google Workspace settings)
- The alias was deleted in Gmail
Check the alias status in Gmail. If it’s still verified there, contact support.
Send As works in the web app but not the Chrome extension.
Make sure the Chrome extension is updated to the latest version. Some older extension builds default to your primary address regardless of dropdown selection.
Replies aren’t routing to the alias address.
By default, replies route to the Reply-To header configured per-organization. If you need replies to go to the alias address specifically, contact your team owner — this is a per-org setting, not per-alias.
