Don’t see your system? Most tools with an API can be connected through aidotz. We’ll confirm on the discovery call.
You do not need to connect everything at once. Most schools start with the one system the agent would otherwise ask staff to look up, such as the learning platform or the student information system. A single, well-tested connection is easier to trust than five half-finished ones. On the discovery call we ask which systems hold the records your team checks most and who administers them. That person matters, because access is granted from your side.
Several of the tools listed here overlap. A school may use Canvas for courses, PowerSchool for records and Teams for staff chat. An agent does not need all three on day one. We pick the smallest set that lets it do the job well, and add others once your team trusts how the first one behaves.
The steps are similar across tools, though each system has its own rules and permissions. We begin by agreeing what the agent should read and what, if anything, it may change. Your administrator then grants access from your side. We test with realistic scenarios, and every action the agent takes is logged so your team can review it afterwards.
Some systems have no API, limit what outside tools can do or restrict access under your own policies. In those cases we say so early and look at alternatives, such as a scheduled export or a staff approval step. Connection details are confirmed on the discovery call, not assumed. If a tool is missing from the list, ask. Most tools with an API can be connected, but we confirm case by case.