-
Type: Epic
-
Status: In Progress
-
Priority: Medium
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: Email communication
-
Labels:None
-
Company:CareerBuilder
-
Epic Name:Email Texting Push Communication and History
Overview:
2-way communication between users of the system, (Admins / Hiring Mangers / Recruiters / Candidates) through email, texting, push notifications, while also keeping a historic record and tracking of messages.
User Stories
1. As a user, I want to be able to send and capture emails within the portal so that all messaging is accurately documented and sent from one place.
2. As a user, I want to be able to send and capture text messages within the portal so that all messaging is accurately documented and sent from one place.
3. As a user, I want to be able to send push notifications from within the portal so that I can message / send notifications to end users.
4. As a user, I want to be able to see a historic record of all messaging (email / text / push) that has been sent from the portal so that I have an accurate trail of what has been done / what candidates have received.
5. As a user, I want to be able to see when a candidate received a message (timestamp) so that I know that user actually got the message.
6. As a user, I want to be able to see when a candidate read or opened a message sent from the portal so that I know when they read it.
7. As a user, I know that if I hit ‘send’, the message is queued up to be sent in the portal so that it will be sent off to the end user.
8. As a user, I know that all messages sent from center are compliant so that I do not break any sort of law (for example, TCPA for texting).
9. As a user, I want to be able to input email communication into multiple languages so that if an end user has chosen a preference of receiving an email in a different language other than English, they will see it in the proper language.
Entry Criteria:
1. The user navigates to DMS.
2. The user navigates to send a message via email, text, or push notification.
3. The user sends message.
Exit Criteria:
- The user sees that message has been sent in the history and exits out of portal if logged in, or navigates to another page.
Acceptance Criteria:
- IF I am a user in the portal, I am able to send an email message to a candidate from the portal, as well as receive their response back in the portal.
- IF I am a user in the portal, I am able to send a text message to a candidate from the portal, as well as receive their response back in the portal.
- IF I am a user in the portal, I am able to send a push notification from the portal.
- IF I am a candidate, I am able to opt into receiving a text message from company.
- IF I am a user in the portal, I am able to see a historic trail of all messages within the message history (email, text, push) sent from portal as well as differentiate what type of message it was.
- IF I am a user in the portal, I am able to see a status of a sent message as to when the candidate received and opened a message.
- IF I have hit send on a message in the portal, the message gets queued for sending, and will send at next push to the end user.
- IF anyone is using the messaging center, it follows all compliance rules and not rule will be broken.
- IF I have created an email template, I can also put translations in for other languages easily.
Prerequisites:
- User has access to DMS.
- User has access to Message History.
- User has access to send messages (email, text, or push)