It goes back where it came from

It goes back into the system that asked for the meeting

Automatically, as well as exporting — so nobody reconciles two lists a week later.

What it is

When the meeting is finished and the register is settled, the result is sent to whatever asked for the meeting in the first place. Your own software is told the same way, over a signed webhook that retries.

It also exports, for the times somebody wants a file.

Why automatically matters

Attendance that has to be exported and imported is attendance that is a week old and occasionally wrong. The work is not the typing; it is the reconciling when the two lists disagree.

Read next

  • Present, late or absent — by your rule

    Your organisation decides what late means and what counts as attending. The arithmetic behind every verdict is printed next to it.

  • Webhooks

    Meeting started, meeting ended, attendance settled, recording ready — signed, retried, and dead-lettered rather than dropped.

  • It plugs into the system you already run

    From your timetable, your learning platform, or your own software — with the right people already invited, and what happened sent back.

Everything it does

Want to see this working?

Tell us what you are trying to do with it and we will show you that, rather than a tour of everything else.

info@seeuall.com
    It goes back where it came from — SeeUAll · SeeUAll