androidlover5842/TrisolarisPMS
1
0
Fork 0
Code Issues 22 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

Telephony: Call-ended assistant (Truecaller enrichment + quick booking bubble) #21

New Issue
Open
opened 2026-02-09 17:46:19 +05:30 by androidlover5842 · 0 comments
androidlover5842 commented 2026-02-09 17:46:19 +05:30
Owner
Copy Link

Goal

  • After a phone call ends, help front desk create a booking fast:
    • identify caller (guest) from local DB
    • if unknown, prefill from Truecaller (when available/consented)
    • show a small bubble/notification to create booking with minimal input (expected check-in/out)

UX

  • On call ended:
    • If an active booking already exists for this caller phone (OPEN/CHECKED_IN), do not show the create bubble. Show either nothing or "Open existing booking" instead.
    • If caller matches a guest in DB: show bubble "Create booking for / ".
    • If not in DB:
      • If Truecaller provides name: prefill name + phone.
      • Otherwise: allow quick manual name entry.
    • Bubble click opens a "Quick Booking" screen:
      • manager enters expectedCheckInAt + expectedCheckOutAt
      • source defaults to WALKIN
      • notes optional
      • everything else prefilled (phone/name)

Android / Platform constraints (must respect OS + policies)

  • Prefer notification + app shortcut if overlay permission is not granted.
  • Overlay bubble requires explicit user enablement and must be dismissible.
  • Access to call state/phone number depends on Android version + runtime permissions + default-dialer restrictions.
  • Do NOT rely on reading other apps' UI directly; for any OCR/screenshot-based extraction, require explicit user action (user picks image) and consent.

Integrations

  • Truecaller enrichment:
    • Use official Truecaller SDK/API if available; respect their TOS and user consent.
    • Cache only what is needed (name/phone) with source attribution.
  • Optional OCR fallback:
    • User-initiated "Import screenshot" -> server AI extracts fields -> show review before save.

Engineering requirements

  • Follow Room DB sync rule: booking create + guest create/link must go server -> Room -> UI.
  • Separate permission gating: add explicit policy methods in core/auth/AuthzPolicy for telephony/guest enrichment.
  • Audit: log enrichment source (DB/Truecaller/OCR) and who approved it.

Acceptance

  • If an active booking already exists for caller phone, bubble is suppressed (or routes to existing booking).
  • After creating a booking, manager can generate a Razorpay payment link and send it to the guest via SMS/WhatsApp (Share intent or server SMS/WhatsApp integration).
  • After a call, manager can create a booking in under 15 seconds with correct name + phone + dates.
Goal - After a phone call ends, help front desk create a booking fast: - identify caller (guest) from local DB - if unknown, prefill from Truecaller (when available/consented) - show a small bubble/notification to create booking with minimal input (expected check-in/out) UX - On call ended: - If an active booking already exists for this caller phone (OPEN/CHECKED_IN), do not show the create bubble. Show either nothing or "Open existing booking" instead. - If caller matches a guest in DB: show bubble "Create booking for <name> / <phone>". - If not in DB: - If Truecaller provides name: prefill name + phone. - Otherwise: allow quick manual name entry. - Bubble click opens a "Quick Booking" screen: - manager enters expectedCheckInAt + expectedCheckOutAt - source defaults to WALKIN - notes optional - everything else prefilled (phone/name) Android / Platform constraints (must respect OS + policies) - Prefer notification + app shortcut if overlay permission is not granted. - Overlay bubble requires explicit user enablement and must be dismissible. - Access to call state/phone number depends on Android version + runtime permissions + default-dialer restrictions. - Do NOT rely on reading other apps' UI directly; for any OCR/screenshot-based extraction, require explicit user action (user picks image) and consent. Integrations - Truecaller enrichment: - Use official Truecaller SDK/API if available; respect their TOS and user consent. - Cache only what is needed (name/phone) with source attribution. - Optional OCR fallback: - User-initiated "Import screenshot" -> server AI extracts fields -> show review before save. Engineering requirements - Follow Room DB sync rule: booking create + guest create/link must go server -> Room -> UI. - Separate permission gating: add explicit policy methods in `core/auth/AuthzPolicy` for telephony/guest enrichment. - Audit: log enrichment source (DB/Truecaller/OCR) and who approved it. Acceptance - If an active booking already exists for caller phone, bubble is suppressed (or routes to existing booking). - After creating a booking, manager can generate a Razorpay payment link and send it to the guest via SMS/WhatsApp (Share intent or server SMS/WhatsApp integration). - After a call, manager can create a booking in under 15 seconds with correct name + phone + dates.
androidlover5842 added this to the TrisolarisPMS Roadmap project 2026-02-09 17:46:38 +05:30
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
ai-ocr
AI / OCR / parsing automation
 api
API / contract / retrofit
 availability
Availability / inventory / allocation
 bug
Bug / regression
 compliance
Compliance / audit / legal requirements
 feature
User-facing functionality
 finance
Cashbook / expenses / settlements
 guest
Guest profile & identity flows
 guest-docs
Guest documents (upload/view/delete)
 hr-payroll
Staff, attendance, payroll
 integration
3rd party integrations / automation
 privacy
Privacy, consent, sensitive data handling
 room-db-sync
Must follow Room DB sync rule
 room-stay
Room stay management
 security
Security / permissions / sensitive data
 telephony
Call-related UX/integrations
 ux
User experience / UI polish
 voice-ai
Speech-to-text / voice extraction
No Label ai-ocr compliance feature guest integration privacy room-db-sync security telephony
Milestone
No items
No Milestone
Projects
Clear projects
No project TrisolarisPMS Roadmap
Assignees
Clear assignees
androidlover5842
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: androidlover5842/TrisolarisPMS#21
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?