Where direct bookings are bleeding to OTAs and Marriott.com, walked click-by-click through the live WebRezPro funnel, the website handoff, and the Marriott Bonvoy Homes & Villas surface. Verdict on whether WebRezPro is sufficient for 2026.
kokomobotanicalresort.com → secure.webrez.com → Marriott Bonvoy Homes & VillasKokomo currently uses WebRezPro (booking engine + PMS, by World Web Technologies) on the website, with SiteMinder as the channel manager syncing inventory to OTAs (Booking.com, Expedia, others), and Marriott Bonvoy Homes & Villas as a separate direct connection. The architecture is normal for a property of this size. The execution is leaking direct bookings at multiple seams.
This audit walked the live funnel from kokomobotanicalresort.com through to the WebRezPro checkout page, and verified the Marriott Bonvoy Homes & Villas surface separately (cross-referenced with the AI Visibility & Apple Maps Audit). The result: five P0 leaks (every one fixable inside WebRezPro or with a single configuration change), six P1 leaks (operational tuning), and three P2 leaks (improvements that compound).
Most of the bleeding can be stopped without migrating engines. But the configurable fixes have to ship before the migration question can be answered honestly.
Live click-by-click walkthrough of the booking funnel from the public website to the payment step, conducted on 12 May 2026 from a clean browser session.
kokomobotanicalresort.com homepage, observed CTA placement and copyThis audit does not assume conversion numbers, OTA mix, or commission rates. Where dollars cannot be sized without that data, the leak is described in mechanism and percentage-of-intent terms.
Highest-cost leaks. Each is fixable inside WebRezPro or with a single ticket to the right vendor.
Clicking Reserve Today on kokomobotanicalresort.com loads secure.webrez.com/hotel/2065/?... in a fresh tab. Different domain, generic engine chrome, no Kokomo theming. Industry data: 20–40% of high-intent clicks are lost at a domain seam alone.
Embed the WebRezPro booking engine inline on a kokomobotanicalresort.com page (/reservations/ or modal overlay), or migrate to an engine that supports a true white-label iframe.
WebRezPro does support an iframe embed; confirm with the vendor whether the current account plan includes embed-capable widgets.
At the payment step the booking policy reads "Alive and Well must receive full and final payment." The umbrella brand logo appears on every step. Guest credit card statement will read "Alive and Well," not Kokomo. Chargeback risk plus immediate trust break.
White-label the WebRezPro property to display "Kokomo Botanical Resort" everywhere a guest sees it: header, logo, booking policy, and the merchant-account payment descriptor.
This is a configuration change. If WebRezPro can't fully white-label per-property under the current account structure, that alone is sufficient justification to migrate.
The Reserve Today button on the homepage carries date_from=20260121&date_to=20260122 (Jan 21–22, 2026, in the past). Every guest who clicks Reserve Today today arrives at the engine seeing "No rooms available," because the engine receives expired dates.
Either remove the date params from the Reserve Today URL entirely (let the engine default to today + 1), or dynamically compute today + 30 days as the default at page-render time. One-line change in the website's button.
Searching "Kokomo Botanical Resort" on Marriott Bonvoy Homes & Villas AI search returned 344 homes. In Hawaii, Australia, and Florida. None matched. Drilling into the Providenciales filter revealed 6 Kokomo cottages are in fact listed, but only findable by destination, never by brand search.
Every Bonvoy member who searches "Kokomo" finds nothing and gives up or books elsewhere.
Open a ticket with the Marriott Bonvoy Homes & Villas account manager. The listing metadata needs "Kokomo Botanical Resort" in searchable property-name fields.
Also request that "Kokomo Botanical Resort" be added as a recognized property in Bonvoy's destination autocomplete, the way individual hotels surface.
Same six cottages, three different label sets across the three systems a guest moves through. See the naming table below. A guest who reads about "Deluxe 2 King" on the website cannot match it to any label on the booking engine. They pick the wrong cottage, abandon, or call to confirm.
Adopt one canonical naming convention. Recommend the website's names since they are the most descriptive of bed configuration.
Update WebRezPro room labels and the Marriott Bonvoy listing titles to match the website. A couple hours of operational work, large UX gain.
Three systems, three different label sets, same six rooms. Pick one.
| Website (kokomobotanicalresort.com) | WebRezPro (secure.webrez.com) | Marriott Bonvoy Homes & Villas |
|---|---|---|
| Classic 2 Queen | Kokomo Classic 2 Bedroom Couple Cottage Suite | Kokomo Classic 2 Bedroom Couples Cottage |
| Classic Queen + 2 Twin | Kokomo Classic 2 Bedroom Family Cottage Suite | Kokomo Classic 2 Bedroom Cottage |
| Deluxe 2 King | Kokomo Deluxe King/Single | Kokomo Deluxe King - Single Cottage |
| Deluxe King + 2 Twin | Kokomo Deluxe King/King | Kokomo Deluxe King - King Cottage |
| Ultra-Lux King + 2 Twin | Kokomo Premium King/King | Kokomo Premium King - King Cottage |
| Ultra-Lux 2 King | Kokomo Ultra-Lux King/King | Kokomo Ultra-lux King - King Cottage |
Recommended canonical naming: the website's bed-configuration-first names (Classic 2 Queen, Deluxe King + 2 Twin, etc.). They convey occupancy and layout in one glance, which is what a guest is comparing against when shopping.
Each one costs single-digit percentage points of conversion. Stacked, they account for substantial direct-bookings loss.
Even when the URL passes valid future dates, the engine renders a "Kokomo Botanical Resort" modal on top of the results forcing the guest to click "Search for availability" again. Pure friction.
Confirm with WebRezPro whether the modal can be suppressed when valid date params are present. Almost certainly a configurable setting on the engine.
Rate cards show "$337.50 (excl tax) USD/night." A guest who internally budgets at $337 hits sticker shock at checkout when it becomes $428.63/night all-in (27% tax). FTC has favored all-in pricing display since 2024.
Toggle WebRezPro's display setting to tax-inclusive pricing on the rate cards. Tax breakdown remains available at checkout and on the confirmation.
The Guest step requires Address 1, City, Country, plus optional State, Postal/ZIP, all before reaching payment. Modern engines collect name/email/phone first, address only at the payment step. Each extra required field drops conversion roughly 2–4%.
In WebRezPro, make Address fields optional or move them to the payment step. If the engine doesn't support this customization at the booking-flow level, it's a structural reason to consider migration.
For a 2-adult booking, the form still renders four "Additional Guest 1 / 2 / 3 / 4" first+last name field pairs. They look mandatory even when empty. Confusing and slow.
Hide additional-guest fields dynamically based on guest count, or move them to a pre-arrival "complete your guest list" email after the reservation is confirmed.
WebRezPro displays three rate plans (Prepay $337.50, Direct Booking KBR $382.50, Best Available Rate $450) and "Earn $X Cash Rewards." None of these are anchored against what the same guest would pay on Booking.com or Expedia. Kokomo Rewards is real and visible at the form step ($151.88 earned on a $1,285 booking = 11.8% effective rebate), but the offer copy is "Enroll in Kokomo Rewards" with no value explanation.
Add a comparison bar above the rate cards: "Best price guaranteed when you book direct. Save 12–18% vs OTA channels and earn $X back in Kokomo Rewards."
Build a clean "How Kokomo Rewards works" page on the website and link from the engine. Make the offer concrete, not enrollment-jargon.
Every cottage card in the engine shows "Minimum age: 21." The website's positioning ("kid-friendly, family-friendly amenities, group friendly") openly contradicts this. A family looking at the website then reaching this gate either calls to clarify or abandons.
Also displayed: "Online reservations must be made at least [N] days in advance," which can lock out last-minute high-margin bookings if the lead-time is too long.
If the property accepts families with kids (the website says so), reset Minimum Age to "no minimum" in WebRezPro, or move adult-only restrictions to a separate adult-only rate plan that surfaces only when the guest filters for adults-only.
Confirm with operations whether the lead-time rule is intentional. If not, lower it to 1 day so last-minute direct bookings can close.
Operational improvements that compound over time.
Rate cards do not surface a Bonvoy member rate or "Earn Bonvoy points on this stay" line. Direct-booking on kokomobotanicalresort.com gives a Bonvoy member nothing extra over booking on marriott.com. This contradicts the Bonvoy partnership.
Set up a Bonvoy member rate plan inside WebRezPro (rate plan tied to a Bonvoy member-ID code), and display a Bonvoy points-earn estimate on each rate card. Coordinate with the Marriott Bonvoy account manager so the points reconcile correctly.
The desktop chrome of secure.webrez.com (4-stage form, full-width additional-guest grid, mandatory address) suggests the engine is desktop-first with a responsive shrink-to-mobile rather than a mobile-first checkout. 65–75% of luxury travel research happens on mobile.
Test the engine on a real mid-range mobile device. Measure form completion rate, time-to-completion, abandonment per step. If it's a desktop form shrunk for mobile, that becomes a P0 reason to migrate to a mobile-first engine (Mews, Cloudbeds).
Clicking Reserve from any cottage page (or from the homepage) lands the guest on the generic engine cottage list. The cottage they were reading about is not pre-selected or surfaced.
Pass room_type_id to WebRezPro from each cottage page's Reserve link, so the engine lands pre-filtered to that cottage's rate plans.
Or build an inline mini-booking widget per cottage page (requires P0.1 embed first).
WebRezPro is a competent mid-tier PMS + booking engine, built for independent inns, B&Bs, and small property groups. For a $400–$800 ADR award-winning Marriott Bonvoy partner with 24+ cottages and a real-estate sales angle, the engine's guest-facing UX is doing structurally less work than what the competitor set (Aman, COMO, Wymara, Beach Enclave) is shipping in 2026.
The leaks that are configurable probably account for ~60% of the conversion delta: P0.2 white-label, P0.3 stale dates, P0.5 SKU naming, P1.1 modal, P1.2 tax display, P1.3 form length, P1.5 incentive copy, P2.1 Bonvoy rate plan. Fix these first before deciding to migrate.
P0.1 inline embed quality, P2.2 true mobile-first checkout, and per-cottage page widgets are structural limitations of the engine's chrome. If, after the configurable fixes, conversion is still under 15% direct, migration is the right answer.
Sprint 1 (2–3 weeks): ship the eight configurable P0/P1 fixes inside WebRezPro and the website's Reserve button.
Sprint 2 (2 weeks): measure baseline conversion with the new configuration. Pull direct-vs-OTA split from the PMS (cross-checked against the GBP Analysis ratings data), OTA commission invoices, and Google Analytics.
Decision point: if direct conversion crosses 15–20%, hold on WebRezPro and keep optimizing. If still below 10%, migrate to an engine purpose-built for luxury hospitality UX.
If migration becomes the decision, the realistic shortlist for a Kokomo-caliber property:
| Engine | Best fit for | Strengths | Setup window |
|---|---|---|---|
| SynXis (Sabre) | Marriott Bonvoy Homes & Villas partners; Bonvoy-strategic properties | Native Bonvoy member rate handling, points display, rate-plan management; the standard Marriott-aligned engine | 8–12 weeks |
| Mews | Properties prioritizing best-in-class guest-facing UX in 2026 | Cleanest inline checkout in the segment, true mobile-first, strong open API, modern PMS | 6–10 weeks |
| Cloudbeds | Mid-market properties wanting fast time-to-value | Solid embed, broad channel manager, decent guest-facing UX, lower cost than Mews | 4–8 weeks |
| RoomRaccoon | Boutique 8–30 room properties, design-sensitive | Cleanest inline widget on a budget; smaller brand presence; probably under-sized for Kokomo's caliber | 3–6 weeks |
If the Bonvoy partnership is strategic long-term, SynXis is the natural target. If conversion lift is the priority over Bonvoy alignment, Mews wins on guest-facing UX. Cloudbeds is the fastest path if speed-to-value matters more than top-end polish.
This audit describes mechanism and percentage-of-intent. To convert that into a dollar number per leak, three data points are required:
With those three numbers, each P0 above gets a dollar amount per month, the breakeven on the configurable fixes lands in weeks, and the migration-vs-stay decision becomes a calculation rather than an opinion.
The biggest single leak is the external-domain handoff (P0.1). The biggest trust break is the "Alive and Well" billing identity (P0.2). The biggest acquired-channel waste is the invisible Marriott Bonvoy listing (P0.4). The biggest UX confusion is the three-naming-system cottage matrix (covered alongside the Website Design Review) (P0.5). All four are inside WebRezPro or a single account-manager ticket away.
Ship the configurable fixes inside one 2–3 week sprint. Measure for two weeks. Then re-open the question of whether WebRezPro is the right engine going forward. With data instead of speculation.