User Technical Support in Rwanda

What is user technical support, and who needs it

It’s direct, patient help for individuals, mostly remote through screen sharing and sometimes at their desk. It covers application questions, sign-in and access problems, file sharing and permissions, email and calendar settings, meeting set-up and short guidance on doing things more efficiently. It suits organisations that have recently moved to Microsoft 365 or a new business system, and those with staff of very different confidence levels with technology.

The problem it solves

Application confusion is invisible in IT reports because it’s rarely reported. Staff email files instead of sharing links because they’re unsure how, keep five versions of a document, avoid Teams meetings because the audio failed once, or spend twenty minutes on something that takes one. Multiplied across an organisation, that’s a large hidden cost. Accessible, friendly support removes it, and staff end up using the tools you already pay for.

Where the time actually goes

Sign-in and access. New phones and multi-factor authentication, forgotten passwords, access to shared mailboxes and folders.

Files and sharing. Finding files in OneDrive, SharePoint and Teams, sharing safely with outsiders, recovering previous versions.

Email and calendars. Rules, delegates, shared calendars, signatures and out-of-office replies.

Meetings. Audio and camera settings, screen sharing, recording and running meetings with external participants.

Office applications. Excel formulas and tables, Word formatting and templates, PowerPoint basics.

Business systems. User-level questions in accounting, HR or sector systems, with deeper issues passed to the vendor along with the details they need to fix them quickly.

Turning answers into lasting help

Every question answered once is a question that may be asked again. So recurring questions become short written guides or one-minute screen recordings, stored where staff can find them. Teams with the same difficulty get a short group session. Monthly reports show which topics come up most, which often points to a setting worth changing for everyone or a short training need. Over time, the same questions stop coming in, and staff who were once hesitant start helping colleagues themselves.

What the work involves

1. Agree scope: which applications and systems are covered, and how staff ask for help.
2. Learn your setup: shared mailboxes, team sites, business systems and their quirks.
3. Support staff remotely or at their desks, with permission for every remote session.
4. Write guides for recurring questions.
5. Review monthly to spot topics needing a session or a settings change.

What’s included and what’s not

Typical timelines and what drives cost

Most questions are resolved in a single session of a few minutes to half an hour. User support is usually part of a helpdesk or managed support agreement, priced by user count, rather than billed per question. Cost rises with the number of applications covered, coverage hours and the amount of desk-side support needed.

Equipment typically used

Secure screen-sharing tools that need the user’s consent, the Microsoft 365 admin centres for account and access issues, a shared knowledge base for written guides, and short screen recordings for common tasks.

Common mistakes we see

Staff told to raise a ticket for every small question, so they stop asking. Support scoped only to hardware and networks. Multi-factor authentication rolled out with no help for people changing phones. The same question answered every week without a guide. And new systems launched with no plan for the questions that follow.