Video summary

Working with Experiences in Wetu: Activities, Day Tours, Private Profiles and Catalogs

Main summary

Key takeaways

Business

Core purpose & customer needs addressed

  • The session focuses on improving clarity and workflow for adding activities/experiences to itineraries—specifically:
    • which Wetu tool to use,
    • when to use it,
    • how to reuse content efficiently.
  • Emphasis: clients are buying curated experiences, so the chosen method affects:
    • itinerary appearance,
    • routing accuracy,
    • marketing output.

“Playbook” framework: 6 ways to add experiences to an itinerary

Wetu describes six methods, each suited to different scenarios (preloaded supplier content vs. custom/bespoke content vs. database search vs. reusable profiles).

1) Product Activities (supplier-linked, preloaded)

  • Appears only when using a supplier whose experiences/services are already preloaded.
  • Workflow:
    1. Select via dropdown
    2. Add to the planner
    3. Set experience type as inclusion / optional / recommended
  • Example:
    • Singita Sabi Earth Lodge with preloaded safaris (e.g., walking safaris, community tours) and Amani Spa.

2) Components (reusable, structured building blocks)

  • “Curated pieces of information” stored at the account level for quick reuse.
  • Workflow:
    • Click Add component → pulls in experiences + pre-measured notes together.
  • Goal:
    • reduce manual work when you routinely add similar content.

3) Day Tours (structured sets published by day tour providers)

  • Workflow:
    • choose Day Tours → search (by name or often by operator) → preview first.
  • Preview supports decision-making by showing:
    • inclusions,
    • duration,
    • points of interest,
    • routing/map outline.
  • Add to itinerary:
    • click Add day tour → includes the provider’s packaged details.
  • Example handling:
    • preview provides operator contact info to confirm availability/book directly.
  • Quality check:
    • expected to be green-highlighted before adding.

4) Database Activities (global search in Wetu activity database)

  • More manual:
    • use Add activity search and select from global results.
  • Key operating rule:
    • ensure the selected experience matches the destination you are selling so routing remains accurate.
  • Example:
    • searching for Shokage Diving and selecting the correct supplier/experience from global matches.

5) Free text activities + Geotagging (quick bespoke when no profile needed)

  • Use when:
    • the activity isn’t in the Wetu database, and you want a one-off entry or custom wording.
  • Workflow:
    1. choose Save as free text
    2. (note) by default, there are no images/descriptions
    3. add geotag/location so output aligns with the correct destination/property (e.g., “Gold Restaurant”).
  • Tradeoff:
    • faster creation, but you must rely on geotag for contextual presentation.

6) Private Profiles (reusable bespoke content, account-scoped)

  • Best for:
    • unique activities you don’t want others to use publicly.
  • Workflow:
    • create a Private Profile → later search by name in the itinerary builder.
  • Visibility:
    • private profiles are marked with blue “private profile” labeling to distinguish from Wetu-provided database content.

Private Profile creation workflow (operations + content governance)

Presented by Chantal (with earlier examples mentioned from Venant/others).

Setup flow (step-by-step)

  1. Go to Content solutions → open Profiles
  2. Click Create profile
  3. Choose build approach:
    • Smart Build (AI-based URL ingestion; presenter encourages testing)
    • Self-build (manual process demonstrated)
  4. Select profile type (e.g., stays, food & beverage, destination, activities / “things to do”)
  5. Provide:
    • Unique name
    • Description (short marketing-style intro)
  6. Add location:
    • street address, or lat/long, or moving map pin
    • routing accuracy depends on pin placement (pin should match where the entrance/activity occurs)
  7. Add required destinations:
    • requires 3 destinations
    • one auto-populates based on location; add two more
    • recommendation: use city-level destinations for relevance/accuracy
  8. Select facilities/services offered + connectivity options
  9. Add languages spoken by staff
    • affects staff languages, not necessarily translations
  10. Add up to 6 images:
    • must have usage rights/copyright permissions
    • include image credits/titles
    • reorder images and set the first (“best”) image as main
  11. Finalize with activity options (offerings within the profile):
    • add activity name + description
    • set inclusion type (e.g., optional)
    • add images for each option
  12. Publish:
    • for private scope, choose Private profile publish mode
    • status shows as active after successful publishing
    • duplicates: if flagged as duplicate, Wetu support may contact you for corrections

