Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-1912

Send an email to clients when services are cancelled

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.6.0
    • Fix Version/s: 4.9.0-b1
    • Component/s: Staff Interface
    • Labels:
      None

      Description

      When services are cancelled, either manually or by a scheduled cancellation, no notice is sent to clients. Instead, an email should optionally be sent to clients to notify them of a cancelled service. It should also send a notice to clients when services are scheduled to be cancelled, so they are aware of the pending action.

      • Create 1 or 2 new email templates for scheduled cancellation and cancellation notices
      • Add company & client group setting for whether these notices should be sent at all, make them off by default.

      Needs further discussion, including sample email content and available tags/data to the templates. Please see http://www.blesta.com/forums/index.php?/topic/5112-notice-service-cancellation-email/ for discussion on this topic, and https://www.blesta.com/forums/index.php?/topic/10960-cancellation-request-confirmation-email/.

        Issue Links

          Activity

          admin Paul Phillips created issue -
          tyson Tyson Phillips (Inactive) made changes -
          Field Original Value New Value
          Link This issue relates to CORE-1564 [ CORE-1564 ]
          admin Paul Phillips made changes -
          Fix Version/s Short Term [ 10800 ]
          tyson Tyson Phillips (Inactive) made changes -
          Description When services are cancelled, either manually or by a scheduled cancellation, no notice is sent to clients. Instead, an email should *optionally* be sent to clients to notify them of a cancelled service. It should also send a notice to clients when services are scheduled to be cancelled, so they are aware of the pending action.

          - Create 1 or 2 new email templates for scheduled cancellation and cancellation notices
          - Add company & client group setting for whether these notices should be sent at all, make them off by default.

          Needs further discussion, including sample email content and available tags/data to the templates. Please see http://www.blesta.com/forums/index.php?/topic/5112-notice-service-cancellation-email/ for discussion on this topic.
          When services are cancelled, either manually or by a scheduled cancellation, no notice is sent to clients. Instead, an email should *optionally* be sent to clients to notify them of a cancelled service. It should also send a notice to clients when services are scheduled to be cancelled, so they are aware of the pending action.

          - Create 1 or 2 new email templates for scheduled cancellation and cancellation notices
          - Add company & client group setting for whether these notices should be sent at all, make them off by default.

          Needs further discussion, including sample email content and available tags/data to the templates. Please see http://www.blesta.com/forums/index.php?/topic/5112-notice-service-cancellation-email/ for discussion on this topic, and https://www.blesta.com/forums/index.php?/topic/10960-cancellation-request-confirmation-email/.
          admin Paul Phillips made changes -
          Rank Ranked higher
          admin Paul Phillips made changes -
          Rank Ranked higher
          tyson Tyson Phillips (Inactive) made changes -
          Rank Ranked higher
          tyson Tyson Phillips (Inactive) made changes -
          Sprint 4.9.0 Sprint 1 [ 98 ]
          tyson Tyson Phillips (Inactive) made changes -
          Rank Ranked higher
          tyson Tyson Phillips (Inactive) made changes -
          Story Points 5
          Hide
          tyson Tyson Phillips (Inactive) added a comment -

          I would think for this that we would have an email template for "Service Cancellation" similar to the other "Service <Creation/Suspension/Unsuspension>". We can have the email template disabled by default.

          The content of the email would be something like:

          Hi {contact.first_name},

          Your service, {package.name} - {service.name}, has been canceled.

          Then whenever a service is canceled, that email will be delivered to the client and any staff BCC'd to receive it as well. That's it.

          The "scheduled cancellation reminder" would be handled by CORE-1564

          Show
          tyson Tyson Phillips (Inactive) added a comment - I would think for this that we would have an email template for "Service Cancellation" similar to the other "Service <Creation/Suspension/Unsuspension>". We can have the email template disabled by default. The content of the email would be something like: Hi {contact.first_name}, Your service, {package.name} - {service.name}, has been canceled. Then whenever a service is canceled, that email will be delivered to the client and any staff BCC'd to receive it as well. That's it. The "scheduled cancellation reminder" would be handled by CORE-1564
          tyson Tyson Phillips (Inactive) made changes -
          Sprint 4.9.0 Sprint 1 [ 98 ] 4.9.0 Sprint 1, 4.9.0 Sprint 2 [ 98, 99 ]
          tyson Tyson Phillips (Inactive) made changes -
          Rank Ranked higher
          jonathan Jonathan Reissmueller made changes -
          Assignee Jonathan Reissmueller [ jonathan ]
          Automated transition triggered when Jonathan Reissmueller created a branch in Stash -
          Status Open [ 1 ] In Progress [ 3 ]
          jonathan Jonathan Reissmueller made changes -
          Remaining Estimate 0 minutes [ 0 ]
          Time Spent 1 hour, 54 minutes [ 6840 ]
          Worklog Id 12991 [ 12991 ]
          jonathan Jonathan Reissmueller made changes -
          Time Spent 1 hour, 54 minutes [ 6840 ] 2 hours, 40 minutes [ 9600 ]
          Worklog Id 12992 [ 12992 ]
          Automated transition triggered when Jonathan Reissmueller created pull request #785 in Stash -
          Status In Progress [ 3 ] In Review [ 5 ]
          Resolution Fixed [ 1 ]
          tyson Tyson Phillips (Inactive) made changes -
          Fix Version/s 4.9.0-b1 [ 11301 ]
          Fix Version/s Short Term [ 10800 ]
          tyson Tyson Phillips (Inactive) made changes -
          Sprint 4.9.0 Sprint 1, 4.9.0 Sprint 2 [ 98, 99 ] 4.9.0 Sprint 1, 4.9.0 Sprint 2, 4.9.0 Sprint 3 [ 98, 99, 101 ]
          tyson Tyson Phillips (Inactive) made changes -
          Rank Ranked higher
          jonathan Jonathan Reissmueller made changes -
          Time Spent 2 hours, 40 minutes [ 9600 ] 4 hours, 3 minutes [ 14580 ]
          Worklog Id 13115 [ 13115 ]
          jonathan Jonathan Reissmueller made changes -
          Time Spent 4 hours, 3 minutes [ 14580 ] 4 hours, 58 minutes [ 17880 ]
          Worklog Id 13148 [ 13148 ]
          tyson Tyson Phillips (Inactive) made changes -
          Sprint 4.9.0 Sprint 1, 4.9.0 Sprint 2, 4.9.0 Sprint 3 [ 98, 99, 101 ] 4.9.0 Sprint 1, 4.9.0 Sprint 2, 4.9.0 Sprint 3, 4.9.0 Sprint 4 [ 98, 99, 101, 102 ]
          Hide
          tyson Tyson Phillips (Inactive) added a comment -

          Be sure the new setting gets added to the documentation.

          Show
          tyson Tyson Phillips (Inactive) added a comment - Be sure the new setting gets added to the documentation.
          jonathan Jonathan Reissmueller made changes -
          Time Spent 4 hours, 58 minutes [ 17880 ] 5 hours, 59 minutes [ 21540 ]
          Worklog Id 13184 [ 13184 ]
          Automated transition triggered when Tyson Phillips (Inactive) merged pull request #785 in Stash -
          Status In Review [ 5 ] Closed [ 6 ]

            People

            • Assignee:
              jonathan Jonathan Reissmueller
              Reporter:
              admin Paul Phillips
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Fix Release Date:
                31/Mar/20

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 5 hours, 59 minutes
                5h 59m

                  Agile