Does Jolly replace Deggy?

No. Your team keeps working in Deggy. Jolly reads the records Deggy keeps as the work happens, and campaigns pay out on those records, not on numbers people report at the end of the week.

Does Jolly write anything back to Deggy?

No. Every Jolly integration is read-only. Jolly reads the data a campaign needs and sends nothing back. Connecting Deggy changes no records, settings, or screens in it, and the people who use it every day keep working the same way.

How does a Deggy connection get set up?

Our team connects Deggy with yours during implementation, as part of the Jolly rollout. Tell us which other systems you run, including ones that aren't in our catalog yet and ones you plan to replace.

Do guards or officers need to change how they patrol or file incidents?

No. Officers keep logging checkpoints, tours, and incidents in Deggy. Jolly counts that activity toward the goal, and each officer follows their progress in the Jolly app.

Deggy

Deggy is a guard tour system that verifies checkpoint visits in real time, checks each scan for authenticity to rule out ghost patrols, and lets guards document incidents in the field with photo evidence.

Get a demo

What Jolly reads from Deggy

Checkpoint, badge, and activity events
Each checkpoint scan, badge read, or logged check, with its place and time, so patrol coverage can be tracked for each officer, post, or site.
Incident reports
Each incident, with its type, its time, and who reported or resolved it, so handling an incident counts for the guard who did the work.
Attribution to a person
Where a scan, incident, or access event records who was involved, a goal can be set for one guard or team member.