LiveLoop · Calendar Sync
Your timetable made
the meeting link.
Two-way sync with Google Calendar and Outlook is the easy part. The hard part — and what makes LiveLoop different — is that we also sync with school, college, and coaching timetables. Period 2 Chemistry becomes the meeting link, automatically.
Recurring meetings get one permanent URL for the whole term. Edit the series, edit one occurrence — the link doesn't break.
LiveLoop Calendar Sync connects LiveLoop video sessions to three calendar systems with bi-directional sync: Google Calendar, Microsoft Outlook (and Exchange), and the Databus ERP timetable stack — SchoolDeck (K-12), CampusAlly (college), TutorDesk (coaching). Recurring meetings get one permanent join URL. Included in the LiveLoop per-host licence at no add-on fee. Built in Chennai.
All four sessions on one LiveLoop dashboard. One click joins each — no app switching.
One setup, then the term runs itself
From "open SchoolDeck on Monday" to "attendance for week 12"
How Mrs. Iyer's Class 9-B Chemistry sessions run for an entire term — without her ever creating a meeting link.
School's academic coordinator finalises the term timetable in SchoolDeck. Class 9-B Chemistry is Period 2 on Mon/Wed/Fri, 9:00–9:48 AM, 36 sessions total across the term.
LiveLoop reads the timetable. Generates one permanent join URL for the Class 9-B Chemistry series. Pushes the event to Mrs. Iyer's Google Calendar, to the 32 students' parent-app calendars, and to the parents' Google Calendars if connected.
10 minutes before class. Email + push reminder fires to Mrs. Iyer and to 32 students. She clicks the link in her Google Calendar entry — already in her browser tab from the morning's quick check.
Class starts. Students join from the same URL — one click in their parent app or calendar. Attendance starts marking automatically. While she's in the call, her Google Calendar shows "Busy" — the HOD doesn't ping her for a 9:15 question.
Class ends. Attendance writes back to SchoolDeck's student record. Recording attaches to the period entry. AI summary lands in Mrs. Iyer's email and in the academic head's SchoolDeck dashboard.
A school holiday is added in SchoolDeck. The Wednesday Chemistry session is auto-cancelled in the timetable. The event disappears from all 32 students' calendars within seconds. The permanent join URL still works for the other 35 sessions in the series.
Mrs. Iyer needs to swap Friday's session to Saturday for that week only. She edits just one occurrence in SchoolDeck. The Saturday slot is created, Friday's slot is removed; the join URL still works; the other 33 sessions are untouched.
35 of 36 sessions completed (one was cancelled). Attendance for every session is in SchoolDeck. Recordings are linked per period. Mrs. Iyer manually created zero meeting links. She started zero sessions from a "create meeting" button — every session started from her timetable.
What's not happening here: nobody is copying Zoom links into WhatsApp groups every morning. Nobody is "send me the link please miss" texting. Nobody is reconciling attendance from a CSV the next day. The timetable IS the calendar IS the meeting link.
Inside the calendar layer
Three integration types. One unified day.
Three calendar systems, one sync engine
Personal calendar, work calendar, institution timetable — all flow into the same LiveLoop dashboard.
📅 Google Calendar
Two-way sync with personal Gmail accounts and Google Workspace.
- Scope: calendar event read/write only — no Gmail, no Drive
- Recurring: series and single-occurrence edits both supported
- Status: auto-set "Busy" while in a LiveLoop call
📧 Microsoft Outlook
Two-way sync with Microsoft 365 (web + desktop) and Exchange.
- Coverage: Outlook.com, M365, Exchange Online, on-prem Exchange
- Permissions: calendar events only — no inbox access
- Meeting injection: join link auto-added to the location field
🏫 Databus ERP timetables
Native — not "via Google Calendar". The differentiator vs Zoom and Meet.
- SchoolDeck: K-12 timetable → period-level video sessions
- CampusAlly: college lecture schedule → guest lecture links
- TutorDesk: coaching batch schedule → recurring batch sessions
Recurring meetings done right
Term-long classes, daily standups, weekly coaching batches — one link for everything.
The forever link
One join URL covers the whole series — set up once, runs all term.
- Same URL: session 1 and session 36 use the same link
- Series edits: move all Wednesdays to Thursdays — link stays valid
- Single-instance edits: skip this Friday only — other 35 unaffected
RSVP + status visibility
See who's coming before you join.
- RSVP: accepted / declined / tentative shown in the lobby
- Busy mapping: calendar shows "Busy" automatically when you're in a session
- Multi-calendar: connect work + personal; conflicts checked across both
Reminders, timezones, and entry
Reduce no-shows for the parent on the other side. Reduce calculation errors for the host who travels.
Pre-meeting reminders
Email + push, configurable per series. Defaults are sensible; customise if you need.
- Default: 1 hour and 10 minutes before
- Custom per series: add a 24-hour reminder for board meetings; remove it for daily standups
- Channels: email + LiveLoop mobile push notification
Timezone & one-click join
No timezone math. No "is the meeting at 7 AM your time or mine?"
- Auto-conversion: 9 AM IST shows as the right local time for every invitee
- Storage: UTC base time, rendered per participant — matches Google's model
- Calendar-to-call: click the link in the invite, you're in — no LiveLoop account needed
LiveLoop calendar vs Zoom & Meet calendar plugins
Where the integration depth shows up
Most platforms sync to Google or Outlook. None of them sync to your school timetable.
| What you'll notice | LiveLoop calendar sync | Zoom / Meet / Teams calendar plugins |
|---|---|---|
| Google Calendar sync direction | Two-way. | Two-way for paid plans; one-way for free. |
| Outlook + Microsoft 365 sync | Two-way. Web + desktop + Exchange. | Two-way. Microsoft 365 paid required. |
| School ERP timetable integration | Native — SchoolDeck, CampusAlly, TutorDesk. | None. CSV import at best. |
| Recurring meeting URL stability | One URL for the whole series. | One URL — but breaks if you edit series in some flows. |
| Attendance writes back to SIS/ERP | Automatic to SchoolDeck/CampusAlly/TutorDesk. | CSV export. Teacher reconciles manually. |
| Multi-calendar conflict checking | Yes — work + personal in one view. | Usually one calendar per account. |
| OAuth scope requested | Calendar events only. | Varies — some request mail + contacts too. |
| Calendly compatibility | Paste LiveLoop link as Calendly location. | Yes (same way). |
| Cost of the calendar feature | Included in per-host licence. | Often requires paid tier. |
Six concrete scenarios across four audiences
Where calendar sync earns its keep
🏫 K-12 class periods via SchoolDeck
Term timetable in SchoolDeck → LiveLoop links auto-generated per period for every section, every day. Teachers start each class from the timetable view. Attendance writes back automatically.
🎓 College lectures via CampusAlly
Lecture schedule in CampusAlly → LiveLoop links per lecture slot. Guest lecturers join the same way faculty do — one click in their Google Calendar entry. Attendance flows back for NAAC records.
📚 Coaching batches via TutorDesk
Recurring JEE / NEET / UPSC / banking batches in TutorDesk → one permanent LiveLoop link per batch. Students get it in their TutorDesk app calendar. Attendance writes back to the batch register.
🏫 Parent-teacher meeting bookings
Teacher's Google Calendar shows 15-minute PTM slots. Parents book a slot — the LiveLoop link is in the calendar event. Browser-only join means the parent doesn't have to install anything.
💼 Team standups & client demos
Daily team standup → recurring Google Calendar event with a single LiveLoop link. Client demo → one-off Outlook event with LiveLoop link injected. Both work the same way for the participant.
🌍 Cross-timezone college guest lectures
A guest lecturer in London joins a Chennai college's CampusAlly-scheduled session. The same UTC base time becomes 9:00 AM IST for students and 4:30 AM... or moves the lecture to a sensible UK time. Math is the system's job.
What this page owns, what it doesn't
Calendar Sync ≠ Webinar Registration ≠ Instant Join ≠ SchoolDeck Timetable
Five nearby pages, five owned jobs. Calendar sync is the layer that ties them together.
This page — /features/calendar/
Owns the calendar integration mechanism: Google + Outlook + Databus ERP timetable sync, recurring URLs, reminders, RSVP, timezone handling.
/features/webinars/
Owns webinar registration. Calendar sync schedules the webinar; the webinar page owns what happens at the event — Q&A, polls, one-way broadcast for hundreds.
/features/instant-join/
Owns the one-click join experience. Calendar sync puts the join link in the invite; instant-join is what happens when a guest clicks it (no app, no account).
/features/security/
Owns encryption and host controls. OAuth scope details for calendar access also discussed here.
/schooldeck/features/auto-timetable/
The SchoolDeck side of the integration — how the school builds the timetable that LiveLoop then reads. This page describes LiveLoop reading it; that page describes SchoolDeck building it.
/schooldeck/features/virtual-classroom/
The SchoolDeck-side virtual classroom feature. Same integration viewed from the school buyer's perspective. LiveLoop is the engine; SchoolDeck Virtual Classroom is the surface.
Frequently asked questions
Ten questions about LiveLoop calendar sync
Which calendar systems does LiveLoop sync with?
Three. First, Google Calendar — two-way sync with personal and Google Workspace calendars. Second, Microsoft Outlook — two-way sync covering Microsoft 365 (web and desktop) and on-premises Exchange backends. Third, the Databus ERP timetable stack: SchoolDeck for K-12 schools, CampusAlly for colleges, and TutorDesk for coaching centres. The third one is the differentiator — generic meeting tools sync to Google and Outlook; only LiveLoop has native timetable integration with Indian school, college, and coaching ERP systems.
What does "bi-directional sync" actually mean here?
Two-way propagation. If you schedule a meeting inside LiveLoop, it appears on your connected Google Calendar or Outlook with a working join link in the location field. If you move or delete the event in Google or Outlook, LiveLoop reflects the change within seconds — the meeting room moves with the calendar event, you don't end up with a dangling LiveLoop session at the old time. The same applies for SchoolDeck/CampusAlly/TutorDesk timetable edits.
How do recurring meetings work?
Set up the series once — a daily standup, a weekly Class 10-A English period, a term-long bootcamp. LiveLoop generates a single permanent join URL that works for every occurrence in the series. Editing the entire series (move all Wednesday classes to Thursdays) keeps the link valid. Editing one occurrence (skip this Friday's session) also keeps it valid. The link does not break or rotate.
Does LiveLoop integrate with SchoolDeck or CampusAlly timetables?
Yes. When SchoolDeck or CampusAlly has a timetable entry — e.g., "Class 9-B Chemistry, Tuesday 10:00 AM, 60 minutes" — LiveLoop auto-generates the join link for that period. The teacher clicks Start Session from the timetable view inside SchoolDeck; no separate scheduling step. After the session, attendance writes back to the student record, the recording attaches to the period entry, and the AI session summary lands in the academic head's email. This integration is what makes LiveLoop's calendar feature different from Zoom's — Zoom syncs to your personal calendar; LiveLoop syncs to your institution's timetable. See the SchoolDeck auto-timetable page for the SchoolDeck side.
Can I connect multiple calendars at once?
Yes. Connect a work calendar (Outlook) and a personal calendar (Google) together — LiveLoop checks both for conflicts before showing you as available. For institutional users, you can also connect a personal calendar alongside the SchoolDeck or CampusAlly timetable so that meetings outside class hours show up in the same unified day view.
What permissions does LiveLoop request from Google or Outlook?
Minimum scope — calendar events only. LiveLoop reads and writes calendar event data: title, time, attendees, location, description, recurrence. We do not request access to your email inbox, contact list, Drive files, or other Google / Microsoft services. This is enforced at the OAuth scope level — Google or Microsoft will only grant us calendar read/write tokens. You can revoke access at any time from your Google account settings or your Microsoft account security panel.
How do pre-meeting reminders work?
Automated email reminders fire at configurable times before the session — typical defaults are 1 hour before and 10 minutes before. If invitees use the LiveLoop mobile interface, push notifications fire at the same times. Reminders can be configured per meeting series — a Class 10-A daily class might need only the 10-minute reminder, while a quarterly board meeting might need a 24-hour, 1-hour, and 10-minute cascade.
How does LiveLoop handle different time zones?
Each participant sees the meeting time in their local time zone. A LiveLoop session scheduled in IST automatically appears as the correct local time for an invitee in London (UK), Singapore (SGT), or Dubai (GST). The host doesn't do timezone math; neither does the invitee. The base time is stored in UTC internally and rendered per-participant — same model Google Calendar uses, so the two systems stay in agreement.
How does the join experience work from a calendar invite?
When LiveLoop creates the calendar event, it injects the join URL into the event's location field. Invitees click the link from their Google Calendar or Outlook event and land directly in the LiveLoop session — no LiveLoop account required for guests, no app download. This pairs with LiveLoop's instant-join feature: one click in the calendar invite, one camera/mic permission prompt, you're in. For schools, this is why parents actually attend PTMs — the link is already in their calendar from the school's invite.
Does the calendar sync feature cost extra?
No. Calendar sync — including Google, Outlook, and the Databus ERP timetable integrations — is included in every LiveLoop per-host licence at no add-on fee, starting at ₹499 per host per month. Higher tiers add capacity (more concurrent sessions, longer recording retention) — not access to the calendar feature itself. See the pricing page for the full tier breakdown.
Related LiveLoop pages
Calendar-adjacent features
Core LiveLoop pages
ERPs LiveLoop reads timetables from
Use cases helped most by calendar sync
Calendar sync · Included in every plan
Connect once.
Schedule for a whole term.
The free demo wires LiveLoop into your existing Google, Outlook, or SchoolDeck setup — and shows your real timetable becoming real meeting links.
From ₹499/host/month · Google + Outlook + ERP timetable sync included · No add-on fees