EdZola
Help desk & grievance systems

Every request gets an owner and a clock.

Volunteers, field teams, donors and the people you serve already write in. We set up the desk that answers them on time, on Zoho Desk: tickets with a priority and an owner, response times that run on your working calendar, and a grievance process you can show a funder or regulator. We start with one queue.

What breaks today

You already run a help desk. It just lives in the wrong place.

Most nonprofits we work with answer dozens of requests a week. The trouble isn’t effort. It’s that nobody can see what came in, who has it and what is late.

01 · SCATTERED INTAKE

Requests live in a WhatsApp group or one person’s inbox.

A volunteer’s question, a field coordinator’s stock-out and a donor’s receipt request all arrive in different places, and some never get an answer.

02 · NO CLOCK

Nothing has a deadline, so nobody knows what is late.

Without a priority and a due time, the loudest request wins. A wage complaint can sit for a week while a quick question gets three replies.

03 · ONE HEAD

The answers live in one person’s memory.

When that person goes on leave, the desk stops. Nobody else knows the fixes, the templates or the people to call.

See it working

Eight desks a nonprofit could run tomorrow.

Each screen pairs one audience with one Zoho Desk feature. Together they show how the same pieces (departments, SLAs, rules and a knowledge base) fit very different kinds of work.

01 · Volunteer support
Volunteer support queue in Zoho Desk: saved views put tickets due today first, each with the time left on its SLA

Views and SLA timers. What’s due today comes first, with the time left on every ticket.

02 · Field operations
Field operations ticket in Zoho Desk, auto-classified as critical with a private note asking a person to confirm

Auto-classification. A rule sets priority, district and owner, then asks a person to confirm.

03 · Beneficiary grievances
Grievance ticket moving through Blueprint stages in Zoho Desk, with required fields and an audit trail

Blueprint. Fixed stages, required fields before closure and an audit trail.

04 · Helpline call-backs
Helpline SLA settings in Zoho Desk with a 24x7 calendar and an escalation ladder

SLA and escalation. A 24x7 calendar and a ladder for call-backs that slip.

05 · WhatsApp intake
WhatsApp messages from field workers arriving as tickets in the Zoho Desk queue

Instant messaging. WhatsApp messages land in the same queue as email.

06 · Donor queries
Donor help centre with Answer Bot replying to a receipt question from the organisation’s own articles

Help centre and Answer Bot. Answers come only from your own articles.

07 · Staff HR and IT
Guided Conversations flow collecting a staff HR or IT request and creating a private ticket

Guided Conversations. A short chat asks the right questions and opens a private ticket.

08 · Programme reporting
Programme dashboard showing ticket volume, SLA breaches and happiness ratings

Dashboards. Volume, breaches and ratings your board can read.

09 · Your desk
1queue to start with. One audience, one address, one promise.
Who
The people who write in most
Where
Email, WhatsApp, web form or phone
How fast
Your SLA, on your calendar
Next
Add the next audience

Start small. Show us where requests land today.

Illustrative mockups with invented organisations, people and numbers. Not live partner records or product screenshots.

How a request moves

From the first message to a closed ticket, nobody re-types anything.

The only manual steps left are the ones that need judgement: confirming the priority, replying and deciding when it’s done.

  1. Arrives by email, WhatsApp, web form or phone
  2. Becomes a ticket with a priority and an owner
  3. The clock starts on your working calendar
  4. The reply draws on templates and the knowledge base
  5. Closure with a one-click rating
  6. Friday review of breaches and known issues
Desks we set up

Each audience gets its own department, address, hours and SLA.

A crisis line can’t share a Monday-to-Friday calendar with donor queries. These are the six desks we set up most often. The response times are examples to adapt, not rules.

Grievance redressal & feedback

Community members, often by phone or WhatsApp. Acknowledge in 24 hours, resolve in 7 days, with a fixed process and mandatory steps before closure, plus a monthly report for the board.

Volunteer support

Questions about shifts, onboarding and certificates. First response in one working day, an acknowledgement with a FAQ link, and tags by programme and city.

Staff & field operations

App issues, stock-outs, payment delays, leave and laptops. Blocked work in 4 hours, the rest in 2 days, routed by district and kept private by function.

Helpline & call-backs

Callers who need a referral or a call back. Urgent cases the same day, every day including holidays, on a 24x7 calendar with an on-call owner.

Donor & CSR queries

Receipts, tax certificates and utilisation reports. Receipts in 2 working days, a template for each document and a priority bump for institutional donors.

WhatsApp intake

