User Story: Downloadable delivery reports for data wranglers

[jonathanbobel]

As a Data wrangler, I want access to indvidual-level delivery information by phone numbers of the messages sent by my service.

So that...

1. I can match delivered messages with my own client-level system data to track impact of text messages on my desired outcomes (e.g. did a message actually change behavior?)
2. I can communicate to outreach staff which phone numbers failed so they can conduct outreach with a follow-up phone call

Detailed condition or criteria that must be met for the user story to be considered complete.

Delivered Messages:

• The data wrangler should be able to view, access, download a list of successful messages by phone number or matchable client ID.

Failed Messages:

• The data wrangler should have visibility into a list of recipients who did not receive the text message.
• Include details such as recipient names, contact numbers, and reasons for failure (e.g., invalid number, network issues).

User-Friendly Interface:

• A clear way to access downloadable reports, with multiple day options (1, 3, 5, 7 days)
• Ensure that the information is presented in a clear and comprehensible manner for efficient tracking.
• Display window of time in which the report was generated/carrier statuses were pinged

Follow-Up Communication: (TBD)

• Implement functionality to facilitate communication with recipients who did not receive the message.
• Include options for sending follow-up messages or other ways of communication (e.g. text to voice)

Historical Data: (TBD)

• Include a historical data section that allows the data wrangler to view past delivery statuses for both Delivered and Failed messages.
• Make historical data sortable and filterable for better analysis.

Notification Alerts: (TBD)

• Implement a notification system to alert the data wrangler of any critical changes in delivery status, especially for Failed messages.

Downloadable Reports: (TBD)

• Allow the data wrangler to download comprehensive reports for both Delivered and Failed messages.
• The reports should be available in .CSV for easy sharing and analysis.
• Reports can/should be auto-emailed to wrangler

List of specific tasks or sub-tasks that need to be done to implement the user story.

• [ ] Delivered Messages:

  • [ ] Recipient Tracking:
  • [ ] The data wrangler can view a list of recipients who successfully received the text message.
  • [ ] Include details such as recipient names, contact numbers, and the timestamp of message delivery.

• [ ] Failed Messages:

  • [ ] Recipient Non-Delivery Tracking:
  • [ ] The data wrangler has visibility into a list of recipients who did not receive the text message.
  • [ ] Include details such as recipient names, contact numbers, and reasons for failure (e.g., invalid number, network issues).
  • [ ] Follow-Up Communication:
  • [ ] Implement functionality to facilitate communication with recipients who did not receive the message.
  • [ ] Include options for sending follow-up messages or other ways of communication.

• [ ] User-Friendly Interface:

  • [ ] Design the delivery status overview page with a user-friendly interface.
  • [ ] Ensure that the information is presented in a clear and comprehensible manner for efficient tracking.

• [ ] Historical Data:

  • [ ] Include a historical data section that allows the data wrangler to view past delivery statuses for both Delivered and Failed messages.
  • [ ] Make historical data sortable and filterable for better analysis.

• [ ] Notification Alerts:

  • [ ] Implement a notification system to alert the data wrangler of any critical changes in delivery status, especially for Failed messages.

• [ ] Downloadable Reports:

  • [ ] Allow the data wrangler to download comprehensive reports for both Delivered and Failed messages.
  • [ ] The reports should be available in .CSV for easy sharing and analysis.

List any dependencies that need to be resolved before starting or completing this user story.

Make sure all relevant data is available for front-end consumption

Any additional information or context that might be useful for the team.

No response

[em-herrick]

Need to add "opt-out" list to this user story. This feels like an epic. Break out user story further into near term needs vs. nice to have future needs