Why this connection works differently
ASI FrontDesk is a long-established property management system still in use at a number of smaller independent motels, particularly older, single-location properties. It generally doesn't offer the kind of live, always-on API that newer cloud PMS platforms (Cloudbeds, Mews, Guesty) do, so a continuous background sync isn't something Suzy can honestly claim for it.
Instead, Suzy supports a CSV-based import: you export your upcoming reservations from ASI FrontDesk in the standard format, upload the file through your Suzy dashboard, and Suzy upserts each reservation, matching by confirmation number so re-uploading the same file doesn't create duplicates. You can also send a single reservation at a time if you'd rather not batch-export.
What this does, and doesn't, mean
Not a live sync
Honest limitationReservation data updates when you upload a new export, not continuously in the background the way Suzy's OAuth-based integrations do. A new booking made in ASI FrontDesk after your last upload won't appear in Suzy until you upload again.
Batch or single-record upload
Your choiceUpload up to 100 reservations at once from a CSV export, or send a single reservation if that fits your workflow better.
Safe to re-upload
No duplicatesRecords are matched by confirmation number, so uploading the same export twice updates existing records instead of creating duplicates.
Honest status
This is a real, working import path, not a live continuous sync, and we're direct about that difference rather than describing it the same way as an OAuth-based integration. Suzy works fully without importing anything from ASI FrontDesk at all; you can enter your property's WiFi, check-in/out times, and policies directly and Suzy answers guest questions the same way.