The support team's access to your account
Sometimes the fastest way to solve a problem on your account is for the support team to see exactly what you see: the activity that is not appearing, the payment link that will not work, the child's details that will not save. So Skool.Cool lets the support team open a support session on your account.
This page explains plainly how that session works, and why we think it is better than asking you for your password or your verification code.
The first rule: we will never ask you for your verification code
A support session needs nothing from you. No password, no verification code sent to your phone, and no screen sharing.
If anybody asks you for the verification code that reached your phone — they are not from Skool.Cool. The code is yours alone. Do not share it with anyone, including anyone who says they are from support or from the school.
Who can open a session on my account?
A very small number of accounts: Skool.Cool's central operations team only. It is not a permission available to every administrator at your school, and it is not granted automatically with any administrative role.
Before a session can be opened, the member of staff is required to write a clear reason for it. No session can be opened without a written reason.
We say it plainly: the system sends you no notification at the moment a support session is opened on your account, and your agreement is not asked for beforehand. What stands today is the written reason and the complete record, not a permission from you.
So if you would rather no session were opened on your account, say so in advance — see What if I would rather not? below — rather than waiting to be asked at the time. And you can always ask for the log of sessions afterwards.
What does the member of staff see?
They see your account as you see it: your children, their registrations, the payment status, the notifications and the profile. The point is for them to see the problem itself rather than trying to picture it from your description.
And there are things that cannot happen in a support session, by the way the system is built rather than by policy alone:
- Your way of signing in cannot be changed. Adding an email address, verifying one, or changing a password are all refused inside the session, because they touch the keys to your account.
- You cannot be signed out of your devices. A support session does not end your sessions on your phone.
- Nobody else can be given access to your children. Inviting an extra parent, or approving one's link, is refused inside the session. Removing existing access is allowed, because narrowing access is not the same as widening it.
- A full schedule clash for your child cannot be acknowledged. If every session of an activity clashes with another of your child's activities, acknowledging that is your decision, taken from your own account, and it is not accepted inside the session.
- The school's policy cannot be accepted on your behalf. The School policy step of registration is refused inside the session.
- The session is time-limited. It ends by itself, and the member of staff — or management — can end it at any moment, at which point it stops immediately.
Beyond these cases and others like them, inside the session the member of staff can do most of what you can do: edit a child's details, cancel a registration, or read a notification. We say so plainly, because pretending otherwise would be worse than saying it. And the safeguard here is not prevention but the record: every action is attributed to the member of staff by name, as the next section explains.
How do we make sure everything is recorded?
Every support session is recorded in full: who opened it, on which account, when, why — the reason they wrote — and from which network address. And every action taken inside the session is recorded in the name of the member of staff who took it, not in yours.
That is the essential point: if something in your account is changed during a support session, the record attributes the change to the member of staff, not to you. The record is kept, and cannot be edited or deleted.
How do I ask for the log of access to my account?
You have a right to know. Contact us through the contact page and we will give you the log of support sessions opened on your account, with each session's date and reason.
If you see a session in the log that you cannot find a convincing explanation for, tell us — we take that seriously.
What if I would rather not?
Tell the support team you would prefer no session to be opened on your account, and we will work on your problem by other means: your description, screenshots, and the administrative tools that act in the member of staff's own name from the outset. It may take longer, but it is your choice.