Telephony: Call recording -> server transcription -> booking field extraction (dates/room type/pax) #22

New Issue

androidlover5842 · 2026-02-09T17:51:01+05:30

androidlover5842 commented

2026-02-09 17:51:01 +05:30

Goal

After a call ends, automatically (with explicit consent) record the call audio, send it to server, transcribe, and extract booking details.
When creating a booking from the call-ended flow, prefill using:
- Truecaller: caller name/phone (if available)
- Voice AI: extracted room type, expected check-in/out, pax, notes

Flow

During/after call:
- If call recording is enabled + allowed: capture audio.
- On call ended: upload audio to server in background.
Server:
- Speech-to-text (STT) with diarization if possible (staff vs guest).
- Extract structured fields:
  - expectedCheckInAt / expectedCheckOutAt (with timezone)
  - roomType / room count
  - guest count (adults/total)
  - notes (pickup, late arrival, etc.)
- Return extraction + confidence + raw transcript (restricted access).
App:
- Call-ended bubble opens Quick Booking:
  - Prefill extracted fields.
  - Show confidence + allow manual edits before submit.

Android constraints

Call recording is heavily restricted on modern Android builds and may depend on:
- OEM dialer support
- being the default dialer app
- device/region policies
Provide fallback when recording not possible:
- user-initiated voice note summary (record staff's recap after call)
- manual entry only

Privacy / Legal (non-negotiable)

Call recording must be opt-in with clear consent UX.
If local law requires two-party consent, support a workflow to collect it (or disable feature).
Encrypt audio at rest and in transit; set retention policy (auto-delete after N days).
Do not expose transcripts to roles that shouldn't see them.
Audit log: who recorded/uploaded/used extraction to create booking.

Engineering requirements

Keep AI/STT server-side; app only uploads and reviews.
Follow Room DB sync rule for booking creation and guest linking.
Add explicit policy methods in core/auth/AuthzPolicy for call recording + transcript viewing.

Acceptance

With consent and supported devices, after a call ends the booking form is prefilled with correct dates/room type most of the time, and staff can correct it quickly when needed.

Goal - After a call ends, automatically (with explicit consent) record the call audio, send it to server, transcribe, and extract booking details. - When creating a booking from the call-ended flow, prefill using: - Truecaller: caller name/phone (if available) - Voice AI: extracted room type, expected check-in/out, pax, notes Flow - During/after call: - If call recording is enabled + allowed: capture audio. - On call ended: upload audio to server in background. - Server: - Speech-to-text (STT) with diarization if possible (staff vs guest). - Extract structured fields: - expectedCheckInAt / expectedCheckOutAt (with timezone) - roomType / room count - guest count (adults/total) - notes (pickup, late arrival, etc.) - Return extraction + confidence + raw transcript (restricted access). - App: - Call-ended bubble opens Quick Booking: - Prefill extracted fields. - Show confidence + allow manual edits before submit. Android constraints - Call recording is heavily restricted on modern Android builds and may depend on: - OEM dialer support - being the default dialer app - device/region policies - Provide fallback when recording not possible: - user-initiated voice note summary (record staff's recap after call) - manual entry only Privacy / Legal (non-negotiable) - Call recording must be opt-in with clear consent UX. - If local law requires two-party consent, support a workflow to collect it (or disable feature). - Encrypt audio at rest and in transit; set retention policy (auto-delete after N days). - Do not expose transcripts to roles that shouldn't see them. - Audit log: who recorded/uploaded/used extraction to create booking. Engineering requirements - Keep AI/STT server-side; app only uploads and reviews. - Follow Room DB sync rule for booking creation and guest linking. - Add explicit policy methods in `core/auth/AuthzPolicy` for call recording + transcript viewing. Acceptance - With consent and supported devices, after a call ends the booking form is prefilled with correct dates/room type most of the time, and staff can correct it quickly when needed.

androidlover5842 added the feature room-db-sync guest compliance security integration telephony privacy voice-ai labels 2026-02-09 17:51:01 +05:30

androidlover5842 added this to the TrisolarisPMS Roadmap project 2026-02-09 17:51:09 +05:30

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: androidlover5842/TrisolarisPMS#22