The help panel, the bell and the feedback button

Most software demos spend their time on the big pieces. The booking engine. The calendar sync. The rate suggestions. Fair enough — those are the parts that earn their keep.

But if you run a guesthouse in San Ignacio with your sister and one part-time housekeeper, you already know the big pieces are not what decides whether a system gets used. What decides it is the Tuesday morning when the housekeeper needs to mark a room clean, you are driving to Belmopan, and nobody can remember where the button is.

So this post is about three small things. A help panel on every page. A notification bell. A feedback button. None of them are impressive. All three are the difference between a system people use and a system people avoid.

Help written on the page you are standing on

The usual way to learn software is to go and find the manual. Somebody emails you a PDF, or sends you to a help site, and you open a second tab and start searching for words you hope match what you are looking at.

That works if you are a person who likes computers. Most owners of small properties are not, and most of the staff are definitely not. The front desk person at a Placencia hotel knows guests, rooms and the tour operators. She does not want to become a software person on top of all that.

The help panel in the Direct Belize admin sits on every page. You open it where you are, and it explains that page — what the fields mean, what happens when you press the thing, what the usual mistake is. No searching. No second tab.

Alongside it there is a printable manual, because some people genuinely prefer paper in a drawer by the desk, and a guided tour that runs the first time someone signs in. Three ways in, because people are different.

The point is not that the help is clever. The point is that it is close. A question that takes ten seconds to answer gets asked. A question that takes ten minutes of hunting gets guessed at instead, and guessing is how a room ends up double-booked.

One bell instead of five places to look

The second small thing is the notification bell.

Here is the problem it solves. At a small property, the things that need a person are scattered. A guest has messaged on Booking.com. Somebody arrived yesterday and was never checked in. A rate suggestion is sitting there waiting for someone to approve or reject it. The sync with one of the booking sites threw an error at two in the morning. A departure room in Hopkins is still showing dirty and the next guest lands this afternoon.

Five different corners of the business, five different places you would have to go and look.

The bell gathers them into one list:

• Arrivals that have not been checked in
• Unread guest messages from the booking sites
• Approvals waiting — price suggestions, drafts, anything that needs a human yes
• Sync errors from the channel manager
• Overdue cleans and maintenance jobs

The question a busy owner asks at seven in the morning is not "what happened yesterday". It is "what needs me right now". The bell is an answer to that question and nothing else.

This matters more at a small property than a big one. A 100-room hotel has a night auditor and a duty manager and a shift handover. A six-room guesthouse on Caye Caulker has you, and whoever is on today. There is no handover meeting. The bell is the handover meeting.

It also matters because of how the permissions work. Staff logins in the admin have a View / Edit / Create / Delete matrix per area, with preset roles — administrator, front desk, marketing, read-only — and custom roles if you need them. A housekeeper signing in sees the housekeeping items. The front desk person sees arrivals and messages. Nobody has to sift through a list of things that are not their job.

You can see how the pieces fit together on the admin features page.

The feedback button, and why it goes straight to the developer

The third thing is the smallest and the one people are most surprised by.

There is a feedback button in the admin. You press it, you type what happened or what you wish the thing did, and it goes to the developer with the page you were on attached. Not a ticket number. Not a queue. Not a form that asks you to describe your browser.

Why this matters at a small property is worth saying plainly. At a hotel group, there is an IT person, and that person is the filter between the staff and the software company. At a guesthouse in Corozal, the owner is the IT department. If something is broken or confusing, there is nobody to tell except the people who made it.

The page being attached does the work. Most bug reports from non-technical people are hard to act on, not because the person described it badly, but because software behaves differently depending on where you are and what you were doing. Attaching the page removes that whole conversation.

And the ideas matter as much as the bugs. The person who notices that the arrival list would be more useful sorted a different way is the person using it forty times a week. That is usually not the owner. It is the front desk.

The same admin, whether you have three rooms or twenty-five

Direct Belize plans run 1–6 rooms on Starter, 7–14 on Growth and 15–25 on Pro, with larger properties set up individually. The admin is the same one in all three cases.

That is deliberate. A two-person guesthouse in Punta Gorda and a 25-room hotel in San Pedro with a front desk, housekeepers and a marketing person are running the same system. What differs is how many staff logins are in use and what each one is allowed to see and change.

Which is exactly why the three small things carry so much weight. The system has to be learnable by somebody who was hired last week to cover the desk, with no training budget and no IT department behind them. Help on the page. One bell. A way to say "this is wrong" that actually reaches somebody.

Setup for a new property is typically done within a couple of weeks, and there is no long-term contract. If you want to see what the plan would look like at your room count, the pricing page lays it out in BZ$.

None of this is the exciting part of the product. It is just the part that decides whether the exciting parts ever get used.