Wetu Voice Implementation Roadmap for Hotels and Tour Operators: The First Month

Week 1: Map the Guest Journey and Pick Your First Use Cases

Before recording a single message, gather the people who own guest communication. In a typical Ugandan hotel or tour operation, that means the front office manager, reservations lead, marketing or communications officer, and whoever handles compliance or data consent. If you run a smaller lodge, the general manager may wear several of these hats.

Start by listing every point where your team currently calls, texts, or messages guests manually. Common touchpoints include:

• Booking confirmations and deposit reminders
• Pre-arrival directions, check-in times, and what to pack
• On-stay check-ins ("Is everything comfortable?")
• Post-stay feedback requests and review prompts
• Loyalty programme updates and birthday offers
• Seasonal promotions (Christmas packages, low-season discounts)
• Payment reminders for corporate accounts or group bookings

For each touchpoint, note the current channel (phone call, WhatsApp, SMS), who sends it, how long it takes, and where follow-up falls through. A front desk agent might call 20 guests to confirm arrival times, reach 12, leave voicemails for 5, and forget to retry the other 3. That gap is your first automation candidate.

Pick one or two high-volume, low-complexity use cases for the pilot. Booking confirmations and post-stay feedback are ideal — they follow a script, need consistent delivery, and benefit from memory (the agent remembers the guest's name, dates, and room type). Avoid complex negotiations or complaint resolution for now; those still need a human.

Deliverable by end of week: A signed-off list of pilot use cases, the guest segments involved (e.g., "all direct bookings for next 30 days"), and the internal owner for each.

Week 2: Build the Knowledge Base and Record Messages

Wetu Voice agents answer questions from your business knowledge. That knowledge lives in a structured FAQ you provide — think of it as the agent's training manual. Sit down with reservations and front office to document the 30–50 questions guests ask most often:

• Check-in/check-out times and early arrival policy
• Airport transfer options and costs
• Wi-Fi availability and password process
• Restaurant hours, dietary options, and room service menu
• Pool, spa, and activity schedules
• Cancellation and amendment policies
• Loyalty programme tiers and redemption
• Nearby attractions, transport, and safety tips

Write answers in plain English, the way your best front desk agent would speak them. Keep each answer under 30 seconds when read aloud. Organise them into categories (Arrival, Facilities, Policies, Local Area) so the agent can navigate them logically.

Now record the outbound messages. Wetu Voice delivers the same recording across voice call, SMS, and WhatsApp — so script for the ear, not the eye. A booking confirmation might sound like:

"Hello [Guest Name], this is Sarah from [Lodge Name]. We're looking forward to welcoming you on [Arrival Date] for [Number] nights in a [Room Type]. Check-in is from 2 pm. Our driver will meet you at Entebbe Airport at [Time] holding a [Lodge Name] sign. Reply YES to confirm or call us on [Number] if anything changes. Safe travels."

Record in a quiet room using a decent USB microphone or the voice memo app on a recent smartphone. Aim for warm, clear, unhurried speech. Make three versions per message: English, Luganda, and Kiswahili if your guest mix warrants it. Wetu Voice lets you assign languages per contact.

While recording, prepare your consent lists. Ugandan data protection law and Wetu Voice's built-in checks require evidence that each contact agreed to receive automated messages. Pull opt-in records from your booking engine, check-in forms, and loyalty sign-ups. Tag each contact with source, date, and channel consent (voice, SMS, WhatsApp). If a segment lacks clear consent, exclude it from the pilot.

Deliverable by end of week: Uploaded FAQ document, recorded message library (named and tagged), and cleaned consent list in CSV format ready for import.

Week 3: Pilot Launch — Test, Listen, Adjust

Import your pilot segment (e.g., 150 direct bookings arriving in the next two weeks) into Wetu Voice. Set the campaign to send the booking confirmation recording 48 hours before arrival, with a fallback SMS for numbers that don't answer the call. Enable quiet-hour blocking (default 9 pm–8 am) and opt-out handling — guests who press 1 or reply STOP are automatically suppressed.

Assign the campaign to a single internal owner — usually the reservations lead — who will monitor the dashboard daily. Key metrics to watch:

• Reach rate: Percentage of contacts reached on first attempt
• Channel split: How many answered via voice, SMS, WhatsApp
• Opt-out rate: Should stay under 2% for transactional messages
• Reply types: Guests confirming, asking questions, requesting changes
• Agent handoffs: How often the AI escalates to a human (and why)

Listen to the first 20 call recordings. Are guests hearing the full message? Do they interrupt with questions the agent can't answer? Note gaps in your FAQ. If three guests ask about early check-in fees and the agent deflects, add that to the knowledge base.

Hold a 15-minute stand-up with the pilot team at day 3 and day 7. Share what the dashboard shows and what the recordings reveal. Adjust timing (maybe 72 hours pre-arrival works better), refine the script (shorten the intro), or expand the FAQ. This iterative loop is where the system learns your operation.

Deliverable by end of week: Pilot performance summary (one page), updated FAQ, and a go/no-go decision for scaling.

Week 4: Expand, Integrate, and Hand Over

With a successful pilot, widen the net. Add the next use case — post-stay feedback sent 24 hours after checkout. Use the same consent list but filter for guests who completed their stay. The agent now has memory: it knows the guest's name, dates, room type, and that they received the pre-arrival call. The feedback message can reference that context:

"Hello [Guest Name], Sarah again from [Lodge Name]. Hope you enjoyed your stay in the [Room Type] from [Dates]. We'd love 30 seconds of your time — press 1 to rate your experience, or tell us what we could improve. Your feedback helps us serve you better next time."

Now involve IT or your property management system (PMS) vendor. Wetu Voice can pull guest data via API or scheduled CSV export from most PMS platforms used in Uganda (Opera, Protel, local builds). Map fields: guest name, phone, email, arrival, departure, room type, booking source, loyalty tier. Automate the daily sync so new bookings enter the confirmation campaign without manual uploads.

Define escalation rules for the agent. When a guest asks something outside the FAQ — "Can I extend my stay?" "I lost my luggage." "My AC isn't working." — the agent should:

1. Acknowledge the request
2. Log the query with full context
3. Notify the front office via WhatsApp group or email
4. Tell the guest: "I've alerted our team; someone will call you within 15 minutes."

Test the escalation path with your front desk team. Run a fire drill: have a colleague call in with a tricky question, verify the alert reaches the right person, and confirm the follow-up happens.

Document everything in a runbook — a living Google Doc or Notion page — covering:

• Campaign schedules and segments
• Message scripts and language assignments
• FAQ update process (who approves, how often)
• Consent management (how new opt-ins are added, how opt-outs flow back to PMS)
• Escalation contacts and SLAs
• Dashboard review cadence (weekly for first month, then monthly)

Assign a system steward — someone who owns the runbook, runs the weekly review, and coordinates with FTA support when needed. This is usually the reservations lead or marketing officer, not the IT person.

Deliverable by end of week: Live multi-campaign setup, PMS integration running, runbook published, steward named.

Ongoing: Monthly Rhythm and Continuous Improvement

After the first month, shift to a monthly rhythm:

First Monday of each month — Steward pulls dashboard export: total sends, reach rate, opt-out rate, top 10 FAQ triggers, escalation volume and resolution time. Share with GM and front office manager.

Second week — Front office reviews top unanswered questions. Steward updates FAQ. Marketing proposes new campaigns (Easter packages, conference season, referral incentives).

Third week — Steward tests new messages on a 5% sample, checks recordings, deploys if clean.

Fourth week — Consent audit: cross-check Wetu Voice opt-out list against PMS marketing flags. Resolve discrepancies.

Quarterly, invite FTA's product team for a 30-minute review. They'll share platform updates (new channels, analytics features, language models) and help you map them to upcoming hospitality seasons.

Who Stays Involved — and When

Role	Week 1	Week 2	Week 3	Week 4	Ongoing
General Manager	Approve use cases	—	Review pilot go/no-go	Sign off runbook	Monthly dashboard review
Front Office Manager	Map touchpoints	Provide FAQ content	Monitor escalations	Define escalation SLAs	Weekly escalation audit
Reservations Lead	Identify pilot segment	Record messages, clean consent	Own pilot dashboard	Configure PMS sync	Campaign steward (ongoing)
Marketing/Comms	Suggest promotional use cases	Script promotional messages	—	Plan quarterly campaigns	Quarterly campaign calendar
IT / PMS Vendor	—	—	—	Build API/CSV integration	Maintain integration, security patches
Compliance / Legal	—	Verify consent records	Confirm opt-out handling	Audit consent quarterly	Annual data protection review

Common Pitfalls to Avoid

Don't automate everything at once. Teams that launch five campaigns in week 1 drown in edge cases. One use case, one segment, one language — master the loop, then expand.

Don't skip the consent audit. A single complaint to the Personal Data Protection Office can pause your entire channel. If you're unsure about a list's provenance, leave it out.

Don't treat the agent as set-and-forget. Guests ask new questions every season ("Do you have EV charging?" "Is the pool heated?"). The FAQ grows; the agent improves. Schedule the update time.

Don't ignore the human handoff. The agent's job is to handle the repeatable 80% and gracefully escalate the 20%. If escalations stall at the front desk, guests lose trust. Build the SLAs and monitor them.

Ready to Start?

You now have a week-by-week plan, a responsibility matrix, and a sense of the monthly rhythm. The next step is a scoping call with FTA's team — they'll walk through your PMS, consent records, and pilot segment to confirm the technical setup. No commitment, just clarity.

Explore Wetu Voice →