Stakeholder feedback changes

Author: jakecosgrove

docs/_includes/custom-components/campaign-feature-list.html

@@ -94,8 +94,8 @@ <h3 class="nhsuk-heading-s">Message channels</h3>
   </tbody>
 </table>
 
-<!-- Additional message formats -->
-<h3 class="nhsuk-heading-s">Additional message formats</h3>
+<!-- Additional letter formats -->
+<h3 class="nhsuk-heading-s">Additional letter formats</h3>
 <table class="nhsuk-table">
   <thead class="nhsuk-table__head nhsuk-u-visually-hidden">
     <tr>
@@ -246,10 +246,26 @@ <h3 class="nhsuk-heading-s">Sending messages</h3>
     </tr>
   </thead>
   <tbody class="nhsuk-table__body">
+    <tr class="nhsuk-table__row">
+      <td class="nhsuk-table__cell">Automatic contact look up (mandatory)
+        <div class="nhsuk-hint">
+          NHS Notify automatically finds and uses your recipients contact details from their NHS number
+        </div>
+      </td>
+      <td class="nhsuk-table__cell">
+        <abbr title="Yes">
+          <svg class="nhsuk-icon nhsuk-icon__tick" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none"
+            aria-hidden="true" width="34" height="34">
+            <path stroke-width="4" stroke-linecap="round" d="M18.4 7.8l-8.5 8.4L5.6 12" stroke="#007f3b"></path>
+          </svg>
+        </abbr>
+      </td>
+    </tr>
     <tr class="nhsuk-table__row">
       <td class="nhsuk-table__cell">Rate limiting
         <div class="nhsuk-hint">
-          Set how many messages are sent per second to control how often recipients access your service
+          Set how many messages are sent per second to control how often recipients access your service, also known as
+          transactions per second (TPS)
         </div>
       </td>
       <td class="nhsuk-table__cell">Up to 5TPS</td>
@@ -283,19 +299,21 @@ <h3 class="nhsuk-heading-s">Sending messages</h3>
     <tr class="nhsuk-table__row">
       <td class="nhsuk-table__cell">Fallback rules
         <div class="nhsuk-hint">
-          The following fallback rules will apply to message channels used in your routing plans:
+          The rules that trigger when a fallback is used for each message channel in a routing plan
         </div>
-        <p>
+        <p class="nhsuk-body">
           All digital message channels will immediately fallback to the next channel if its rejected or an 'unnotified'
           status is received.
         </p>
-        <p>NHS App messages will fallback to the next channel when:</p>
+        <p class="nhsuk-body">NHS App messages will fallback to the next channel when:</p>
         <ul class="nhsuk-list nhsuk-list--bullet">
           <li>a 'notified' status is not received within 1 hour</li>
           <li>the message is not read by the recipient within 24 hours</li>
         </ul>
-        <p>Emails and text messages will fallback to the next channel if they are XYZ after 72 hours </p>
-        <p>Letters do not have any fallback rules as they’re always sent last in routing plans for transactional
+        <p class="nhsuk-body">Emails and text messages will fallback to the next channel if they are not delivered after
+          72 hours </p>
+        <p class="nhsuk-body">Letters do not have any fallback rules as they’re always sent last in routing plans for
+          transactional
           messages.</p>
       </td>
       <td class="nhsuk-table__cell">
@@ -332,10 +350,10 @@ <h3 class="nhsuk-heading-s">Sending messages</h3>
         <div class="nhsuk-hint">
           NHS Notify prevents you from sending messages to specific recipients to make your messaging more effective
         </div>
-        <p>You cannot send transactional messages to recipients with:</p>
+        <p>You cannot send campaign messages to recipients with:</p>
         <ul class="nhsuk-list nhsuk-list--bullet">
           <li>flagged records</li>
-          <li>exit codes (also known as reason for removal codes)</li>
+          <li>reason for removal codes (also known as exit codes)</li>
           <li>international addresses</li>
           <li>invalid postcodes</li>
           <li>invalid email addresses</li>

docs/_includes/custom-components/direct-message-feature-list.html

