Select Redirect letter wording

* As an Intake analyst
* I want to add templated wording for common redirects
* so that I can easily customize template letters with minimal manual effort

**Assumptions & Scope**
Wording to be added to letters has been drafted by UX and SMEs
Wording is the same for Personal and General requests

What is in and not in scope?
In scope: selecting multiple redirect options
Not in scope: expanding 'See More Options' field

**Acceptance Criteria**

**Scenario 1: Select one option**
* GIVEN the analyst has selected Redirect in Full on the Review Request screen
* WHEN the analyst selects one of the 12 options for where to redirect the applicant [Final options still TBD]
* AND the analyst clicks Create Redirect Letter
* THEN the analyst will be taken to the Correspondence screen
* AND the generated letter will be available as a link
* AND the letter will contain the templated wording corresponding to the analyst's selection

**Scenario 2: Select multiple options**
* GIVEN the analyst has selected Redirect in Full on the Review Request screen
* WHEN the analyst selects one of the 12 options for where to redirect the applicant [Final options still TBD]
* AND the analyst clicks Create Redirect Letter
* THEN the analyst will be taken to the Correspondence screen
* AND the generated letter will be available as a link
* AND the letter will contain the templated redirect wording corresponding to the analyst's selection
* AND the templated redirect wording will appear in the order in which they appeared in the selection list

**Scenario 3: Deselect options**
...

**Dependencies? What is the impact of this dependency? (If so, link dependency in the ticket, make it visible in a team´s backlog)**
Questions: When would the request status change to Redirect? When the analyst has clicked Redirect in Full or when they go to create the letter? What about partial redirects?

**Validation Rules? (If yes, list here)**

**Design**
@xxx - please link the Design here

**Definition of Ready**

1. [ ] Is there a well articulated User Story?
2. [ ] Is there Acceptance Criteria that covers all scenarios (happy/sad paths)?
3. [ ] If there is a user interface, is there a design?
4. [ ] Does the user story need user research/validation?
5. [ ] Does this User Story needs stakeholder approval?
6. [ ] Design / Solution accepted by Product Owner
7. [ ] Is this user story small enough to be completed in a Sprint? Should it be split?
8. [ ] Are the dependencies known/ understood? (technical, business, regulatory/policy)
9. [ ] Has the story been estimated?

**Tasks**
-[ ]- API
-[ ]- UX
-[ ]-DB

**Definition of Done**

1. [ ] Passes developer unit tests
2. [ ] Passes peer code review
3. [ ] If there's a user interface, passes UX assurance
4. [ ] Passes QA of Acceptance Criteria with verification in Dev and Test
5. [ ] Confirm Test cases built and succeeding
6. [ ] No regression test failures
7. [ ] Test coverage acceptable by Product Owner
8. [ ] Ticket ready to be merged to master or story branch
9. [ ] Developer to list Config changes/ Update documents and designs
10. [ ] Can be demoed in Sprint Review
11. [ ] Tagged as part of a Release
12. [ ] Feature flagged if required
13. [ ] Change Management activities done?
14. [ ] Refinement : Expectation is complete the API, UX, DB part to complete

Start by reviewing the Review Request and Correspondence screens and clarifying the API, UX, and DB tasks listed in the issue. Resolve the unanswered redirect-status questions, finalize the 12 options and missing scenarios, and confirm the design before implementing. Done means selected redirect wording appears in the generated letter in selection order for single, multiple, and deselected options.

Written by the indexing model from the issue text.