Roadmap

See what we're working on and what's coming next.

Roadmap

See what we're working on and what's coming next.

Roadmap

See what we're working on and what's coming next.

Ideas35

See guest conversations across your other numbers

See guest conversations across your other numbers When viewing guest details, see if that guest has had conversations with other phone numbers in your organization (that you have access to), with links to jump to those conversations. Get the full picture of a guest's history with your property without switching between numbers to look for it.

Mews payment link variable for messages

Mews payment link variable for messages A message variable that inserts a link to the guest's payment page in Mews. Drop it into a text or automation and the guest gets a personalized link to add their payment method - no more manually copying payment URLs for each reservation.

Compliance-language website wizard

Compliance-language website wizard Smooth out the wizard that helps customers add the required SMS compliance language (opt-in/consent language, privacy policy references) to their own website, so they can complete that part of 10DLC without hand-writing it.

Easier handoff of 10DLC onboarding instructions

Easier handoff of 10DLC onboarding instructions Make it easy for customers to hand off the 10DLC onboarding/setup instructions to whoever manages their website or handles the technical steps. Today the account owner often can't complete the steps themselves — give them a clean way to pass the instructions along to a teammate or web person so nothing stalls.

More guest context on the mobile app screen

More guest context on the mobile app screen Add guest context to the mobile conversation/call screen that isn't there today. 1) Guest status tag — a quick indicator of whether the person is a past, present, or future guest, shown especially when they call in, so staff have instant context. 2) Door code — surface the guest's door/access code in the app, which doesn't exist there currently.

Typing indicators in conversations

Typing indicators in conversations Show a live "typing…" indicator when a teammate (or the guest) is actively typing in a conversation, so staff can see in real time that someone is responding before the message lands. Surfaces the live action as it happens rather than only showing the finished message.

Presence + typing on mobile (web parity)

Presence + typing on mobile (web parity) Bring conversation presence to the mobile app. Today staff can only see who has a conversation open in the web browser — mobile shows neither who is viewing a conversation nor who is typing. Add both to the mobile app so mobile users have the same awareness web users do.

More guest context on the mobile app screen

Easier handoff of 10DLC onboarding instructions

Compliance-language website wizard

Planned4

WhatsApp connection wizard

The self-serve signup flow that lets a hotel connect its own WhatsApp Business Account to Hello Hotel and start messaging — covering the WhatsApp/Meta signup, number verification, approval steps, and mapping the connected account to the right property. Implementation path is still being decided (leaning toward Telnyx's hosted signup flow). Target: late summer 2026. Note: WhatsApp can already be enabled manually per property by request today; this ticket is the widely available, self-serve version.

Front desk dashboard & customizable guest-list view

A front-desk / guest operations dashboard, combining two closely related ideas: 1) Operational 'what needs a response now' view: missed calls not yet called back, texts awaiting reply, outstanding/needs-attention items, aging/urgency, arrivals today, in-house guests with open threads, voicemails, and a data-hygiene queue. 2) A tabbed, customizable guest table: Arriving / Departing / In-House / custom Lists with an easy top toggle between views, and customizable columns - conversation status, sentiment, arrival status, stay dates, room type, room number, housekeeping status from Mews, staff assignment, door code - plus saved custom lists. Inspiration: Akia's dashboard. Complements the pre-booking (#23) and overall (#26) intelligence dashboards - this is the operational 'now' view. Dependencies: housekeeping status & room type need the right Mews fields; the staff-assignment column depends on conversation owners (#46/#30). Column prefs per user. Key definition to settle: what counts as 'responded'. (Merged from the former Reception/guest-support dashboard and customizable guest-list view tickets.)

Conversation assignment and claim

Conversation assignment and claim Let team members claim or assign a conversation to themselves or a teammate so it lands in that person's personal queue. Assigned conversations show an owner badge on the thread and can be filtered by assignee in the inbox view. Prevents two team members from replying to the same guest at the same time during busy periods, and gives every thread clear ownership so nothing falls through the cracks during hand-offs. Pairs naturally with the conversation intelligence dashboard so operational metrics like average response time, conversation load, and resolution rate can be measured per team member — not just at the property level. 4

Cloudbeds Integration

A native integration with Cloudbeds so properties on Cloudbeds get the same experience Mews properties get today: live reservation context next to every conversation, automatic guest identification on inbound calls and texts, smart guest status labels (Arriving, In-House, Departing, Past), two-way contact sync, and a one-click link from any conversation back to the guest in Cloudbeds. This is one of the most requested integrations on our roadmap.

In progress2

Two-way contact sync with Mews

Two-way contact sync with Mews Sync guest contacts in both directions between Hello Hotel and Mews. Today contacts flow from Mews into Hello Hotel - with two-way sync, updates you make in Hello Hotel (like a corrected phone number or email) would push back to the guest profile in Mews, so both systems stay accurate.

Group texting

Group texting Start a group text conversation with multiple guests in one thread - for example, a wedding party or a group traveling together. Everyone sees the same messages and can reply in one place.

In Testing3

Web chat widget for your website

An embeddable chat widget you can add to your own website. It's AI-response-first, but your team can jump in and reply directly in the web chat. If the guest wants to keep the conversation going elsewhere, the chat can move to text, call, or email — and the full context of the conversation carries over. Each web chat also creates a contact card for that person with the chat attached.

Reservation & guest notes (Mews two-way) + internal note type

Reservation & guest notes (Mews two-way) + internal note type Add three kinds of notes, choosing the type when adding: Guest note (about the person, at the top above Contact Information), Reservation note (about the stay, inside each reservation), and Internal Hello Hotel note (not synced to Mews). Show reservation/guest notes from Mews and write back two-way; internal notes stay in Hello Hotel only. Related: #32 internal notes on threads. Open question: does the Mews integration support reading both note types and writing back.

