Open Forum

Hi Evya,

Thank you for sharing your feedback and I am sorry to hear about the experiences you faced through your first event. I can assure you we want our customers, and their registrants, to have the best experience possible, and I am confident you can do so when you launch your fall conference. 

I first wanted to let you know that I passed this feedback on to your account team. Your Account Manager shared that you have a call set up next week, along with your Client Success resource, and will be able to discuss any of this in full detail.

Additionally, I reached out to the manager of our Messaging Platforms team, who oversees all Cvent email systems and delivery. His team has shared the below information, which you can also discuss with your Account Team further as needed:

Regarding deliverability of emails, there are a couple items to check:

1. Check with your IT team/provider if the domain/subdomain you are using has a DMARC policy and what the policy states.
              a) DMARC (Domain-Based Message Authentication, Reporting, and Conformance) is an email authentication and reporting policy built by your IT team/provider.
              b) The DMARC policy for your domain/subdomain (if it exists) indicates to recipient mail servers what to do with emails sent from your domain/subdomain out of our platform that are unauthenticated (such as to quarantine or even reject them, if your DMARC policy states to do so).

2. DKIM can be implemented per domain/subdomain in order to align with your DMARC policy - our customer support team can assist with these requests.
              a) DKIM is an authentication method we offer using public/private key cryptography that checks against the 'header from' domain to determine whether that is the domain responsible for the content of an email message, as well as whether or not the headers and content of an email message have been tampered with.
              b) Even if your domain/subdomain does not have a DMARC policy in place, DKIM would still be encouraged as some recipient mail servers may still check for it.

This combination of DMARC and DKIM gives the receiving mail system(s) information on what domain takes responsibility for an email and its content, as well as a way to verify whether or not the headers and content of that email have been modified – and if the domain and email content don't meet the requirements, then the DMARC policy is referenced for how to proceed.

NOTE: DKIM is not an enforcement method – rather, it's a type of authentication that allows the recipient mail system to decide whether it can treat an email coming from the responsible sending domain as valid and secure. It is also more useful as a solution if the sender has enough email volume to have grown their own email reputation.

Regarding the registrant payment concern, here is a great Knowledge Base article that walks you through troubleshooting steps.

If you have any questions or additional feedback, please let me know - I'm happy to pass anything on to your Account Team or discuss with our product teams. Steven's experiences shared below are also extremely helpful as another Cvent user! 

Best,

Danni  

Hi Evya,

Thank you for sharing your feedback and I am sorry to hear about the experiences you faced through your first event. I can assure you we want our customers, and their registrants, to have the best experience possible, and I am confident you can do so when you launch your fall conference. 

I first wanted to let you know that I passed this feedback on to your account team. Your Account Manager shared that you have a call set up next week, along with your Client Success resource, and will be able to discuss any of this in full detail.

Additionally, I reached out to the manager of our Messaging Platforms team, who oversees all Cvent email systems and delivery. His team has shared the below information, which you can also discuss with your Account Team further as needed:

Regarding deliverability of emails, there are a couple items to check:

1. Check with your IT team/provider if the domain/subdomain you are using has a DMARC policy and what the policy states.
              a) DMARC (Domain-Based Message Authentication, Reporting, and Conformance) is an email authentication and reporting policy built by your IT team/provider.
              b) The DMARC policy for your domain/subdomain (if it exists) indicates to recipient mail servers what to do with emails sent from your domain/subdomain out of our platform that are unauthenticated (such as to quarantine or even reject them, if your DMARC policy states to do so).

2. DKIM can be implemented per domain/subdomain in order to align with your DMARC policy - our customer support team can assist with these requests.
              a) DKIM is an authentication method we offer using public/private key cryptography that checks against the 'header from' domain to determine whether that is the domain responsible for the content of an email message, as well as whether or not the headers and content of an email message have been tampered with.
              b) Even if your domain/subdomain does not have a DMARC policy in place, DKIM would still be encouraged as some recipient mail servers may still check for it.

