Two ways in
Crescove for iOS is the first-party native application. A browser-based field surface is available on the control plane for crews on other devices. Both talk to the same API with the same server-side authorization.
Technician app
Everything the visit needs, signal or not.
Technicians get the day's visits, the property, the contacts, the access details, the checklist, photos, notes, and time tracking. Work done without a connection is queued and sent when there is one.
Offline writes that survive
Status changes, notes, checklist responses, and time entries queue locally, survive the application being closed, and replay in order.
- Each queued operation carries an idempotency key, so a retry cannot double-apply
- Operations replay in a deterministic order rather than whichever finishes first
- A conflict stays visible for review instead of being discarded
Conflicts, not silent overwrites
If the server has already moved a visit on, the queued write is rejected as a conflict and shown to the technician. A phone that was in a basement for an hour does not get to undo the office.
Photos from the field
Photos upload to private storage through short-lived, tenant-scoped credentials. The application never holds storage credentials, and nothing is written to a public bucket.
Built for outdoors and one hand
Large targets, Dynamic Type, VoiceOver labels, dark mode, and reduced-motion support. Critical arrival and status information is not buried behind a menu.
Sign-out clears sensitive state
Signing out removes credentials from the Keychain and clears cached tenant data. Access codes are never persisted offline at all.
See Field Service & CRM against your own workflow.
Tell us how your business runs today and we will walk through what is available now, what is still being built, and what would need to be connected for you.