Add attachments to message composer

Support sending MMS attachments from the message composer — images, PDFs, and short video clips. Staff should be able to drop a file into the composer, preview it, and send it alongside text. This unlocks sending cabin maps, arrival instructions, receipts, menu PDFs, and property photos from inside a conversation thread, and closes a real gap against SMS-only tools like Kipsu and AKIA where operators have to link out to external hosts for long-form content.

Released32

URL shortening for guest links

URL shortening for guest links Automatically shorten long links — like check-in and booking links — down to a clean Hello Hotel branded short domain. Long URLs look messy and can break or get flagged in texts; short branded links are easier to share and look more trustworthy to guests.

Auto-create alphanumeric sender ID per messaging profile

Auto-create alphanumeric sender ID per messaging profile Automatically create an alphanumeric sender ID for every messaging profile we set up - likely a gap on number porting and/or new numbers. Also add the alpha sender name to the new-org setup flow so the sender ID is created with the right name. Note: alphanumeric sender IDs are region-dependent and not used for standard US A2P/10DLC long-code messaging - confirm where they actually apply (Telnyx + our markets) before defaulting on. Backfill existing profiles?

'Send Text' option to not re-open a closed conversation

'Send Text' option to not re-open a closed conversation Add an option on the Send Text automation action to NOT re-open a closed/resolved conversation, so informational automated messages don't resurface a thread as if it's live/unhandled. Open: should automated sends default to not reopening (opt-in to reopen)?

Delays should trigger a data refresh

Delays should trigger a data refresh When an automation hits a delay/wait step, re-fetch fresh data on resume (re-pull guest/reservation state, re-evaluate conditions) instead of acting on the snapshot from when it started - things change during a wait (cancellations, room reassignment, number updates). Bigger opportunity: re-check entry conditions after a delay and stop if they no longer hold (a 'still valid?' gate).

Stay-relative / recurring-within-stay trigger

Stay-relative / recurring-within-stay trigger Send messages on a cadence relative to each guest's own stay - e.g. text every 2nd day to offer room cleaning. Verified not possible today: Scheduled intervals are global (not per-guest), Check-in/out Upcoming only count hours before arrival/departure, and conditions check current day/time, not nights-elapsed. Missing primitive: a day-of-stay / nights-elapsed concept - a 'N days after check-in' / 'every N nights' trigger, or a condition/variable for nights into the stay. Generalizes to mid-stay offers (cleaning, check-ins, towel service, late checkout).

Choose 'match any' vs 'match all' on trigger conditions

Choose 'match any' vs 'match all' on trigger conditions On a trigger's matching conditions (e.g. the Schedule trigger's 'matching any of': check-in today, check-out today, in-house, has tag), let the user choose between any (OR) and all (AND). Currently hardcoded to any, so you can't narrow (e.g. 'check-in today AND tagged Event'). Quick win: a simple any/all toggle; fuller version: nested condition groups.

Trigger: same-day arrivals missing online check-in

Trigger: same-day arrivals missing online check-in A scheduled trigger that checks Mews for same-day check-in reservations that haven't completed online check-in, to nudge them the morning of arrival. (The Schedule trigger largely exists; this is the targeted use.) Open: does the Mews integration expose online check-in status; stop once they complete.

Trigger: room status change -> alert the guest

Trigger: room status change -> alert the guest When a room's status changes (e.g. from Inspected), alert the guest of that room ('your room is ready'). Hard part: correlate the room back to the reservation/guest occupying it that day (lookup: room + today's date -> active reservation -> guest). Watch: same-day turns (target the arriving reservation), timing, unassigned rooms. Make-or-break: can the room-status event resolve to a reservation/guest via the current Mews integration? Related: space status condition (#47).

Internal alerts & soft-fail flags in automations

Internal alerts & soft-fail flags in automations Let automations raise internal alerts, including 'soft fails' where the automation can still run but something is wrong. Example: texting a door code but the code is missing - still send (or a safe version) AND flag the conversation so a human handles it. Feeds the dashboard 'needs attention' widget. Open: define soft-fail vs hard-fail; mark a variable as required so its absence auto-flags.

Bulk add/remove tags in Contacts View

Bulk add/remove tags in Contacts View Select multiple contacts in the Contacts View and add or remove tags in bulk (e.g. tag all event guests at once, or clear a stale tag). Open questions: selection model (checkboxes, select-all, select-all-matching-filter); apply to the current filter/search result; other bulk actions (export, message).

Ideas35

See guest conversations across your other numbers

Mews payment link variable for messages

Compliance-language website wizard

Easier handoff of 10DLC onboarding instructions

More guest context on the mobile app screen

Typing indicators in conversations

Presence + typing on mobile (web parity)

More guest context on the mobile app screen

Easier handoff of 10DLC onboarding instructions

Compliance-language website wizard

Planned4

WhatsApp connection wizard

Front desk dashboard & customizable guest-list view

Conversation assignment and claim

Cloudbeds Integration

In progress2

Two-way contact sync with Mews

Group texting

In Testing3

Web chat widget for your website

Reservation & guest notes (Mews two-way) + internal note type

Add attachments to message composer

Released32

URL shortening for guest links

Auto-create alphanumeric sender ID per messaging profile

'Send Text' option to not re-open a closed conversation

Delays should trigger a data refresh

Stay-relative / recurring-within-stay trigger

Choose 'match any' vs 'match all' on trigger conditions

Trigger: same-day arrivals missing online check-in

Trigger: room status change -> alert the guest

Internal alerts & soft-fail flags in automations

Bulk add/remove tags in Contacts View