| **Scenario** | Sending automatic confirmation upon job acceptance |
| **Given** | Fluid accepts a job in the WMS |
| **When** | the job is accepted |
| **Then** | an automatic message is sent to the customer confirming the job acceptance and scheduled time |
| ##### | ##### **Good When** | ##### | ##### **Bad When** |
| Confirmation messages sent automatically without any unintended delay. | | Notifications are not sent or are unintentionally delayed. |
| Message includes all relevant job details, including the scheduled time and any other relevant information. | | Confirmation messages don't share required information about the job. |
| Customers receive confirmation in a clear format without the need for additional assurance. | | Messages are unreadable or unoptimised for all required devices |
| ##### **Completed When** |
| Every accepted job triggers an immediate, accurate, and formatted confirmation to the customer. |
| ##### **Start When** |
| When purchase order has been issued to the client. |
| ##### **Feature Priority** | - [x] ##### **High Priority** - ##### **Medium Priority** - [ ] ##### **Low Priority** |
| ##### **Client Approves Feature** | - [ ] **Approved** *Once approved, inform us by email, we will close the feature checklist and begin the process.* |
| ##### **Agreed Timeline** | Once approved the process will continue as - Create mock ups of the feature within 14 days of 'Start When' - Schedule of the project will be agreed within 14 days of ‘Start When', - Development of the feature once mocks up have been approved. - Q/A and delivery 7 days after development cycle Estimated development time for this feature would be **X days**, |