Product
Solutions
Trust
ResourcesDocs
Live previewBook a demo

Help inbox

Students ask for help in their own words, and each request reaches the right staff with the right urgency.

Answered by
Your staff, always
Priority
Normal, urgent, crisis
Crisis
Pinned, responders alerted
Record
Full audit trail

Every request answered by your team

Every request is answered by someone on your team, which is what a nervous first question deserves.

Students pick a help category, try a suggested resource, then ask in their own words. Every request gets a priority, and crisis requests go straight to the top. Your staff reply in one thread the student can follow. Response targets show what's due and what's overdue. How staff triage requests.

From their words to the right person

Students write in their own words, and the right person picks it up.

  1. Students choose from your help categories, see a few resources worth trying first, then write what they need in their own words.

  2. Each request arrives with a priority. Crisis language pins it to the top and alerts your crisis responders.

  3. A staff member replies in the same thread. The student sees the whole conversation in one place and can reply by email.

  4. Response targets show what is due and overdue, and the timeline records every assignment, note and status change.

  • Only the staff in scope

    Only staff whose role includes the inbox, for the students they look after. Revealing contact details is audit-logged.

  • Every look is recorded

    Each time a staff member opens a student's record, it is written to a tamper-resistant audit log.

  • Never sold or mined

    We do not sell or mine student data. Every subprocessor is disclosed, and the data of record is hosted in Australia.

  • Their note stays out of email

    If you mirror requests to a help desk, the student’s own note is left out of the email.

Fits what you already run

  • Your help desk, mirrored

    Each request can open a ticket in any help desk with email-to-case, with per-category queues and a separate crisis queue.

  • Crisis alerts where your team is

    Optionally send crisis alerts to your Slack or Microsoft Teams channel, as well as by email.

  • Signed webhooks

    Signed events when a request is created, updated or resolved, sent to your HTTPS endpoint without message text.

FAQs

Can't see your question? Ask us and we'll reply.

Is the inbox answered by AI?

No. Your staff write every reply, and the writing assistant doesn't draft them. First Six only sets the priority and routes the request.

How are crisis or welfare requests handled?

If what a student types matches a crisis signal, they see immediate support straight away (000, Lifeline 13 11 14, Beyond Blue). The request is pinned as crisis and your crisis responders are emailed, plus Slack, Teams or your help desk if you connect them.

How fast are students answered?

That depends on your team. Each ticket tracks a first-response target: 30 minutes for crisis, 4 hours for urgent and 24 hours for normal, so anything ageing is obvious.

Can students see the status of their request?

Yes. Each student sees their whole conversation in one place, so they always know where their request is up to.

Who can see a student's help request?

Staff whose role includes the inbox, for the students in their scope. Revealing contact details is audit-logged, and a help-desk mirror leaves the student's own note out.

See the inbox at work

Follow a student's request from their own words to the staff member who answers it.