This combination of DMARC and DKIM gives the receiving mail system(s) information on what domain takes responsibility for an email and its content, as well as a way to verify whether or not the headers and content of that email have been modified – and if the domain and email content don't meet the requirements, then the DMARC policy is referenced for how to proceed.

NOTE: DKIM is not an enforcement method – rather, it's a type of authentication that allows the recipient mail system to decide whether it can treat an email coming from the responsible sending domain as valid and secure. It is also more useful as a solution if the sender has enough email volume to have grown their own email reputation.

Regarding the registrant payment concern, here is a great Knowledge Base article that walks you through troubleshooting steps.

If you have any questions or additional feedback, please let me know - I'm happy to pass anything on to your Account Team or discuss with our product teams. Steven's experiences shared below are also extremely helpful as another Cvent user! 

Best,

Danni  

Hi Evya,

Thank you for sharing your feedback and I am sorry to hear about the experiences you faced through your first event. I can assure you we want our customers, and their registrants, to have the best experience possible, and I am confident you can do so when you launch your fall conference. 

I first wanted to let you know that I passed this feedback on to your account team. Your Account Manager shared that you have a call set up next week, along with your Client Success resource, and will be able to discuss any of this in full detail.

Additionally, I reached out to the manager of our Messaging Platforms team, who oversees all Cvent email systems and delivery. His team has shared the below information, which you can also discuss with your Account Team further as needed:

Regarding deliverability of emails, there are a couple items to check:

1. Check with your IT team/provider if the domain/subdomain you are using has a DMARC policy and what the policy states.
              a) DMARC (Domain-Based Message Authentication, Reporting, and Conformance) is an email authentication and reporting policy built by your IT team/provider.
              b) The DMARC policy for your domain/subdomain (if it exists) indicates to recipient mail servers what to do with emails sent from your domain/subdomain out of our platform that are unauthenticated (such as to quarantine or even reject them, if your DMARC policy states to do so).

2. DKIM can be implemented per domain/subdomain in order to align with your DMARC policy - our customer support team can assist with these requests.
              a) DKIM is an authentication method we offer using public/private key cryptography that checks against the 'header from' domain to determine whether that is the domain responsible for the content of an email message, as well as whether or not the headers and content of an email message have been tampered with.
              b) Even if your domain/subdomain does not have a DMARC policy in place, DKIM would still be encouraged as some recipient mail servers may still check for it.

This combination of DMARC and DKIM gives the receiving mail system(s) information on what domain takes responsibility for an email and its content, as well as a way to verify whether or not the headers and content of that email have been modified – and if the domain and email content don't meet the requirements, then the DMARC policy is referenced for how to proceed.

NOTE: DKIM is not an enforcement method – rather, it's a type of authentication that allows the recipient mail system to decide whether it can treat an email coming from the responsible sending domain as valid and secure. It is also more useful as a solution if the sender has enough email volume to have grown their own email reputation.

Regarding the registrant payment concern, here is a great Knowledge Base article that walks you through troubleshooting steps.

If you have any questions or additional feedback, please let me know - I'm happy to pass anything on to your Account Team or discuss with our product teams. Steven's experiences shared below are also extremely helpful as another Cvent user! 

Best,

Danni  

Hi Evya,

Thank you for sharing your feedback and I am sorry to hear about the experiences you faced through your first event. I can assure you we want our customers, and their registrants, to have the best experience possible, and I am confident you can do so when you launch your fall conference. 

I first wanted to let you know that I passed this feedback on to your account team. Your Account Manager shared that you have a call set up next week, along with your Client Success resource, and will be able to discuss any of this in full detail.

Additionally, I reached out to the manager of our Messaging Platforms team, who oversees all Cvent email systems and delivery. His team has shared the below information, which you can also discuss with your Account Team further as needed:

Regarding deliverability of emails, there are a couple items to check:

