Hello again,

Please go to the notifications section inspect the page then try and send test notifications and then if there are any issues you will see the error in the network section. If there is any please send us a screenshot so that we can take a look.

The error should show unless you are using PHP mail. We can help only if you are using SMTP if you are using WP mail which is this party plugin then you need to reach out to their support team and if you are using PHP mail you need to change this

We strongly recommend changing the mail service setting to SMTP or Mailgun because the email that is sent with PHP Mail generally gets flagged as spam by mail servers and also can take some time to send. See below how to configure SMTP and Mailgun mail services.

So please set the SMTP on your site

• SMTP (Simple Mail Transfer Protocol) – In this article, we show how to configure the SMTP mail service for Gmail, but you can set it up for any other outgoing service that supports SMTP for a mail client. When you select this option, four inputs will appear – you need to populate them to configure SMTP properly. A Google SMTP example:
  • SMTP Host – smtp.gmail.com
  • SMTP Port – 587
  • SMTP Secure – TLS
  • SMTP Username – Your Gmail address
  • SMTP Password – Your App password (details about setting up an app password can be found in the notice section below)

  The most commonly used SMTP Ports are 465 and 587. Port 465 uses “SSL” as SMTP Secure, while port 587 uses “TLS” as SMTP Secure. Make sure to check what the correct SMTP settings are for your mailing provider.

Google SMTP (Gmail accounts):

From 30 May 2022, Google will no longer support the use of third-party apps or devices which ask you to sign in to your Google Account using only your username and password, so “Allow less secure apps” will be removed.

In order to continue using SMTP with Gmail, you will need to set up an App Password for Amelia. App Passwords can only be used with accounts that have 2-Step Verification turned on. Instructions about this can be found on Google’s Documentation, here.

For detailed set-up instructions, please take a look at this article on our official support platform.

Microsoft SMTP (outlook, hotmail, live, and office365 email accounts):

If you’re having issues using SMTP with your Microsoft account, please make sure to set up an App Password for Amelia. App Passwords can only be used with accounts that have 2-Step Verification turned on in the Security Basics section of your Microsoft account. Instructions about this can be found on Microsoft’s Documentation, here.

For detailed set-up instructions, please take a look at this article on our official support platform.

Hope this helps. 

Hello again,

Same applies for any issue on the site. 

Please go to the notifications section inspect the page then try and send test notifications and then if there are any issues you will see the error in the network section. If there is any please send us a screenshot so that we can take a look.

Looking forward to your reply. 

Hello again,

Yes, we understand that. But you did not sent us screenshot of what we have asked for.

Please go to the notifications section inspect the page then try and send test notifications and then if there are any issues you will see the error in the network section. If there is any please send us a screenshot so that we can take a look.

So right click on a page then click on network just like in the screenshot and send us the error that you get.

Looking forward to your reply. 

Hi Francesca,

Marko is out of office, i will fill in for him on this one. It looks like the template "Tint - Patch test" is working properly 

But if I try the "Customer appointment approved", I do see this issue in developer console 

 

Forbidden Use Cases

Certain types of messages are not allowed, and we take these restrictions seriously to maintain a safe and reliable messaging environment for all users. It is essential to refrain from engaging in the following activities listed in the table below. Please note that these forbidden use cases are not only related to the content of the message but the business type itself.

Additional Restrictions

Even if your specific use case is not listed as prohibited, certain message content may still be subject to restrictions. For instance, the use of shared or free public URL shorteners is not permitted and will lead to filtering. Ensure that when using a shortened URL it is company branded.

 

Forbidden message categories for SMS/MMS in the US/Canada

 

 

 

 

Hi Francesca,

Apologies for the delayed response. It looks like everything is working properly now. I’ve sent a test email for "appointment approved," and this is the email I received.

It does have the company_website placeholder. Is it the same situation on your end?