COMMUNICATION CHANNELS
Images, video and PDFs
How D3x agents read guest photos, video, screenshots, and booking PDFs, then continue the conversation, and how they send knowledge-base photos of services, items, and locations.
- Images and video in-thread
- Screenshots of bookings
- PDF booking confirmations
- Knowledge-base photos sent back
Guests do not only type. They send a photo of a broken fixture, a video of a loose lamp, a screenshot of an OTA booking, or a confirmation PDF. D3x makes sense of that media and continues the conversation itself. Chatbots answer. D3x resolves.
The same agent can go the other way: when a guest asks what breakfast looks like, or wants more detail on a service, item, or location, D3x searches the property knowledge base and sends the relevant photos in the thread. Product overview: Messaging.
What the agent can read
Images and video
In-room issues, damage, and fixtures. In a German-language thread the agent interpreted a video of a loose bedside lamp with exposed wiring and told the guest not to use it or touch it any further.
Screenshots
Booking details pulled from one or more screenshots so matching can continue. Example: the screenshot showed the name Emma GmbH for a stay from 31 August to 3 September 2026, while the booking number given so far still did not match.
PDFs
Booking confirmation attachments. D3x extracts the details and keeps going in the same thread, instead of asking the guest to retype what is already on the document.
Knowledge-base photos
Outbound, not only inbound. Breakfast, a service, an item, or a location: the agent pulls the matching photos from the D3x knowledge base and shows them to the guest.
How it shows up in the conversation
- 1
Guest sends a file
Photo, video, screenshot, or PDF on WhatsApp or another supported messaging channel.
- 2
The agent reads it
It identifies what is in the media: a safety issue in a room, a company name on a screenshot, dates and names on a confirmation PDF.
- 3
The thread continues
The reply uses those details. Safety instructions when wiring is exposed. Booking-match questions when a confirmation number still does not line up. Knowledge-base photos when the guest wants to see a service or space.
Examples from production threads
These are replies the agent sent after reading guest media. Quoted in English here; the first two threads ran in German.
- Images + video: “Thank you, the video shows a loose bedside lamp with exposed wiring. Please don't use it or touch it any further.”
- Screenshots: “The screenshot shows the name ‘Emma GmbH’ for the stay from August 31–September 3, 2026. However, the booking number provided so far still does not match.”
- PDF: the agent extracts fields from a booking confirmation and continues troubleshooting with that context.
- Knowledge base: a guest asks for a breakfast photo or more detail; D3x sends the relevant images from the property library.
What this is not
- Not a captioning toy. The point is to keep resolving the request in the same thread.
- Not an automatic PMS write from a screenshot. Extracted details feed the conversation and the Skills Engine; writes still follow your property rules.
- Not a replacement for voice notes. Voice memos are transcribed separately and handled as text. See WhatsApp.