Request received email confirmation for applicant

As an applicant, I want an email confirmation so that I know my request was received

**Acceptance Criteria**

**Scenario 1: Receipt email*
* GIVEN an applicant has entered a valid email address in the Submit a Request app
* WHEN the applicant clicks 'Submit'
* THEN an email will be sent to the applicant's email address with the following content:
(Matt or Arielle to enter CONTENT here)

DRAFT (awaiting validation from Intake)
Request submitted!

Your Freedom of Information request has been received. An analyst from Information Access Operations will review your request and get in touch with you about next steps.

Please note this is not confirmation an FOI request file has been opened. You will receive further correspondence once an analyst has reviewed your request.

Information Access Operations
www.gov.bc.ca/freedomofinformation
250 387-1321

**Dependencies?
Email notification service

Email content

**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?

**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?

Start with the Submit a Request app flow and locate the Email notification service dependency. Confirm the receipt-email content with Intake and the named stakeholders before implementation. Done means a valid submission sends the approved message to the applicant and the acceptance criteria and developer tests pass.

Written by the indexing model from the issue text.