Skip to content
Gallery
Product Management
Product Hub
Roadmap
Standup meeting
Decision Logs
OKRs
PRD
Document Templates
UX Improvements
Process Mapping
Subscription Issue Resolution
Data Requirements Across Collection Channels
Email Communications In Signal
Key Design Decisions
More
Share
Explore
Feature PRD Template

Signal Security Request Process Update

Purpose

The purpose of this document is to present a detailed description of the integration of the security response with emergency medical response. The security feature should include the “Pay as you go” service for the security response.

Objective

The objective of this release is to:
Allow users to request for security response without having a subscription plan.
Provide a wide array of security services to clients.
Implement the payment gateway for security requests.

Functionalities for release

The user should be able to select a security emergency request if they do not have a plan.
The user should be able to add a landmark when making a request.
The user should be able to make payment for a request when they are not subscribed to a plan.
User Stories
EPIC
FEATURE
USER STORY
1
Security Request Module
Security request button
As a user, I want to able to make a security emergency request so that I can get access to security personnel
Acceptance Criteria
When a user is on the signal app home page, they should be able to click on the emergency request button to create a security emergency request on the next screen.
The user should be able to click on the emergency request button.
After the user has selected an emergency request, the user should be able to select the category of the request (Security) if they have purchased a plan that has security cover or not.
2
​
Select emergency type.
As a user, I want to be able to select a security request type so that the security personnel can know the exact situation that I am in.
Acceptance Criteria
When a user has selected a security emergency, they should be able to select from a list of security emergency types on the next screen.
3
​
Input Location and landmark
As a user, I want to be able to input my location after creating a security request so that the security personnel can know my location
Acceptance Criteria
When a user has selected a security emergency, they should be able to input their location on the next screen
The system should automatically pick the users location
If the user is not satisfied with the selected location, they should have the option to input the accurate location before submitting the request.
The user should have an optional field to any landmarks in that location to allow the security team reach them faster
4
​
Select Responder Type
As a user, I want to be able to select the response that I require so that the security personnel can come to my help.
Acceptance Criteria
When a user has selected their location, they should be able to select a security response type on the next screen.
The system should display the responder types available for security.
ART
The user should be able to see the cost of the response (N20000)
The user should see a flutterwave link to make payment for the service.
The flutterwave link should be persistent until payment has been made.
5
​
Emergency Summary
As a user, I want to be able to see a summary of my request so that I can see my request details.
Acceptance Criteria
When a user has completed all option selections, they should be able to see the summary of their request.
After the user reviewed their request, they should be able to submit their request
6
​
​
​
7
​
​
​
There are no rows in this table
⁠
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.