An education and workforce-training nonprofit may use Microsoft 365, a learning-management system, student databases, assessment tools, scheduling platforms and several funder portals.
Employees depend on these systems every day. Yet practical instructions are often scattered across old training documents, email threads, screenshots, Teams messages and the memory of one technically capable employee.
When someone forgets how to enroll an instructor, locate an attendance report or request access to a shared folder, they contact that person.
The result is an informal help desk that consumes staff time without solving the underlying problem.
Maisy can give employees one place to ask routine technology questions and find approved internal guidance.
The Accidental Technology Support Department
Consider a workforce-training nonprofit with 45 employees delivering classes at three locations.
The organization has one technology manager, but most daily questions go to an operations coordinator who knows how everything works.
Employees ask her:
- Where is the current class-roster template?
- How do I give a new instructor access to Teams?
- Which system contains the official attendance record?
- How do I correct a student’s training status?
- Where do I submit a software request?
- Which report should be sent to the funder?
- Who approves access to participant information?
None of these questions is especially difficult. The problem is volume.
The coordinator stops her work, searches for instructions, explains the process and often sends a link or document. A week later, another employee asks the same question.
Why Technology Questions Keep Repeating
Technology support problems often persist because the nonprofit has not separated three different needs.
The first is a technical incident. A system is unavailable, an account is locked or an integration has failed. That issue belongs with IT or the software vendor.
The second is training. An employee does not understand how to perform a task.
The third is organizational guidance. The employee knows how the software works but does not know which process the nonprofit expects them to follow.
For example, a learning-management system may allow an instructor to edit completion records. The software documentation explains which buttons to press. The nonprofit must still define:
- Who is authorized to make the correction
- What evidence is required
- Who reviews the change
- Which record is authoritative
- When a supervisor must be involved
TechSoup recommends providing documentation and on-demand training employees can return to when they need a refresher or when new employees and volunteers are onboarded. (blog.techsoup.org)
What Maisy Can Provide
Maisy can organize approved technology guidance stored in SharePoint and make it searchable through a conversational interface.
An employee might ask:
“How do I correct a student’s attendance record?”
Maisy could provide the approved procedure:
- Confirm the attendance documentation.
- Submit the correction request to the program manager.
- Do not overwrite the original record without approval.
- Make the approved correction in the learning-management system.
- Contact technology support if the system prevents the update.
The learning-management system remains authoritative for the student’s record. Maisy explains the process surrounding that record.
Useful knowledge may include:
- System-access procedures
- Password-reset instructions
- Approved software lists
- Training guides
- Reporting instructions
- Data-entry standards
- Technology request procedures
- Troubleshooting steps
- System ownership
- Escalation contacts
- Cybersecurity guidance
What Maisy Should Not Replace
Maisy is not a remote support technician.
It does not replace:
- IT administrators
- Software vendors
- Cybersecurity professionals
- Learning-management systems
- Student databases
- Help-desk platforms
- Human review
If a system is offline or an account has been compromised, the employee still needs technical support.
Maisy can help identify the correct response:
“Stop using the account and contact the technology manager through the security incident process.”
It should not attempt to diagnose every technical problem or provide unsupported fixes.
Permissions Must Be Reviewed
Technology instructions sometimes contain sensitive information.
General employees may need instructions for requesting access. They should not receive administrative passwords, security configurations or instructions intended only for system administrators.
Microsoft documents that Copilot Studio can use SharePoint as a knowledge source while authenticating users through their Microsoft credentials. The agent does not grant additional SharePoint access beyond what the employee already has. (Microsoft Learn)
That protection depends on the existing permissions being correct.
Before launch, the nonprofit should separate:
- General user instructions
- Manager procedures
- Technology-administrator documentation
- Security information
- Vendor contracts
- Credentials and secrets
NIST defines least privilege as limiting access to the minimum needed to perform assigned work. (NIST Computer Security Resource Center) Maisy should follow that same principle.
A Practical Starting Point
Begin with the 20 technology questions employees ask most often.
For each question:
- Identify the approved answer.
- Confirm which system is authoritative.
- Assign a content owner.
- Remove outdated instructions.
- Organize the guidance in SharePoint.
- Review permissions.
- Test the question in Maisy.
- Define when the employee should contact a person.
This creates a focused first use case without attempting to document every system at once.
Reduce Interruptions Without Reducing Support
Maisy helps nonprofit employees find approved technology procedures, system instructions and escalation guidance without replacing IT staff or operational software.
Pixeldust begins with discovery: identifying repeated questions, locating authoritative instructions, organizing them in SharePoint and determining which employees should have access.
The result is not fewer people receiving support. It is fewer routine questions consuming the time of employees who should be solving more important problems.
