Skip to main content

What is a Parser?

πŸ“¨ What is a Parser?

Introduction

When hotels receive messages from Online Travel Agencies (OTAs) like Booking.com, those messages arrive as emails β€” not as structured chat messages. Without a parser, these emails can appear garbled, incomplete, or hard to read in the Unified Inbox. πŸ“₯

The Email Parser is a Bookboost feature that automatically extracts and structures the content of incoming OTA emails, so hotel staff can read them clearly and respond efficiently β€” all without leaving the Unified Inbox.


Main Concept

A parser is a tool that reads the raw content of an incoming email and converts it into a clean, readable message format inside the Unified Inbox.

When an OTA like Booking.com sends a message to your hotel, it arrives as a raw email with complex formatting. The parser processes this email and displays it as a structured message. For full transparency, Bookboost shows both the raw email and the extracted message, so agents always have access to the original content if any parsing issue occurs.

Key terms:

  • Raw email β€” the original, unformatted email as received from the OTA.

  • Parsed message β€” the cleaned-up, structured version displayed in the Unified Inbox.

  • Parser domain β€” the email domain the parser listens to (e.g., mchat.booking.com for Booking.com messages).


Use Cases

  • πŸ“© Displaying Booking.com guest messages cleanly inside the Unified Inbox

  • πŸ” Giving agents access to both the raw email and parsed content for full context

  • βš™οΈ Configuring, enabling, or disabling message parsing per organisation

  • πŸ› οΈ Supporting internal testing via custom domain configuration


Configuration and Setup

Follow these steps to configure the Email Parser in Bookboost:

image

  1. Navigate to Inbox Settings using the settings icon in the Unified Inbox.

  2. Go to the Organisation Settings section.

  3. Find the Email Parser configuration.

  4. Select Booking.com as the parser type (currently the only available option).

  5. The default domain is pre-set to mchat.booking.com β€” this does not need to be changed for most hotels.

  6. Toggle the parser on or off as needed (default: enabled). βœ…

  7. Click Save to apply your settings.

πŸ’‘ Tip: Most hotels should leave the domain setting unchanged. Editing the domain is only needed for internal testing or if your organisation uses a custom email forwarding setup.


Advanced Setup

Editing or Deleting the Parser

Once a parser is configured, you can:

  • Edit the domain β€” useful if your hotel has a non-standard email forwarding setup or for internal testing purposes.

  • Disable the parser β€” if you no longer want messages to be parsed automatically, you can toggle it off without deleting it.

  • Delete the parser β€” removes the parser configuration entirely from your organisation settings.


Known Issues or Limitations

  1. Images are not parsed β€” images included in Booking.com emails cannot currently be extracted or displayed in the Unified Inbox.

  2. Not 100% guaranteed β€” occasional message content may be missed due to the structure of OTA emails. In such cases, the raw email remains available. Any parsing issues should be flagged with the Bookboost Product team as soon as possible.

  3. Action buttons are not parsed β€” Booking.com action buttons (e.g., "Accept Request") within emails are not yet supported by the parser.

  4. Booking.com only β€” currently, the Email Parser supports Booking.com as the only OTA parser type.


Conclusion

The Email Parser ensures that OTA messages, particularly from Booking.com, are displayed clearly and accurately inside the Unified Inbox. By enabling and correctly configuring the parser, hotel teams can reduce miscommunication, improve response times, and always have access to both the original and structured versions of guest messages. 🌟


Support

Please contact us through the 'Talk to Us' option on the left menu in the platform, or through the Bookboost Support email at support@bookboost.io if you have questions or need additional support.

Did this answer your question?