Name the page or city, and tell us whether it was a guide, sample route, result, share surface, or My Trips moment.
Support notes
Send a clear note with page context already attached
Use this page to report broken links, off-tone copy, route output issues, save/share bugs, or anything that interrupts the city → sample → trip flow.
The current page, language, city, and build version are captured here automatically, so you can send a cleaner report without rewriting the whole situation by hand.
Quick handoff
Best for quick issue reports
Pick an issue type first. The report block below will reshape itself around that problem so the most useful detail is already prompted.
Captured context
Current page snapshot
Open this desk from any Ryokoplan page and that surface is carried in automatically.
Current context
Open this page from anywhere in Ryokoplan and we will carry that page context here automatically.
Captured page
Waiting for page context…
Language
Waiting…
Build version
Checking version…
Release check note
Carry build context into feedback
No release-check draft detected on this browser yet.
Issue focus
What kind of thing felt off?
Pick the closest issue type. It changes the report template below so the handoff is more specific.
Active issue focus: General flow note · Use when the page felt rough, unclear, or off-tone but nothing was fully broken.
What helps most
Best details to attach
Short reports are fine. These are just the details that make fixes faster.
One clean sentence is enough: where you thought the click, scroll, save, or route handoff should have gone instead.
Say whether it felt broken, unclear, too dense, too memo-like, off-brand, or simply harder to use than expected.
Report block
Copy this feedback handoff
It includes issue type, source page, path, language, build version, and room for your note.
Open this desk from the exact page that felt wrong so path, language, and city are already attached when you copy the block.
Run release check first, then clear or attach that draft here so deploy checks and page-specific feedback stay together.