Communication & Inbox

Why Experience Hospitality Needs a Purpose-Built Inbox

A surf camp in Taghazout receives a booking inquiry on Instagram at 10 PM, a dietary-restriction update over WhatsApp at 7 AM, an airport-transfer question via the website chat widget at noon, and a group-discount request by email later that afternoon — all from the same guest, across four channels, handled by three different staff members on three different devices. Without a unified system, the morning shift has no idea what the night shift promised on Instagram, the transfer request sits unanswered in a personal WhatsApp thread, and the group-discount email gets buried under supplier invoices in a shared Gmail account.

This is the daily reality of guest communication in experience hospitality, and it's fundamentally different from traditional customer support. Intercom and Zendesk are designed for SaaS companies where support tickets follow predictable patterns — bug reports, billing questions, feature requests. A surf camp's inbox is a messy blend of pre-arrival logistics, mid-stay coordination, post-checkout feedback, and marketing inquiries, often in multiple languages, with context that depends on the guest's booking, room assignment, activity schedule, and dietary preferences. Generic support tools don't understand any of this context.

Artidal's Communication & Inbox module was built specifically for this reality. Every message, regardless of channel, flows into a single team inbox where it's automatically linked to the guest's profile, their current or upcoming booking, their room assignment, and their activity schedule. When a staff member opens a conversation, they see the full picture — not just the message thread, but everything the property knows about that guest.

Omnichannel Aggregation with Full Context

The inbox aggregates six channels into one interface: email (with full threading and attachment support), WhatsApp Business API (including template messages for booking confirmations and payment reminders), Instagram Direct Messages (so social-media inquiries don't live in a separate app on someone's personal phone), a brandable web chat widget that embeds on your booking site, SMS for markets where WhatsApp penetration is low, and push notifications through the Guest App for on-property communication.

Each channel maintains its native formatting and capabilities — WhatsApp messages show read receipts, Instagram threads preserve image attachments, email replies thread correctly — but all conversations are visible in the same unified view. A guest who starts on Instagram, switches to email for booking details, and then uses WhatsApp for day-of logistics appears as a single continuous conversation, not three disconnected threads.

Every message is automatically enriched with the guest's CRM data: their booking dates, room assignment, package type, dietary requirements, past stays, and lifetime value. When a returning guest sends a message, the agent immediately sees their history — previous stays, feedback scores, any unresolved issues from past visits. This contextual awareness transforms every interaction from a cold support ticket into a warm, informed conversation.

Ticketing, SLAs, and Agent Assignment

Unstructured messaging becomes manageable through a ticketing layer that adds accountability without adding bureaucracy. Every conversation can be assigned a priority (urgent, high, normal, low), an SLA timer (configurable per priority level — e.g., urgent replies within 15 minutes, normal within 2 hours), and an assigned agent. When an SLA is about to be breached, the system escalates automatically — reassigning to a manager or sending a push notification to the assigned agent.

Agent assignment can be manual (a team lead triages and assigns) or automatic (round-robin across online agents, skill-based routing for specific languages, or channel-based routing where WhatsApp queries go to the front-desk team and email inquiries go to reservations). For small teams, the round-robin approach ensures equitable workload distribution. For larger operations with specialized roles, skill-based routing ensures the right person handles the right query.

Canned responses accelerate replies for common questions — directions to the property, check-in procedures, equipment requirements, cancellation policies — while maintaining a personal tone. Each canned response supports dynamic variables (guest name, booking dates, room type) so the reply feels personalised rather than robotic. The team library of canned responses grows organically as staff save their best replies, creating institutional knowledge that survives staff turnover.

CSAT, Sentiment Analysis, and Broadcast Channels

After a conversation is resolved, guests receive a satisfaction rating prompt (configurable per channel) that feeds into agent-level and team-level CSAT dashboards. Over time, this creates a data-driven view of communication quality — which channels produce the highest satisfaction, which agents consistently receive top ratings, and which types of queries correlate with lower scores.

Sentiment analysis runs on every incoming message, flagging negative-sentiment conversations for priority attention. When a guest sends an angry message about a missed transfer or a room issue, the conversation is automatically bumped in priority and highlighted for the team lead. This early-warning system catches service-recovery opportunities before they become negative reviews on TripAdvisor or Google.

Broadcast channels allow one-to-many communication — weather updates, schedule changes, event announcements — sent to targeted groups of guests. A surf camp can broadcast 'Flat conditions tomorrow — we've arranged a day trip to Paradise Valley instead' to all guests currently checked in, via their preferred channel. Broadcasts respect GDPR opt-out preferences, ensuring guests who have opted out of marketing communication still receive operational messages, while promotional broadcasts are suppressed.

The GDPR compliance layer manages consent at the channel level — a guest can opt in to WhatsApp operational messages but opt out of email marketing, and the system enforces these preferences automatically. Consent records are maintained with timestamps and audit trails, giving operators confidence in their compliance posture when regulators come knocking.

Why Not Just Use Intercom or Zendesk?

Intercom costs $39–$139 per agent per month and was designed for SaaS product support — it excels at in-app chat and help centres for software users, but it doesn't understand bookings, rooms, guest profiles, or hospitality workflows. Connecting Intercom to your PMS, your booking engine, and your activity scheduling system requires custom integrations that are expensive to build and fragile to maintain. Even then, the agent sees a bolt-on data panel, not native context.

Zendesk is the enterprise incumbent, powerful but complex — most experience hospitality operators are overwhelmed by its configuration options and never unlock its value. Neither platform supports WhatsApp Business API natively without third-party add-ons, neither links conversations to hospitality-specific entities like bookings and room assignments, and neither provides the broadcast functionality needed for on-property group communication.

Mailchimp and ActiveCampaign operate in the marketing automation space — they're great for newsletters and drip campaigns but don't provide real-time conversational messaging or ticketing. The result is that most operators use a Frankenstein stack: Zendesk or Intercom for support, Mailchimp for marketing, WhatsApp Business on a personal phone, and Instagram through the native app. Artidal replaces all of this with a single, hospitality-native inbox that understands your business.