Notifications & auto-checkout

Calliyo runs two pieces of “background work” on your phone: follow-up reminders (notifications) and automatic checkout at the end of your day. Both rely on Android’s alarm system. Both can be sabotaged by aggressive battery savers.

Follow-up reminders

When you schedule a follow-up for “today at 3:00 PM”, Calliyo registers two alarms:

• A 5-minute pre-call notification (fires at 2:55 PM).
• A 30-second pre-call notification (fires at 2:59:30 PM).

Both notifications show:

• Title — the lead’s name.
• Body — “Followup call”.

Tap a notification to jump straight to Today’s follow-ups with the lead in focus.

Enabling

Settings tab → Notifications toggle.

When you turn it on:

• On Android 13+, Android prompts for the POST_NOTIFICATIONS permission. Tap Allow.
• On Android 12+, Calliyo also needs SCHEDULE_EXACT_ALARM for the notifications to fire on the exact minute. The app asks Android to grant this; some manufacturers (especially Xiaomi, Oppo) hide the toggle deep in Settings — see Troubleshooting.

Why a notification didn’t fire

In rough order of likelihood:

1. Notifications toggle is off in the Settings tab.
2. Android’s notification permission is denied for Calliyo (Settings → Apps → Calliyo → Notifications).
3. Battery saver killed the alarm. Most non-stock Android OEMs ship with “battery optimisation” on by default for non-system apps — killing background alarms after a few hours of inactivity. Set Calliyo to Don’t optimise / No restrictions.
4. Scheduled time was in the past when the screen loaded. Calliyo skips scheduling alarms whose time has already passed.
5. You opened a fresh follow-ups list that re-scheduled alarms; if you opened it again after the original window passed, the alarms have been cancelled.

A quick test

To check notifications work without waiting:

1. Open the web app.
2. Schedule a follow-up for 3 minutes from now.
3. Open the mobile app’s Today’s follow-ups screen.
4. Wait 2½ minutes. You should see “Calling [Name] in 30 seconds…”

If you don’t, walk through the list above.

Auto-checkout

Every day at 11:59 PM (your phone’s local time), Calliyo:

1. Sends POST /agents/attendance/checkout to the server.
2. Clears your local “checked in” flag.

Result: when you open Calliyo the next morning, you’ll see the Attendance screen and need to check in fresh.

Why this exists

• It prevents stale shifts that span calendar days from messing up your team’s attendance reports.
• It ensures that any work done after midnight is consciously started with a check-in, not accidentally counted on yesterday’s shift.

What you’ll see

Nothing in the foreground — auto-checkout is silent.

If you happen to have Calliyo open at 11:59 PM, you’ll notice the next navigation jumps to Attendance.

Disabling

You can’t, from inside Calliyo. If your team genuinely needs cross-day shifts, ask your admin to raise this with support — the rollout uses a per-company flag on the server side.

Boot-time re-registration

When your phone reboots, Android forgets all alarms. Calliyo’s BootReceiver re-registers them on the next boot — so notifications and auto-checkout keep working.

For this to work, Android must allow Calliyo to autostart / run at startup. Most phones honour this for apps you’ve used recently; some (looking at you, Xiaomi) require manual opt-in:

Settings → Apps → Manage apps → Calliyo → Autostart → Enable.