Glossary
Omnichannel Decision Mesh
Consider a fictional coastal heritage route. A traveller discovers it through a short video and wants to visit in October without a car. A destination guide explains the places, but the decision also depends on transport, museum visiting conditions and the return journey.
The useful answer is spread across several sources. The visitor needs to understand which source answers each question and how the information fits together.
The Omnichannel Decision Mesh is Tamaga’s model of the connected pages, channels, sources and people that help a traveller make a decision while keeping relevant conditions and responsibility clear.
Connect each question to an appropriate source
For the fictional October visit, different sources contribute different answers:
| Source | Question it helps answer |
|---|---|
| Destination guide | What does the route involve, and how might its places, terrain and pace suit this visit? |
| Transport provider’s current information | Which services cover the intended date, and what return options need checking? |
| Museum’s visitor information | When can someone visit, which entrance applies and whether advance reservation is required? |
| Guided-visit operator or booking page | What arrangements are offered, which terms apply and what still needs confirmation? |
A visitor can enter through any of these sources. The next useful question determines where they should continue.
For example, a passage in the route guide could explain:
For an October visit, check the autumn return timetable before choosing your museum time.
That gives the reader a reason to follow the connection. Use consistent names for the places and services so they remain identifiable across the different explanations.
Give each channel a useful job
A newsletter can explain why October deserves consideration. A short video can show the terrain. The maintained guide can bring the practical questions together and direct readers to current transport, visiting and booking information.
Each version should preserve the conditions that affect its message. A video presenting the route as a car-free visit needs to retain any important transport qualification, even when the full timetable belongs elsewhere.
Choose the channels your audience uses and the versions you can maintain. A useful mesh can begin with a few well-connected explanations.
Keep responsibility visible when information changes
The destination organization may maintain the route guide. The transport provider maintains its timetable. The museum establishes its visiting arrangements. An operator handles a particular guided-visit request.
A public description can explain these relationships without taking over every decision. Where published information answers the question, make that answer easy to find. Where an arrangement remains unresolved, explain what needs checking and who can respond.
If a timetable changes, update the guide and any reusable introductions you maintain. Request corrections to outdated partner descriptions and retain unresolved differences. Updating your own page does not establish that an external listing or AI answer has changed.
Recurring visitor questions can reveal an unclear connection. If people reach the museum information but still miss its reservation requirement, review the passage leading there, retain the condition in relevant introductions and check the path again.
Where the concept comes from
Tamaga develops the Omnichannel Decision Mesh in One Hotel, Seven Versions, drawing on Bourrelly’s audience-led semantic architecture and omnichannel work, alongside Méline’s emphasis on intention and lexical continuity.
The paper examines accommodation. The coastal-route example here illustrates a broader tourism application; it is not an observed research case.
Use the Topical Mesh method to clarify page responsibilities and useful continuations in your own content. Read Source-to-Service Chain when the question concerns how information connects with an offer, confirmation, action or recovery.