@@ -99,8 +99,8 @@ <h3 class="nhsuk-heading-s">Message channels</h3>
   </tbody>
 </table>
 
-<!-- Additional message formats -->
-<h3 class="nhsuk-heading-s">Additional message formats</h3>
+<!-- Additional letter formats -->
+<h3 class="nhsuk-heading-s">Additional letter formats</h3>
 <table class="nhsuk-table">
   <thead class="nhsuk-table__head nhsuk-u-visually-hidden">
     <tr>
@@ -276,10 +276,26 @@ <h3 class="nhsuk-heading-s">Sending messages</h3>
     </tr>
   </thead>
   <tbody class="nhsuk-table__body">
+    <tr class="nhsuk-table__row">
+      <td class="nhsuk-table__cell">Automatic contact look up (mandatory)
+        <div class="nhsuk-hint">
+          NHS Notify automatically finds and uses your recipients contact details from their NHS number
+        </div>
+      </td>
+      <td class="nhsuk-table__cell">
+        <abbr title="Yes">
+          <svg class="nhsuk-icon nhsuk-icon__tick" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none"
+            aria-hidden="true" width="34" height="34">
+            <path stroke-width="4" stroke-linecap="round" d="M18.4 7.8l-8.5 8.4L5.6 12" stroke="#007f3b"></path>
+          </svg>
+        </abbr>
+      </td>
+    </tr>
     <tr class="nhsuk-table__row">
       <td class="nhsuk-table__cell">Rate limiting
         <div class="nhsuk-hint">
-          Set how many messages are sent per second to control how often recipients access your service
+          Set how many messages are sent per second to control how often recipients access your service, also known as
+          transactions per second (TPS)
         </div>
       </td>
       <td class="nhsuk-table__cell">Up to 5TPS</td>
@@ -307,7 +323,7 @@ <h3 class="nhsuk-heading-s">Sending messages</h3>
     <tr class="nhsuk-table__row">
       <td class="nhsuk-table__cell">Fallback rules
         <div class="nhsuk-hint">
-          These are rules that trigger when a fallback is used for each message channel in a routing plan
+          The rules that trigger when a fallback is used for each message channel in a routing plan
         </div>
         <p>
           If you send direct messages with the NHS App you must create your own fallback functionality and adhere to the
@@ -366,10 +382,10 @@ <h4 class="nhsuk-heading-xs">3. Acute secondary care appointment NHS App message
         <div class="nhsuk-hint">
           NHS Notify prevents you from sending messages to specific recipients to make your messaging more effective
         </div>
-        <p>You cannot send transactional messages to recipients with:</p>
+        <p>You cannot send direct messages to recipients with:</p>
         <ul class="nhsuk-list nhsuk-list--bullet">
           <li>flagged records</li>
-          <li>exit codes (also known as reason for removal codes)</li>
+          <li>reason for removal codes (also known as exit codes)</li>
           <li>international addresses</li>
           <li>invalid postcodes</li>
           <li>invalid email addresses</li>

docs/_includes/custom-components/transactional-feature-list.html

@@ -98,8 +98,8 @@ <h3 class="nhsuk-heading-s">Message channels</h3>
   </tbody>
 </table>
 
-<!-- Additional message formats -->
-<h3 class="nhsuk-heading-s">Additional message formats</h3>
+<!-- Additional letter formats -->
+<h3 class="nhsuk-heading-s">Additional letter formats</h3>
 <table class="nhsuk-table">
   <thead class="nhsuk-table__head nhsuk-u-visually-hidden">
     <tr>
@@ -246,14 +246,14 @@ <h3 class="nhsuk-heading-s">Sending messages</h3>
   <thead class="nhsuk-table__head nhsuk-u-visually-hidden">
     <tr>
       <th scope="col" class="nhsuk-table__header">Feature</th>
-      <th scope="col" class="nhsuk-table__header">Included for transactional messages</th>
+      <th scope="col" class="nhsuk-table__header">Included</th>
     </tr>
   </thead>
   <tbody class="nhsuk-table__body">
     <tr class="nhsuk-table__row">
