Luggage Marketplace · SCR-33

💬 Messages 2 conversations

Rajesh Kumar 2 min ago

Sure, please come to the main entrance. Ring the bell.

Hotel Admin Yesterday

Drop-off confirmed. See you!

Sanjay R. 🔒

Chat available after booking confirmation

Rajesh Kumar · Rajesh Storage Hub

Booking #LSM-2026-A4B7C9D2 · Jun 5–7, 2026 · 🔵 Confirmed

View Booking →

Jun 4, 2026

Hi Rahul! Your booking is confirmed. I'll be at the shop from 9 AM. Let me know when you're on your way.

Rajesh Kumar · 3:25 PM

Thanks Rajesh! I'll be there around 10 AM. Quick question — where exactly is the entrance to the storage area?

You · 3:30 PM ✓✓

Sure! Enter through the main front door of the shop — the storage area is at the back. Here's a photo to help you find it:

🏪

shop_entrance.jpg · 1.2 MB · Tap to expand

Rajesh Kumar · 3:34 PM

Jun 5, 2026

I'm 10 minutes away. Should I park on the street outside?

You · 9:50 AM ✓✓

Yes, there's free parking right outside. If you can't find it, you can call me on +91 ******* 4521 — oh wait, just use this chat! 😄

Rajesh Kumar · 9:52 AM

Sure, please come to the main entrance. Ring the bell twice and ask for Rajesh. See you soon! 🙂

Rajesh Kumar · 9:55 AM

Phone masking annotation: The message above contained "+91 98712 34521" — the system detected and masked it to "+91 ******* 4521". This enforcement is backend-side, not client-side, so it cannot be bypassed by either party. Prevents off-platform contact attempts. SRS §7.9 FR-38

54 / 1000

📎

➤

🔒 Chat Access Restriction (annotation)

When chat IS available:

Booking status = Confirmed, Checked-in, or Completed. Both guest and host can send messages within the booking context.

When chat is BLOCKED:

Booking status = Pending or before confirmation. Message: "Chat becomes available once your booking is confirmed." Prevents off-platform contact that bypasses commission. SRS §7.5 FR-17; §7.9 FR-38

Wireframe Annotations — SCR-33 · In-App Chat

Persona: Guest and Host (Active Booking Communication) — Communication channel opened after booking is confirmed. Accessible from SCR-12. Not available before confirmation — prevents pre-booking direct contact that would bypass the platform. SRS §7.9 FR-38

Booking Context Header — Chat header shows: other party's name + avatar / Booking ID / Listing name / current booking status badge (colour-coded per FR-17 states). Anchors every conversation in its booking context. "View Booking" link to SCR-12. SRS §7.5 FR-17; §7.9 FR-38

Message Bubbles — Standard chat: sent right-aligned (orange bubbles) / received left-aligned (white bordered bubbles). Timestamp + read receipt (✓✓) per message. Max 1000 chars per message with live character counter in input area. SRS §7.9 FR-38

Phone Number Masking — System automatically detects and masks phone number patterns: "+91 98712 34521" → "+91 ******* 4521". Backend-enforced — cannot be bypassed by either party. First-message onboarding tooltip explains the masking behaviour. SRS §7.9 FR-38; §8.4 Security

Photo Attachment — 📎 paperclip button: attach up to 3 photos per message (JPG/PNG max 5 MB each). Photos displayed as inline thumbnails in the message thread. Tap to expand full-screen. Stored in S3/GCS cloud storage (FR-93). SRS §9.2 FR-93

Chat Access Restriction — Chat is only available when booking status = Confirmed, Checked-in, or Completed. Before confirmation: blocked with message "Chat becomes available once your booking is confirmed." Conversation list shows locked items for pre-confirmation bookings. SRS §7.5 FR-17; §7.9 FR-38