The verbiage of the “from” on automated email notifications were inconsistent, some had “Support Ticket – Tech Team” , some had “Ticket Support – Tech Team”.
It MUST BE :
“Ticket Support – Tech Team”
Why? Because the distinctions need to be specified. There are different types of Tech Team Support.
“Ticket Support – Tech Team”
“Chat Support – Tech Team”
“Email Support – Tech Team”
“Phone Support – Tech Team”
“Field / Client Onsite Support – Tech Team”
And specific Consultant Assignments get different billable hours. They need to be quantified.
Options > Languages > Translate
Tweaked ID #9 as well.
For Admins, you can also generate Reports for Staff and Ticket Resolutions or Status. You can filter them by dates. For the Ticket Package Test date Range 6-9 to 6-11.
I’ve closed all the Test Tickets. This package is good to go. 🙂
CON or MOD,
On the Ticket Support Portal
I didn’t change the path for the Ticket Support portal. The old one, with the old version, I moved and archived. I scrutinized the code and figured why it quit working. The field name and label was changed from TiketID to TicketID. When I first installed it, I noticed that, but it’s a typo and knew it would cause a problem once that typo is fixed. It’s a Ticket Portal and so if naming conventions are misspelled, and eventually changed, that would cause DB errors for those portals that were installed with the original naming convention “Tiket”, instead of “Ticket”, since it would be pulling from a DB field that no longer exist. When I went to the DB, I saw how this would be impossible to troubleshoot, as PWs are not shown on the DB, (because it’s stored in BLOB). So when one triggers the “forgot PW link, it will just say that “the email doesn’t exist”. Why? Because the “Tiket ID” (yes the old misspelled field) has been changed to “Ticket ID”, so those assigned to the New Tickets, etc., cannot be found. It’s pulling from a different field and field table. So that one was corrupted, so it was better for me to start from scratch. I used the later version on it from AXN.
On the Appointment Scheduler Portal
I changed the path on this because I was scrutinizing code and why it quit working. On the GUI. I noticed that the Company Details on the old version disappeared, ergo, it’s not pulling from the old tables. The phenomenon is something like what happened on the Ticket Portal.
Let’s test the new appointment installation now.
Don’t forget to clear your cache before looking into it and testing it. The footer is your SIGN that you are testing the right one. I added the 2015 – 2021 year. That’s what we are testing. I am not putting the direct URL’s here because it is admin type access only. (Sorry hackers / trollers). 🙂
The “Professionalists” .. the new installation has all the smiley Avatars? Shouldn’t we change the term to U.S. “Professionals” instead?
You can change it at:
Options > Languages > Translate
Then type on the Search “Professionalists” the ID # would display. You can change it there.
I changed it to “Professionals”
(Professionalists is a UK term, since we are using UK English as a default language). Good catch!
I added verbiage “or GMT -6:00). ” on Services:
“On the “Notes” area of the form below, kindly include your best phone number (which will be your Signal App user ID), so we can synchronize our phones faster. (Our Online Scheduler is synced with our Work Calendars, in Central Standard Time – CST or GMT -6:00). ”
I also reviewed the verbiage on the automated email notifications.
The parties are:
1) Client
2) Manager
3) Staff
All three are CC’d on the notifications so everyone is on the same page.
I temporarily opened a Custom Work Schedule for tonight, so we can test more. 9PM to midnight. I also added a 1 hour email notification before scheduled appointment.
I will revert it back to 10 hours before booking, after I’ve seen it to work.
Let’s go! 🙂
I tested the payment flow and noticed that the logo was not displaying. Let’s just use the default templates of Paypal. There was an announcement there that PayPal also will be moving to the “cloud”, so God knows a lot of logos would break, if the paths to the image files change too.
Another change, I also converted the Payment Notification from HTML to text.
That’s minimized “phishing” because people can clearly see where the links are going to.
So that works.
So the Client will get this type of email:
—————–
“Hi Cris Testing,
Thank you for booking an appointment with us. Kindly save this email for your records.
ID: JT1623466507
Service/s:
Test Transaction for Clients – Live Payment :
06/11/2021
11:00 PM – 11:15 PM
Personal details:
Name: Cris Testing
Phone: REDACTED
Email: REDACTED
This is the price for your booking:
Tax: $0.50
Tax: $0.04
Total: $0.54
Deposit required to confirm your booking: $0.54
Additional notes:
Test Transaction for Clients – Live Payment
The link above is code specific – so since I set up that appointments for the Free 15 minute comsultation – they can cancel at least 2 hours before the scheduled appointment.
——————–
It goes to the Thank You Page, advising client to check their email.
Also, I included automation, that would send an email reminder, which for this Testing Session Date, I set to 1 hour. (Normally the reminder is set to 10 Hours).
So the System message returns this message:
“System message
You need to cancel the booking 2 hour(s) before the appointment start.”
The cancellation link works for other Free appointments scheduled in the future (above 2 hours notice).
The paid services can’t be cancelled. Clients need to think hard before paying. It will save everybody the headache, and time.
Each appointment Schedule flow, from scheduling to cancellation, the 3 parties above get notified.
Done deal. This package is also good to go.
Cancelled all the “test” bookings, so the time slots will be open again. The testing for tonight will automatically expire by 12 MN.
Did some more tweaks:
1) Ticket Support Portal
The verbiage of the “from” on automated email notifications were inconsistent, some had “Support Ticket – Tech Team” , some had “Ticket Support – Tech Team”.
It MUST BE :
“Ticket Support – Tech Team”
Why? Because the distinctions need to be specified. There are different types of Tech Team Support.
“Ticket Support – Tech Team”
“Chat Support – Tech Team”
“Email Support – Tech Team”
“Phone Support – Tech Team”
“Field / Client Onsite Support – Tech Team”
And specific Consultant Assignments get different billable hours. They need to be quantified.
Options > Languages > Translate
Tweaked ID #9 as well.
For Admins, you can also generate Reports for Staff and Ticket Resolutions or Status. You can filter them by dates. For the Ticket Package Test date Range 6-9 to 6-11.
I’ve closed all the Test Tickets. This package is good to go. 🙂
CON or MOD,
On the Ticket Support Portal
I didn’t change the path for the Ticket Support portal. The old one, with the old version, I moved and archived. I scrutinized the code and figured why it quit working. The field name and label was changed from TiketID to TicketID. When I first installed it, I noticed that, but it’s a typo and knew it would cause a problem once that typo is fixed. It’s a Ticket Portal and so if naming conventions are misspelled, and eventually changed, that would cause DB errors for those portals that were installed with the original naming convention “Tiket”, instead of “Ticket”, since it would be pulling from a DB field that no longer exist. When I went to the DB, I saw how this would be impossible to troubleshoot, as PWs are not shown on the DB, (because it’s stored in BLOB). So when one triggers the “forgot PW link, it will just say that “the email doesn’t exist”. Why? Because the “Tiket ID” (yes the old misspelled field) has been changed to “Ticket ID”, so those assigned to the New Tickets, etc., cannot be found. It’s pulling from a different field and field table. So that one was corrupted, so it was better for me to start from scratch. I used the later version on it from AXN.
On the Appointment Scheduler Portal
I changed the path on this because I was scrutinizing code and why it quit working. On the GUI. I noticed that the Company Details on the old version disappeared, ergo, it’s not pulling from the old tables. The phenomenon is something like what happened on the Ticket Portal.
Let’s test the new appointment installation now.
Don’t forget to clear your cache before looking into it and testing it. The footer is your SIGN that you are testing the right one. I added the 2015 – 2021 year. That’s what we are testing. I am not putting the direct URL’s here because it is admin type access only. (Sorry hackers / trollers). 🙂
The “Professionalists” .. the new installation has all the smiley Avatars? Shouldn’t we change the term to U.S. “Professionals” instead?
You can change it at:
Options > Languages > Translate
Then type on the Search “Professionalists” the ID # would display. You can change it there.
I changed it to “Professionals”
(Professionalists is a UK term, since we are using UK English as a default language). Good catch!
I added verbiage “or GMT -6:00). ” on Services:
“On the “Notes” area of the form below, kindly include your best phone number (which will be your Signal App user ID), so we can synchronize our phones faster. (Our Online Scheduler is synced with our Work Calendars, in Central Standard Time – CST or GMT -6:00). ”
I also reviewed the verbiage on the automated email notifications.
The parties are:
1) Client
2) Manager
3) Staff
All three are CC’d on the notifications so everyone is on the same page.
I temporarily opened a Custom Work Schedule for tonight, so we can test more. 9PM to midnight. I also added a 1 hour email notification before scheduled appointment.
I will revert it back to 10 hours before booking, after I’ve seen it to work.
Let’s go! 🙂
I tested the payment flow and noticed that the logo was not displaying. Let’s just use the default templates of Paypal. There was an announcement there that PayPal also will be moving to the “cloud”, so God knows a lot of logos would break, if the paths to the image files change too.
Another change, I also converted the Payment Notification from HTML to text.
That’s minimized “phishing” because people can clearly see where the links are going to.
So that works.
So the Client will get this type of email:
—————–
“Hi Cris Testing,
Thank you for booking an appointment with us. Kindly save this email for your records.
ID: JT1623466507
Service/s:
Test Transaction for Clients – Live Payment :
06/11/2021
11:00 PM – 11:15 PM
Personal details:
Name: Cris Testing
Phone: REDACTED
Email: REDACTED
This is the price for your booking:
Tax: $0.50
Tax: $0.04
Total: $0.54
Deposit required to confirm your booking: $0.54
Additional notes:
Test Transaction for Clients – Live Payment
3) IT Consultant
06/11/2021
11:00 PM – 11:15 PM
We look forward to connecting with you!
All the best,
Business Development – Tech Team
P.S. If for any reason, you need to cancel, just let us know at least 2 hours in advance, so we can open up the slot for other clients. You can cancel at: https://www.agdtechnology.com/sc21/index.php?controller=pjFrontEnd&action=pjActionCancel&cid=1&id=3&hash=d4de8cab7cf45aa485047fb4e40d47b510ecd744
The link above is code specific – so since I set up that appointments for the Free 15 minute comsultation – they can cancel at least 2 hours before the scheduled appointment.
——————–
It goes to the Thank You Page, advising client to check their email.
Also, I included automation, that would send an email reminder, which for this Testing Session Date, I set to 1 hour. (Normally the reminder is set to 10 Hours).
So the System message returns this message:
“System message
You need to cancel the booking 2 hour(s) before the appointment start.”
The cancellation link works for other Free appointments scheduled in the future (above 2 hours notice).
The paid services can’t be cancelled. Clients need to think hard before paying. It will save everybody the headache, and time.
Each appointment Schedule flow, from scheduling to cancellation, the 3 parties above get notified.
Done deal. This package is also good to go.
Cancelled all the “test” bookings, so the time slots will be open again. The testing for tonight will automatically expire by 12 MN.