Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

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)

  • The USCT program has been set up, and its objectives and eligibility criteria have been defined.

  • The Ministry of Social Welfare or another leading agency/organization is responsible for organizing the information campaign.

  • Digital campaign communication channels (e.g., mobile messaging, emails) have been established and are available under Messaging BB.

  • All necessary building blocks and workflows have been set up.

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

  • Name

  • Description

  • Category

  • Host Entity ID

  • From

  • To

  • Deadline

  • Subscriber Limit

  • Terms

  • Status

  • Venue

Scheduler Resource

  • Name

  • Category

  • Phone

  • Email

  • Alert URL

  • Alert Preference

Scheduler Entity

  • category

  • name

  • phone

  • email

  • website

Scheduler Message

  • Entity Identifier

  • Category

  • Message content


Workflow Process

  • Name

  • Type

  • Version

  • Description

  • Process Body

    • code

    • value

Beneficiary

  • First Name 

  • Second Name 

  • DOB 

  • National ID Number 

  • Place of residence

  • Contact info:

    • Email 

    • Phone Number 

    • Address

  • Eligibility criteria [Data required for making decisions on enrollment, e.g. with using Proxy Means Test, can vary between countries]

    • number of children

    • marital status

    • type of settlement [town, village, etc.]

    • employment status

ACTORS 

Human

  • Leading Organization (Ministry of Social Welfare or other entity)

  • Target beneficiary group(s)

System 

  • Messaging BB

  • Scheduling BB

  • Consent BB

  • Identity BB

  • Registration BB

NORMAL COURSE 

Step 1: Setup outreach schedule for potential beneficiaries

Note: 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 Prepare outreach campaign content step).

Step 1.1: Create scheduler 

Feature: 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:

  • /event/new

    • Add new event

  • /message/new

    • Create content message event 

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 beneficiaries

Step 2.1 Prepare targeting workflow 

Feature: 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:

  • /data/{registryname}/{versionnumber}

    • Access the list of individuals for scoring.

Relevant Scheduler BB endpoints:

  • /event/list_details

    • Get information regarding about what event beneficiaries will be appointed to

Relevant Workflow BB endpoints:

  • /processes (post)

    • Create new workflow

Step 2.2 Execute targeting workflow

Feature: 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:

  • /resource/new

    • Save beneficiary in scheduler BB

  • /appointment/new

    • Bind potential beneficiary to the event 

Relevant Digital Registries BB endpoints:

  • /data/{registryname}/{versionnumber}

    • Query digital registry for target group

Relevant Consent BB endpoints:

  • /service/agreement/{agreementId}/

    • Confirm that potential beneficiary has signed the agreement and can be notified about the program

Relevant Workflow BB endpoints:

  • /processes/{processId}/start

    • Trigger appointment process

Step 2.3 Notify target group

Feature: Send bulk notifications  
Scenario: Scheduled event is triggered and messages are sent to target group
  Given Target Group was registered in the scheduler BB
    And Scheduler can trigger bulk message in messaging BB
    And Scheduler Alert had been scheduled
  When Alert is triggered
  Then Target group receives notifications through messaging BB
    And Scheduler sets marks action as successfull

Relevant Scheduler BB endpoints:

  • /alert_schedule/new

    • Used to setup trigger for notifying target group

Relevant Messaging BB endpoints:

  • /send/email/batch

    • Notify target group. At the moment that’s only available batch endpoint, should be extended when other notification methods are added.

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:

  1. Client Communication (covered)

  2. Client Education (not covered, no BBs specified at the moment)

  3. Content management (partially included in the existing step, no BB)

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)

  1. The target audience is aware of the USCT program and its objectives, benefits, constraints, timeline, etc.

  2. Potential beneficiaries are encouraged to enroll in the USCT program and they know how to do this.

  3. Relevant content has been created and managed for use in the information campaign.

EXCEPTIONS 

  1. Target audience doesn’t accept messages used to spread awareness

  2. Consent policy to use data to inform about social program has not been created

RELATED BBs

  • Messaging BB

  • Scheduling BB

  • Consent BB

  • Identity BB

  • Registration BB

SEQUENCE DIAGRAM

 Mermaid UML 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

  • No labels