Country of Residence
Nigeria
Age
19
Project title
NoEcho
Project Summary: Describe your project in one sentence
NoEcho is a WhatsApp-first student service desk for Crawford University that gives every student a reference number, a response deadline, and a public accountability dashboard turning anonymous complaints into trackable civic records that institutions must respond to.
Website URL(s) or social media handles.
https://www.linkedin.com/in/heritage-oni-56135b321?utm_source=share_via&utm_content=profile&utm_medium=member_android
Project Category
My project is a brand new / emerging idea
Project Stage
Idea (We’re hoping to get started in the future)
Founding Story: What was the spark that led you to start your project? What was the "Aha!" moment that led you to get started and see the potential for this to succeed?
In April 2026, a Crawford University student named Eboma Raymond was expelled after raising complaints about campus conditions through unofficial channels. Heritage watched it unfold on the same campus where he studies and lives. What struck him was not just that the outcome was unjust. It was that there was no alternative path. No safe channel. No record that a concern had ever been raised. The only option available to students was a physical suggestion box in two locations on campus. The Vice-Chancellor's office holds the key. Nobody knew when it was opened. No student had ever received an acknowledgement. The moment the question formed, it would not go away: why does a university with five thousand students not have the most basic civic infrastructure, a way to raise a concern and have it taken seriously? Heritage's connection to the Student Representative Council meant he could see both sides of the problem. SRC members were carrying student complaints to authority desks informally and with no power to compel a response. That is what NoEcho is: the infrastructure that should have existed before Eboma Raymond had nowhere to turn.
The Problem: What problem are you helping to solve? Why does it matter to you and your community?
At Crawford University in Igbesa, Ogun State, students have two ways to raise a concern: speak to a senior official in person, or drop a note into one of two physical suggestion boxes on campus. Submissions are filtered before reaching anyone with authority to act. There is no acknowledgement, no reference number, no deadline, and no public record of what was raised or whether anything changed. The result is not silence. It is the louder, more damaging kind of noise that happens when silence becomes the only other option. The Eboma Raymond expulsion in April 2026 demonstrated what a broken feedback system costs: students lose trust, institutions lose credibility, and genuine problems go unresolved until they become crises. This is not a Crawford-specific failure. It is the default across Nigerian university governance. No structured channel. No anonymity protection. No obligation to respond. No accountability if nothing changes. The suggestion box is not a solution. It is the symbol of a system that was never designed to listen. Heritage lives on this campus. He knows which desks ignore requests, which issues have been raised and never resolved, and which students are afraid to speak because there is nowhere safe to do so.
Your Solution: How are you solving this problem? Share your specific solution.
NoEcho is a digital student service desk for Crawford University. A student sends a message to the NoEcho WhatsApp number, no app to download, no account to create. They describe their issue in their own words. NoEcho confirms what it understood, assigns a unique reference number (for example NCR-20261020-0042), and routes the submission to the right authority desk through the Student Representative Council. From that point, the submission moves through a structured system with accountability built in. The SRC reviews and assigns the ticket within one working day. The receiving authority desk has five days to respond before an automatic escalation begins. If a desk goes seven days without acting, the ticket escalates to the next authority level. After ten days with no resolution, the issue appears on the public accountability dashboard, the category, the age of the ticket, and the desk that has not responded with no student identifying information. Students track their submission by reference number through WhatsApp or the web portal. They see exactly where their ticket is and whether a response has been written. They never need to follow up in person or wonder if anyone read what they wrote. NoEcho handles three types of submissions: complaints and grievances (academic issues, welfare concerns, rights violations); facility and maintenance requests (broken infrastructure in hostels, classrooms, laboratories); and suggestions or policy ideas. The public dashboard shows aggregate statistics: resolution rates, response times, overdue counts, with no student names or personal details. The pressure falls entirely on the institution.
Impact: How has your project created impact / made a difference so far? Or, if at an early stage, what will impact look like?
NoEcho is currently at the design and build stage. The product architecture, database schema, escalation logic, WhatsApp submission flow, and public accountability dashboard have all been fully specified. The technology stack is selected and configured. The MVP build is in progress. The Crawford pilot will run with 30 to 50 students submitting real tickets before January 2027. The outcome framework is defined: we will measure the number of tickets submitted, what percentage were assigned within one working day, what percentage received a response within the five-day deadline, and how many escalated. We will document average time to resolution and publish the first dashboard data publicly. The longer-term impact is structural. Crawford University has approximately 5,000 enrolled students, none of whom currently have a safe, trackable channel for raising concerns. Every student who receives a reference number and a dated response has something no Crawford student has had before: evidence that the institution heard them. The architecture is open and fully documented for replication. Any student body at another Nigerian university should be able to adopt NoEcho for their institution. The long-term potential is a national student voice infrastructure layer across Nigerian higher education.
Your Innovation: What is different about your project compared to other programs or solutions already out there? How is your project new or innovative?
No Nigerian university currently operates a structured, anonymous, trackable student service desk with automatic escalation and a public accountability dashboard. The closest comparison is a physical suggestion box, which is passive, unacknowledged, and unaccountable. NoEcho is a fundamentally different kind of tool. Three things make it genuinely new in this context. First, the submission channel. Nigerian university students use WhatsApp daily. NoEcho meets them where they already are: no app download, no registration, no barrier to entry. A student can submit a complaint in under two minutes. The AI layer parses natural language into structured tickets, removing the form-filling friction that causes participation to collapse in most digital suggestion platforms. Second, the accountability architecture. The escalation clock and public dashboard change the incentive structure for university administrators without requiring confrontation. When a desk knows that an overdue ticket will become publicly visible, the institutional default shifts. Neglect becomes costly. Responsiveness becomes measurable. The SRC gains evidence for advocacy it has never had before. Third, the data layer. Every ticket that moves through NoEcho adds to a time-stamped, categorised record of which problems recur, which desks respond promptly, and where systemic failures concentrate. That record does not exist anywhere in Nigerian university governance today. It is useful not just for individual students but for researchers, civil society organisations, and regulators working on higher education accountability. NoEcho does not replace university authority. It makes what universities do with student voices visible.
How many people are on your team?
1
Your team: What role(s) do your team members play? How do you share leadership with them?
Heritage leads the project and manages all Crawford institutional relationships as SRC liaison. Two SRC members will operate the triage dashboard as ticket reviewers and routers. A technical advisor with software architecture experience designed the system and supports the build. Governance belongs entirely to the student team. The technical advisor has no role in platform decisions.
What’s Next: What are the next steps you plan to take to grow or strengthen your project over the next year? If your project is still in the idea stage, describe the steps you will take over the next three months to launch or begin developing it.
Over the next three months (to January 2027): Build the MVP using the coding scaffold already prepared. Test the WhatsApp submission flow using the Twilio sandbox. Onboard Heritage and two SRC members as the first triage operators on the dashboard. Run a closed beta at Crawford with 30 to 50 students submitting real tickets. Document outcomes, number of submissions, SRC assignment times, desk response rates, escalation counts, and time to resolution. Submit the Carnegie Challenge application with beta data by 31 January 2027. Over the following year (2027): Launch publicly at Crawford University with formal SRC endorsement and the first full public dashboard. Open-source the codebase and publish the deployment guide so other student bodies can replicate the model. Begin outreach to Student Representative Councils at two additional Nigerian universities. Pursue formal university administration partnership using the beta outcome data as evidence of value.
How do you encourage other people to join your project or learn about the problem you’re working on? If you have a new idea, tell us how you will do this in the future.
The core engagement strategy for NoEcho is making the problem visible through the students it affects, starting with the SRC. Heritage has direct relationships with SRC members at Crawford who already carry student complaints informally and want a better tool. Onboarding them as operators is the first act of engagement: SRC members who use the dashboard daily become the most credible advocates for the platform among their peers. When a student submits a ticket and receives a response with a reference number, they tell others. The reference number is the proof of concept. For the broader student body, the public accountability dashboard is the engagement mechanism. Students who see the dashboard, resolution rates, overdue tickets, which desks are responding, understand what the platform does without needing to be told. In the future, we plan to hold a brief SRC-hosted orientation at the start of each semester and share anonymised case studies showing how submissions led to real responses. The goal is for every Crawford student to know their reference number option before they ever need it.