-      <td class="nhsuk-table__cell">Personalisation
+      <td class="nhsuk-table__cell">Automatic contact look up (mandatory)
         <div class="nhsuk-hint">
-          Add details like your recipients name, appointment times or reference numbers to your messages
+          NHS Notify automatically finds and uses your recipients contact details from their NHS number
         </div>
       </td>
       <td class="nhsuk-table__cell">
@@ -268,7 +268,8 @@ <h3 class="nhsuk-heading-s">Sending messages</h3>
     <tr class="nhsuk-table__row">
       <td class="nhsuk-table__cell">Rate limiting
         <div class="nhsuk-hint">
-          Set how many messages are sent per second to control how often recipients access your service
+          Set how many messages are sent per second to control how often recipients access your service, also known as
+          transactions per second (TPS)
         </div>
       </td>
       <td class="nhsuk-table__cell">Up to 5TPS</td>
@@ -278,7 +279,7 @@ <h3 class="nhsuk-heading-s">Sending messages</h3>
         <div class="nhsuk-hint">
           Use routing plans to decide how messages will be sent to your recipients and in what orders.
         </div>
-        <p class="nhsuk-body">You can send transactional messages in the following ways:</p>
+        <p class="nhsuk-body">You can send event based messages in the following ways:</p>
         <ul class="nhsuk-list nhsuk-list--bullet">
           <li>NHS App message only</li>
           <li>NHS App message, Email</li>
@@ -301,9 +302,9 @@ <h3 class="nhsuk-heading-s">Sending messages</h3>
     <tr class="nhsuk-table__row">
       <td class="nhsuk-table__cell">Fallback rules
         <div class="nhsuk-hint">
-          The following fallback rules will apply to message channels used in your routing plans:
+          The rules that trigger when a fallback is used for each message channel in a routing plan
         </div>
-        <p>
+        <p class="nhsuk-body">
           All digital message channels will immediately fallback to the next channel if its rejected or an 'unnotified'
           status is received.
         </p>
@@ -313,7 +314,7 @@ <h3 class="nhsuk-heading-s">Sending messages</h3>
           <li>a 'notified' status is not received within 1 hour</li>
           <li>the message is not read by the recipient within 24 hours</li>
         </ul>
-        <p>Emails and text messages will fallback to the next channel if they are XYZ after 72 hours </p>
+        <p>Emails and text messages will fallback to the next channel if they are not delivered after 72 hours </p>
         <p>Letters do not have any fallback rules as they’re always sent last in routing plans for transactional
           messages.</p>
       </td>
@@ -351,10 +352,10 @@ <h3 class="nhsuk-heading-s">Sending messages</h3>
         <div class="nhsuk-hint">
           NHS Notify prevents you from sending messages to specific recipients to make your messaging more effective
         </div>
-        <p>You cannot send transactional messages to recipients with:</p>
+        <p>You cannot send event based messages to recipients with:</p>
         <ul class="nhsuk-list nhsuk-list--bullet">
           <li>flagged records</li>
-          <li>exit codes (also known as reason for removal codes)</li>
+          <li>reason for removal codes (also known as exit codes)</li>
           <li>international addresses</li>
           <li>invalid postcodes</li>
           <li>invalid email addresses</li>

docs/pages/using-nhs-notify/campaigns.md

@@ -10,7 +10,7 @@ permalink: /using-nhs-notify/campaigns
 section: By use case
 ---
 
-Use NHS Notify to set up national or local campaigns to send messages in bulk to patients and the public.
+Use NHS Notify to set up national or targeted campaigns to send messages in bulk to patients and the public.
 
 ## Examples of campaign messaging
 

docs/pages/using-nhs-notify/event-based-messaging.md

@@ -10,7 +10,7 @@ permalink: /using-nhs-notify/event-based-messaging
 section: By use case
 ---
 
-Use NHS Notify to send messages to your recipients when a specific event is triggered in your organisation or service.
+Use NHS Notify to send messages to patients and the public when a specific event is triggered in your organisation or service.
 
 ## Examples of event based messaging