Most questions are about import — the parser doesn't know every format. Start here, and if you're still stuck, reach out directly.
The booking importer is regex-based — it pattern-matches against thousands of confirmation formats. It works well for most airlines, hotel chains, and booking platforms, but there are formats it hasn't seen. Here's how to handle common problems.
A low score (below 60%) means Honk found the booking type but couldn't extract much detail. The import preview screen lets you fill in anything missing before saving.
Tap any field on the import preview to edit it. Required fields (date, type) must be filled before you can save.
Sometimes a hotel email gets parsed as a flight, or a tour confirmation comes in as a restaurant. On the import preview, tap the booking type label to change it before saving.
If this happens consistently with one sender, it's a bug — report it (see below).
The parser returned empty. This usually means the email format is one it hasn't seen. Try a different import method — if you used Share Extension, try pasting the text instead. Sometimes reformatting helps.
If the email is from a major airline or hotel chain and Honk gets nothing, that's a gap worth reporting.
Date parsing can go wrong on unusual confirmation formats, and airport lookup can misfire on ambiguous IATA codes. Always verify dates on the import preview before saving.
Tapping a date field opens the date picker. Tapping an airport field lets you type a new IATA code or full name.
Every format Honk learns makes the app better for everyone. If you find a consistently broken format, reporting it helps.
To report a parsing failure, email support@honktravel.com with:
Never send real booking references, passport numbers, or payment details. Redact anything sensitive before sending.
Email directly. Honk is a solo project — you'll hear back from the person who built it.
support@honktravel.com