In my testing this morning, I surfaced numerous problems with the creation of a test notification message. I changed the appointment time of a test client from 11:00 to 12:00. but the resultant appointment showed up in the email message to the client as 4:11 which is 7 hours after the time zone I am in (PST).
Specific problems:
1) Wrong time zone on client's calendar (4:00 AM instead of 12:00 PM)
2) Message subject says "Service Name" instead of the value of %service_name%
3) Message is addressed to "John" instead of "Moxy". Who is John?
4) Appointment is with "Richard Roe" instead of "Bob Jones". Who is this Richard Roe person? He is not in my database.
5) Time in confirmation message is 4:11 instead of %appointment_start_time%.
6) Changed time does not show up in my Outlook calendar. In fact, nothing is showing up in that calendar.
7) Phone number in message sent is completely wrong.
Please advise ASAP. I cannot complete my testing with this many problems.
Bob Jones
(360) 756-2424
<<<< NOTIFICATION TEMPLATE >>>>
%customer_first_name%,
The details for your %service_name% appointment with %employee_full_name% have hanged. The appointment is now set for %appointment_date% at %appointment_start_time%.
If you have any questions about this change, please call %employee_first_name% at %employee_phone%.
The 'Notification Test Message' is just a random message to let you see if the template is correct and if the settings to send mails are working.
All informations inside those TEST messages will be random informations "John , Richard Roe, 11:27pm ..." It's not connected to the real bookings your clients made !
Once your notifications have been created the way you want them... You can try a LIVE test... it means that you book an appointment through your website as if you were a client ! At that moment, the notification email you will get will be correct with good informations (name, time, ...)
Thank you. Your explanation helps. Perhaps adding some content to the notification message that explains that the data is intentionally bogus would help.
One of the problems I noted was that %service-name% was not being replaced with a value. Is behavior also covered by the TEST case?
So, like Laurent said, and as I mentioned in the other ticket, the Test email option on the Amelia -> Notifications is mostly there for you to check whether the email notifications are sent or not. The placeholders and information sent using them needs to be tested using real bookings, as in the test options we put some examples for some placeholders and some of them will be the same only as text and if there is no real appointment for them there is no real information that can be sent.
So, please test the placeholders/information using real (test) appointments, and let me know if you have any issues with that.
In my testing this morning, I surfaced numerous problems with the creation of a test notification message. I changed the appointment time of a test client from 11:00 to 12:00. but the resultant appointment showed up in the email message to the client as 4:11 which is 7 hours after the time zone I am in (PST).
Specific problems:
1) Wrong time zone on client's calendar (4:00 AM instead of 12:00 PM)
2) Message subject says "Service Name" instead of the value of %service_name%
3) Message is addressed to "John" instead of "Moxy". Who is John?
4) Appointment is with "Richard Roe" instead of "Bob Jones". Who is this Richard Roe person? He is not in my database.
5) Time in confirmation message is 4:11 instead of %appointment_start_time%.
6) Changed time does not show up in my Outlook calendar. In fact, nothing is showing up in that calendar.
7) Phone number in message sent is completely wrong.
Please advise ASAP. I cannot complete my testing with this many problems.
Bob Jones
(360) 756-2424
<<<< NOTIFICATION TEMPLATE >>>>
%customer_first_name%,
The details for your %service_name% appointment with %employee_full_name% have hanged. The appointment is now set for %appointment_date% at %appointment_start_time%.
If you have any questions about this change, please call %employee_first_name% at %employee_phone%.
%employee_full_name%
%company_name%
<<<< MESSAGE CLIENT RECEIVED >>>>
Service Name Appointment Rescheduled
Bob Jones <[email protected]>
To:[email protected]
Sat, Sep 12 at 9:11 AM
John,
The details for your Service Name appointment with Richard Roe have hanged. The appointment is now set for September 12, 2020 at 4:11 pm.
If you have any questions about this change, please call Richard at 150-698-1858.
Richard Roe
Cave Bear Coaching
Hello,
The 'Notification Test Message' is just a random message to let you see if the template is correct and if the settings to send mails are working.
All informations inside those TEST messages will be random informations "John , Richard Roe, 11:27pm ..." It's not connected to the real bookings your clients made !
Once your notifications have been created the way you want them... You can try a LIVE test... it means that you book an appointment through your website as if you were a client ! At that moment, the notification email you will get will be correct with good informations (name, time, ...)
Laurent
(I'm a client, not a part of the Amelia Team)
Thank you. Your explanation helps. Perhaps adding some content to the notification message that explains that the data is intentionally bogus would help.
One of the problems I noted was that %service-name% was not being replaced with a value. Is behavior also covered by the TEST case?
Bob Jones
Hello Bob,
So, like Laurent said, and as I mentioned in the other ticket, the Test email option on the Amelia -> Notifications is mostly there for you to check whether the email notifications are sent or not. The placeholders and information sent using them needs to be tested using real bookings, as in the test options we put some examples for some placeholders and some of them will be the same only as text and if there is no real appointment for them there is no real information that can be sent.
So, please test the placeholders/information using real (test) appointments, and let me know if you have any issues with that.
Thank you for helping out, Laurent.