Concrete example in the session

  • Adventure” activities profile created as a Private Profile, including:
    • location via street address + pin accuracy check
    • destination allocation via suggested nearby destinations
    • images added (with credits and ordering)
    • at least one activity option (e.g., archery/shoot targets) with inclusion type and images

Catalog Manager workflow (marketing distribution + safe sharing)

Presented by Chantal/Shanae (catalog details mainly explained by Shanae).

What catalogs are used for

  • Create a single shareable link that bundles multiple offerings for marketing (e.g., itineraries, day tours, eye brochures/accommodation content).

Catalog constraints / governance

For marketing/bulk sharing, catalogs allow only:

  • out of itineraries
  • sample itineraries (not personal itineraries) to avoid exposing client details
  • also allowed:
    • day tours
    • multi-day tours
    • eye brochures (accommodation content)

Catalog build steps

  1. Go to Catalog Manager → create new catalog (Add)
  2. Set:
    • Catalog name (heading)
    • Language (must match content language being added)
  3. Add chapters (“sections”):
    • define chapter heading + content type (e.g., itineraries)
  4. Add content items via Add item:
    • search for samples using name, reference, or category
  5. Save:
    • the generated link remains the same and is live-updated as content changes
  6. Share distribution:
    • embed/share via newsletters, websites, social media, or directly with travelers

Catalog presentation customization (actionable detail)

  • Choose output theme such as Classic vs Discovery
  • If two offerings from the same destination repeat an image:
    • use change picture to set a different display image
    • save changes and refresh to see updated visuals

KPI / metrics

  • No business KPIs (revenue, CAC, LTV, churn, timelines, conversion targets) were stated.
  • The session is primarily product workflow enablement rather than performance measurement.

Actionable recommendations (based on what was taught)

  • Choose the right experience method based on content source:
    • Product Activities → supplier-preloaded offerings
    • Components → internal reusable blocks
    • Day Tours → structured, previewable provider packages (routing/inclusions clarity)
    • Database Activities → scalable search, but strictly validate destination match for routing accuracy
    • Free text + Geotagging → fast one-off wording/location context
    • Private Profiles → reusable bespoke content kept account-private
  • For private profiles, prioritize:
    • location pin accuracy for correct routing
    • city-level destination allocation for relevance
    • image rights compliance and strong ordering (best image first)
  • For catalogs:
    • always use sample itineraries to avoid leaking personal client data
    • align catalog language with content language
    • use chapter structure + image swaps to differentiate similar destination offerings

Q&A highlights captured

Duplicate a quote instead of redoing?

  • Yes: use itinerary library/browser copy options to create duplicates quickly from core components.

Do includes/excludes show on Discovery view?

  • No: by design, includes/excludes do not show in Discovery output; they are incorporated into itinerary main or day-by-day inclusions/exclusions.

“Smart Bold URL cannot open”

  • Check the URL format includes https://.
  • If correct, route to support for investigation.

Difference between day tours and day components

  • A prior lab/video was referenced for full distinction; it wasn’t fully explained in this transcript.

Presenters / sources (as mentioned)

  • Barbara — Head of Customer Experience, Wetu
  • Zulfa — chat host
  • Venant — demonstrated the six methods of adding experiences
  • Chantal — demonstrated private profile creation (and related Q&A)
  • Shanae — contributed to Catalog Manager and later question context
  • Renate — brought back near end for wrap/recap context
  • Arnault — referenced earlier work/lab on components
  • Fermand (Fernand) — answered Q about duplicating quotes
  • Vernon — answered Q about Discovery includes/excludes behavior

Original video