Sender Name, Sender Address & IP Pools

Learn on how to configure Sender Name, Sender Address & IP Pools if you are using Sendgrid

From FT CRM, you can configure different Sender Names, Addresses, and load Categories for IP Pools from Sendgrid.
These are dynamic and can be changed for each email send out.

Sender Name

To be able to change the sender names of your campaigns or communication, you can add a field named 'SenderName' in the email action. You can make the selection into a dropdown by selecting dropdown as the field type. The value should be the correct Sender Name and Text is what will be displayed in the dropdown.
Example:
  1. The default Sender Name is BrandName
  2. You can set up another sender name called “BrandName Exclusive” or “BrandName Promotions”

Sender Address

To be able to change the sender addresses of your campaigns or communication, you can add a field named SenderEmail in the email action.
Example:
  1. The default Sender Address is: support@brand.com
  2. You can set up another sender address which could be: promotions@brand.com for some activities and info@brand.com for another type of communication

IP Pools

In case you wish to switch between different IP Pool Categories these following steps need to be done:
  1. Configure IP Pools inside the Sendgrid account you wish this to be used for (https://sendgrid.com/docs/ui/account-and-settings/ip-pools/)
  2. Set up a field named IpPool in the email action
  3. Set up the field type to be Dynamic Dropdown
  4. Set the API Endpoint URL to http://crm-api/sendgrid/pools
In case there are categories configured in Sendgrid, these should now be visible in a dropdown in the email action.
Nothing will be displayed in case there are no categories set up.
Example:
  1. You currently run with only one pool of Sender IP’s
  2. You can set up different IP Pool Categories to group up the likelihood of your communication to end up in spam/inbox etc.
  3. Marketing/Offers can be sent via one IP Pool
  4. Transactional Emails (e.g. receipts) can be sent via one IP Pool as these can have a “bad” IP
  5. Very important communication could use an IP that is rarely used and you need to make sure these end up in the inbox and not spam