1. Check with your IT team/provider if the domain/subdomain you are using has a DMARC policy and what the policy states.
              a) DMARC (Domain-Based Message Authentication, Reporting, and Conformance) is an email authentication and reporting policy built by your IT team/provider.
              b) The DMARC policy for your domain/subdomain (if it exists) indicates to recipient mail servers what to do with emails sent from your domain/subdomain out of our platform that are unauthenticated (such as to quarantine or even reject them, if your DMARC policy states to do so).

2. DKIM can be implemented per domain/subdomain in order to align with your DMARC policy - our customer support team can assist with these requests.
              a) DKIM is an authentication method we offer using public/private key cryptography that checks against the 'header from' domain to determine whether that is the domain responsible for the content of an email message, as well as whether or not the headers and content of an email message have been tampered with.
              b) Even if your domain/subdomain does not have a DMARC policy in place, DKIM would still be encouraged as some recipient mail servers may still check for it.

This combination of DMARC and DKIM gives the receiving mail system(s) information on what domain takes responsibility for an email and its content, as well as a way to verify whether or not the headers and content of that email have been modified – and if the domain and email content don't meet the requirements, then the DMARC policy is referenced for how to proceed.

NOTE: DKIM is not an enforcement method – rather, it's a type of authentication that allows the recipient mail system to decide whether it can treat an email coming from the responsible sending domain as valid and secure. It is also more useful as a solution if the sender has enough email volume to have grown their own email reputation.

Regarding the registrant payment concern, here is a great Knowledge Base article that walks you through troubleshooting steps.

If you have any questions or additional feedback, please let me know - I'm happy to pass anything on to your Account Team or discuss with our product teams. Steven's experiences shared below are also extremely helpful as another Cvent user! 

Best,

Danni  

Hi Evya,

Thank you for sharing your feedback and I am sorry to hear about the experiences you faced through your first event. I can assure you we want our customers, and their registrants, to have the best experience possible, and I am confident you can do so when you launch your fall conference. 

I first wanted to let you know that I passed this feedback on to your account team. Your Account Manager shared that you have a call set up next week, along with your Client Success resource, and will be able to discuss any of this in full detail.

Additionally, I reached out to the manager of our Messaging Platforms team, who oversees all Cvent email systems and delivery. His team has shared the below information, which you can also discuss with your Account Team further as needed:

Regarding deliverability of emails, there are a couple items to check:

1. Check with your IT team/provider if the domain/subdomain you are using has a DMARC policy and what the policy states.
              a) DMARC (Domain-Based Message Authentication, Reporting, and Conformance) is an email authentication and reporting policy built by your IT team/provider.
              b) The DMARC policy for your domain/subdomain (if it exists) indicates to recipient mail servers what to do with emails sent from your domain/subdomain out of our platform that are unauthenticated (such as to quarantine or even reject them, if your DMARC policy states to do so).

2. DKIM can be implemented per domain/subdomain in order to align with your DMARC policy - our customer support team can assist with these requests.
              a) DKIM is an authentication method we offer using public/private key cryptography that checks against the 'header from' domain to determine whether that is the domain responsible for the content of an email message, as well as whether or not the headers and content of an email message have been tampered with.
              b) Even if your domain/subdomain does not have a DMARC policy in place, DKIM would still be encouraged as some recipient mail servers may still check for it.

This combination of DMARC and DKIM gives the receiving mail system(s) information on what domain takes responsibility for an email and its content, as well as a way to verify whether or not the headers and content of that email have been modified – and if the domain and email content don't meet the requirements, then the DMARC policy is referenced for how to proceed.

NOTE: DKIM is not an enforcement method – rather, it's a type of authentication that allows the recipient mail system to decide whether it can treat an email coming from the responsible sending domain as valid and secure. It is also more useful as a solution if the sender has enough email volume to have grown their own email reputation.

Regarding the registrant payment concern, here is a great Knowledge Base article that walks you through troubleshooting steps.

If you have any questions or additional feedback, please let me know - I'm happy to pass anything on to your Account Team or discuss with our product teams. Steven's experiences shared below are also extremely helpful as another Cvent user! 

Best,

Danni