For any team whose users don’t email. Messages join the same ticket queue; outbound messages need templates approved by WhatsApp first, and people opt in.

What we build

A desk that a stranger could run from day one.

The real test of a help desk is the week its owner is on leave. We set it up so the rules, the templates and the knowledge live in the system, not in one head.

01

Departments and addresses on your domain

One support address per audience, on your own domain, with replies going out from the same address so threads stay together.

02

SLAs on working hours and holidays

Timers that count your working hours, pause on your holiday list and move when someone changes the priority.

03

Intake rules and Blueprints

Rules that set priority, category and owner from the message, never overriding a person, and fixed stages for grievances.

04

Emails, templates and a knowledge base

An acknowledgement that asks for what you need, reply templates, internal articles that appear beside every ticket and, if you want one, a public help centre.

05

Links to the rest of your systems

Donors in Zoho CRM, staff in Zoho People, time in Zoho Projects and programme records in Zoho Creator, so a ticket knows who it’s about.

Built for sensitive requests

Grievances need privacy and proof of process.

A complaint about wages, safety or a service is not a support ticket like any other. The desk has to keep it private, collect only what it needs and show every step afterwards.

Restricted departments

Grievance, safeguarding and HR queues that only named people can open.

Forms that collect less

Web forms with only the fields you need, and a standing line asking people not to email ID numbers or bank details.

An audit trail by default

Who did what and when, on every ticket, ready for a funder, a board or a regulator.

Deadlines the rules set

India’s DPDP Rules ask organisations to answer grievances within a set period, UK fundraising charities are expected to publish a complaints procedure, and many funders ask for a grievance mechanism. The desk turns those into timers.

We set up the process and the system. Your legal or safeguarding lead decides the policy. For a wider look at personal data across your systems, see ZolaShield.

Reports your board can read

Service quality as a number, not an anecdote.

Once every request is a ticket, the report writes itself: volume by programme, SLAs met and breached, ratings from the people you served and the oldest open grievance. Logged time shows a funder what support actually costs.

01

Volume by programme and place

See which district or programme is suddenly flooding the desk.

02

Breaches and the oldest open grievance

The two numbers a board should see every month.

03

Happiness ratings

A one-click rating on every closed ticket, rolled up by desk.

How a project runs

What you get at each stage.

Every help desk follows the same ImpactOS stages and sign-off points, so you always know what is being decided, by whom, and what you will have at the end of it.

Costs and licences

Small to start, and priced per person who answers.

Zoho Desk has a free edition for very small teams, and paid editions are priced per agent per month. Registered nonprofits new to Zoho can apply for Zoho’s nonprofit credits before paying for licences. EdZola’s setup is billed separately, and eligible nonprofits can access subsidised delivery through the Built for Impact Programme.

Zoho for nonprofitsCheck Zoho’s nonprofit credits and editions →
Questions

What teams usually ask first.

If yours isn’t here, bring it to the first call. We’d rather answer it honestly than have it surface halfway through a build.

Can people raise a request without email?

Yes. Requests can come in by WhatsApp, a web form, a chat on your website or a phone call that an agent logs as a ticket. The clock starts either way.

Can a 24x7 helpline run beside an office-hours HR desk?

Yes. Each desk is its own department with its own calendar, holiday list and SLA, all in one Zoho Desk account.

How do we keep grievances confidential?

Grievances sit in a restricted department that only named people can open, intake forms collect only what is needed, and every action is recorded in an audit trail.

Does it work in Hindi, Tamil and other languages?

People can write in any language, and templates and help articles can be written in yours. Answer Bot and the help centre support many languages; we check yours during scoping.

Do we need Zoho One?

No. Zoho Desk works on its own. If you already use Zoho One, Desk is included and links to CRM, People and Projects more easily.

How long does the first queue take?

Our own partner desk took two days to set up, because the promise was already written in a contract. For a nonprofit, the first queue usually follows the one-page SLA we write together in Scope.

Does AI reply to people on its own?

Only if you choose it, and only from your own articles, through Answer Bot on a help centre or website. Agent replies are written or approved by a person.

Connected verticals

A help desk works best beside the records it answers about.

Tickets become more useful when they know the donor, the staff member or the programme they concern.

Start with one queue.

Bring the inbox, WhatsApp group or phone log where requests land today. We will show you which audience to start with, what the promise should be and what a first desk would take.

Show us where requests land today

EDZOLA NEWSLETTER

Hear more about the work, once a month.

Subscribe for practical ideas, field notes and updates from EdZola’s work with social-impact organisations.

A monthly email from EdZola. You can unsubscribe at any time.