You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(may need to split this out into a flow map w/ decision loops, but for now trying to do it as simpler features)
Feature: SMS reminder sign-up
As an interested party, I want to sign up for reminders on all hearings (of a given Case Number)
so that I can ensure the defendant shows up to the court date
(interested party could potentially be defendant)
Scenario: Existing Case - has future hearing(s)
Given: I submitted a sign up request
And: My case number is in hearing data
And: I have at least one hearing date in the future
Then: I receive a text confirming I'm signed up for reminders on all hearings
Scenario: Existing Case - no future hearings
Given: I submitted a sign up request
And: My case number is in hearing data
And: I do not have a hearing date in the future
Then: I receive a text telling me there are no hearings to set up for reminders
Scenario: Non-Existent Case
Given: I submitted a sign up request
And: My case number is not in hearing data
Then: I receive a text saying case number not found
Open Questions
Need some kind of confirmation (what if case number isn't unique across counties?)
What other key scenarios are we missing?
The text was updated successfully, but these errors were encountered:
Here's what we have so far. This is in the project shared Twilio account - see message in #georgia-courtbot slack channel for instructions on how to get access
My memory and paraphrasing of Andrew's responses to my questions. The answers to the first three Qs are all "yes". In general, yes, we want to support these features at some point, but none of them would be targets for the initial release version. With the right system in place to scan for case date changes with enough notice, that situation could be accommodated.
(may need to split this out into a flow map w/ decision loops, but for now trying to do it as simpler features)
Open Questions
The text was updated successfully, but these errors were encountered: