Using CC and BCC in Uppush Automated Emails
We’ve added support for CC (Carbon Copy) and BCC (Blind Carbon Copy) to Uppush automated emails. This helps you automatically send copies of outgoing emails—such as Abandoned Cart emails—to other recipients, like your internal team.
What are CC and BCC?
CC (Carbon Copy): Adds recipients to the email for informational purposes. Everyone who receives the email can see the addresses listed in the CC field. Example: If you CC your support team, your customer will see that your support team also got a copy.
BCC (Blind Carbon Copy): Works similarly to CC, but the addresses in the BCC field are hidden from other recipients. Example: If you BCC your support team, your customer will not see that they also got a copy.
When to use which?
Use CC when it’s okay for all recipients to see each other’s addresses.
Use BCC when you want to keep other recipients private.
How to add CC/BCC in Uppush
You can add CC and BCC addresses to any automated email (e.g., Abandoned Cart emails).
Go to the Automation you want to edit
In your Uppush dashboard, open the automation (like Abandoned Cart).
Click Customize on the specific email:
Find the CC/BCC fields
Inside the email customization screen, look for the CC and BCC fields.
Add one or multiple email addresses as needed (you can select up to 3).
Verify your CC/BCC addresses first
For security and deliverability, any CC or BCC address must be verified before you can use it.
Make sure you’ve verified the addresses under the testing/verification process in Uppush (you can also click Add email which takes you to
Settings
>Verify email
)
Save your changes
Once saved, every time that automation sends an email, your CC/BCC addresses will automatically get a copy.
Tips and Notes
Privacy tip: Use BCC if you don’t want the main recipient to see internal team addresses.
Deliverability: Only verified addresses can be selected for CC/BCC.
Order of fields: CC appears before BCC in the UI (standard email convention). If you see them swapped, don’t worry—functionality remains the same.
Last updated
Was this helpful?