Automated guest-journey flows and one-off broadcasts, same templates, same segments, same opt-in store.
Replies go to your AI Operator and Team Inbox, just like any other guest message.
.png)
Whether the trigger is a guest journey event (booking confirmed, day of arrival, day after checkout) or a scheduled send, you're using the same templates, the same segments, the same opt-in store, and the same reply routing.
Choose send-now or scheduled delivery. Review each campaign's audience count and preview before it goes out. Save drafts, duplicate past campaigns as starting points.
"Viqal has reduced our workload and improved guest experience. Guests are pleasantly surprised when they receive the initial welcome message with detailed information in their native language."
The first message lands 48 hours before check-in — branded, on WhatsApp, in the guest's language. Use Flow templates to capture arrival time, dietary preferences, transfer requests; or simple welcomes that link to digital check-in. Fewer lobby questions. A guest who feels expected.
Time-aware nudges for the moments that drive revenue and reviews — restaurant carousels at 17:30, spa availability at 11:00, breakfast hours each morning. Each template ties into the rest of Viqal: a tap on “Reserve a table” opens a conversation in Team Inbox; a booking posts to the folio.
The day after checkout, ask one good question — and route the answer where it should go. Happy guests get a one-tap CTA to your TripAdvisor or Google review. Anything below that quietly opens an internal thread for the GM. The right outcome, every time.
Start with a status window — in-house, arriving, past guests — then narrow with a significant amount of segmentation options, including PMS-based ones: room type, language, loyalty tier, booking source. Counts update live from your PMS.
Any moment in the guest journey. Triggers fire relative to a reference point in the booking — e.g. 3 hours after booking, 2 days before arrival, the morning of day 2, 24 hours after checkout. Reference points are PMS-driven (reservation created, arrival, departure) so each guest only gets what applies to their actual stay.
Only marketing templates need Meta approval, and they generally come back within a few minutes — occasionally up to 24–48 hours for edge cases. Transactional and utility templates (check-in, arrival info, post-stay review, etc.) do not require approval and go live immediately. You can also use a Viqal-owned WhatsApp account that's ready to go on day one if you don't want to set up your own Meta business account yet.
Yes. Every message includes a native “stop” option and opt-outs are honored across all future flows — the guest still gets transactional messages (check-in, room-ready) unless they opt out of those too.
200+ languages. We detect the guest's language from the country code in their phone number or, when available, from the PMS profile — then send in that language. Staff writes once, Viqal delivers it localized.
A significant amount of segmentation options, including any PMS-based field your property maintains — booking source, room type, rate code, stay length, loyalty tier, language, arrival/departure date, past-stay count. You can also combine behavioral signals (opened, replied, booked upsell).
Sent, delivered, read, replied, and attributed revenue (for upsell touchpoints). Broken down by segment, template, and touchpoint. Exports to CSV or your BI tool.
.avif){kind=spacer}
