Check In on Arrival in Canary

Today, Canary Technologies is only usable if the guest initiates and completes the workflow.

If they don’t:

• Front desk cannot complete ID or CC tasks inside Canary
• Staff must capture data elsewhere (PMS, terminal, notes, email, etc.)
• Canary becomes optional, not authoritative

That creates:

• ❌ Two systems of record
• ❌ Duplicate effort
• ❌ Compliance & audit risk
• ❌ Broken pre-arrival automation
• ❌ Staff confusion (“Where is the truth?”)

What the System Should Look Like

Canary must be the single system of record

Regardless of how the data is captured.

Guest-completed OR Staff-assisted → Canary stores it

That is the non-negotiable design principle.

Why This Happens (Root Cause)

Canary’s default setup assumes:

• Guests will self-complete pre-arrival
• Staff intervention is rare

But in real hotels:

• Business travelers skip links
• Airbnb guests miss emails
• Mobile browsers fail ID upload
• Guests arrive late / tired / rushed

Canary is being used as a “guest tool” instead of a “front-desk system.”

Enable Staff-Assisted Completion in Canary 

Required capability:

• Staff can:
  • Upload ID on behalf of guest
  • Trigger CC authorization
  • Complete tasks even if guest never used the link

Outcome:

• Canary remains authoritative
• PMS is downstream only
• Zero duplication