USCT-01-Outreach-Communication
USE CASE STEP | USE CASE: Unconditional Social Cash Transfer STEP: Outreach Communication |
PRECONDITIONS (list of conditions that MUST be met in order to be able to successfully execute this process) |
|
DATA INPUTS | Note: Details on Data Inputs will most likely depend on Building Blocks that are not yet available. For now high level inputs are listed. Scheduler Event
Scheduler Resource
Scheduler Entity
Scheduler Message
Beneficiary
|
ACTORS | Human
System
|
NORMAL COURSE | Step 1: Setup outreach schedule for potential beneficiariesNote: For now we assume that content of the scheduled massage is hard-coded. At the moment definition of Content Management BB is not determined, and therefore we’re sending message directly to the scheduler BB. This will be changed in next iterations (example use of using Content Management BB was presented added in previous version of this document under Step 1.1: Create schedulerFeature: Create scheduler event
Scenario: Setup outreach event in the scheduler
Given timeline of outreach program was determined
And Outreach channels were determined
And Social Welfare worker can schedule events
And Social Welfare worker has prepared content of the outreach
When Social Worker create new scheduler bb event
And Social Worker attaches event message
Then new scheduler event is created
And new scheduler message is created Relevant Scheduler BB endpoints:
Note: This assumes that only one event and message will be created. Should we assume that different outreach channels will require different events and messages? Step 2 Beneficiary targeting Identify target group of potential beneficiariesStep 2.1 Prepare targeting workflowFeature: Create new workflow
Scenario: Create workflow that adds beneficiary Scheduler BB resources using Digital Registry BB data
Given Social Worker can create workflows
And Workflow is connected to the Digital Registry BB
And Workflow is connected to the Scheduler BB
And Function/model to evaluate potential beneficiaries is ready
When Social Worker creates new workflow
Then New workflow is created
And Potential beneficiaries who meet the targeting criteria can be identified
Relevant Digital Registries BB endpoints:
Relevant Scheduler BB endpoints:
Relevant Workflow BB endpoints:
Step 2.2 Execute targeting workflowFeature: Schedule notifications for target group
Scenario: List potential beneficiaries for outreach
Given that a scheduler event has been created
And that a targeting workflow process exists
When the Social Worker triggers the workflow process
And the potential beneficiaries meet the criteria
And the potential beneficiaries have signed a consent agreement to be notified
Then the potential beneficiaries should be added as resources in the scheduler BB
And they should be associated with the previously created event
Relevant Scheduler BB endpoints:
Relevant Digital Registries BB endpoints:
Relevant Consent BB endpoints:
Relevant Workflow BB endpoints:
Step 2.3 Notify target groupRelevant Scheduler BB endpoints:
Relevant Messaging BB endpoints:
Current steps don't cover handling Outreach Campaign monitoring or assessing the effectiveness of the outreach campaign. Should we include these as indispensable parts of the use case step, or include outreach monitoring and assessment in a separate step (8. Ongoing M&E)? On the Figma chart, the Outreach Communication step is composed of three workflows:
Should we include Client Education and Content Management in the scope of this use case step or focus on the Client Communication workflow? |
ALTERNATIVE COURSE | TBA |
DATA OUTPUT |
|
POST-CONDITIONS (SUCCESS CRITERIA) |
|
EXCEPTIONS |
|
RELATED BBs |
|
SEQUENCE DIAGRAM | sequenceDiagram participant SW as Social Welfare Worker participant SBB as Scheduler BB participant WBB as Workflow BB participant DRBB as Digital Registries BB participant CBB as Consent BB participant MBB as Messaging BB activate SW SW->>SBB: Create scheduler event (/event/new) activate SBB SW->>SBB: Attach event message (/message/new) SBB-->>SW: Confirm scheduler event and message created deactivate SBB SW->>WBB: Create workflow (/processes (post)) activate WBB WBB-->>DRBB: Validate Digital Registry BB connection WBB-->>SBB: Validate Scheduler BB connection WBB->>SW: Confirm new workflow created SW->>WBB: Trigger workflow process (/processes/{processId}/start) deactivate SW WBB->>DRBB: Access list of individuals for targeting (/data/{registryname}/{versionnumber}) loop For each potential beneficiary WBB->>CBB: Check consent agreement (/service/agreement/{agreementId}/) alt Has signed agreement WBB->>SBB: Add beneficiary as resource (/resource/new) WBB->>SBB: Associate beneficiary with event (/appointment/new) end end WBB-->>SW: Inform about finished process deactivate WBB SW-->>SBB: Schedule alert for notifications (/alert_schedule/new) activate SBB SBB->>MBB: Trigger bulk message (/send/email/batch) activate MBB loop For each potential beneficiary MBB->>Beneficiary: Send notifications end MBB->>SBB: Confirm notifications sent deactivate MBB SBB-->>SW: Confirm outreach communication executed deactivate SBB
|