SMS, IVR, and USSD let conservancy members send and request information through one central repository—the same data store behind the Public Dashboard. Use the tabs to compare channels, follow the process steps, and review warning signals fed into governance views.
Community members use SMS/IVR or USSD to send and request data. Both channels connect to the same central repository; the Public Dashboard is the front-end for viewing and analysis.
Aim: transparency and bidirectional communication
CarbonWatch gives conservancy members easier ways to access data about their conservancies—including carbon activities, payments, and grievance status—and to send reports and feedback. The centralized repository keeps communication with conservancy members bidirectional: members can request information and submit data through the same channels.
How each channel works
The Public Dashboard is the front-end of the repository: it displays the data stored in the central repo so that transparency is visible to all. All inputs and responses from SMS, IVR, and USSD are stored in the same centralized repository.
Community members receive alerts and can reply via SMS or IVR. Use the mockup below to see how messages appear in English or Kiswahili.
Community members receive short codes and can reply to check payment status, report issues, or request information. Messages are logged and can trigger follow-up.
Phone-based menu for those who prefer or only have voice access. Callers can select options for carbon updates, complaints, or general conservancy information.
Members send SMS, use IVR, or use USSD to report issues, request data (e.g. payment status), or voice perspectives. Inputs are timestamped and linked to conservancy where possible.
Implementing agencies (e.g. conservancy managers, project partners) log each input and route to the right team. Data feeds the central repository. Response time and outcome are tracked for transparency.
Community receives confirmation and, where appropriate, a direct response. Recurring or serious issues feed into warning signs and action prompts on the dashboard.
Carbon modules and updates can be sent via SMS/IVR or requested via USSD. The Public Dashboard (front-end interface for data description and analysis) shows issue counts, response times, and education reach where disclosed.
Community Interface feeds into governance signals. Watch for:
For details on how to report or escalate, contact your conservancy board. CarbonWatch does not replace official channels—it makes community voice visible and response accountable.
Community Interface should feed governance action, not just data.
USSD uses a short code on any feature phone—no mobile data—to query the same central repository that powers the Public Dashboard. Below: gateway path, sample menu, and what happens when a member dials.
Community members dial a short code (for example *123*44#) on any feature phone. The request is routed through the USSD gateway to the CarbonWatch application server, which queries the central repository and returns a short text response.
USSD works on basic feature phones and does not require mobile data. This makes it ideal for conservancies where connectivity is limited but GSM coverage exists.
The USSD service talks to the same central repository used by the Public Dashboard:
After dialling the short code (e.g. *123*44#), the user sees this main menu on their phone. No internet is required—only network signal.
Below are mockups of the screens the user sees when they choose each option. Each path leads to a request from the central repository.
After the user selects an option and any required code or ID, the system fetches data from the central repository and sends a short text reply to the phone.
Example reply for "Last carbon payment" after the user entered their conservancy code. Data source: CarbonWatch dashboard.