Travelers understand a Service when it describes a clear outcome rather than a broad promise to “help with anything.”
Build from a real traveler need
Identify the problem or experience: a half-day heritage walk, pre-trek planning, wildlife interpretation or transport-and-porter coordination. Use a title that names the outcome and place.
Define the scope
State:
- Who the Service suits
- Destination and duration
- Minimum/maximum group size
- What your work includes
- What the traveler pays or arranges separately
- Required fitness, equipment, permits or preparation
- Price basis and currency
- Conditions that may change the plan
Separate your responsibility
If another person or company provides transport, accommodation or support staff, say so. “Permit coordination” is not a promise that a government will issue a permit. “Weather dependent” should explain how changes are discussed—not remove every responsibility.
Make the next step clear
Tell the traveler what information to include in a request and what happens after submission. A request is not automatically a confirmed booking.
Before publishing, ask someone unfamiliar with the Service to explain it back to you. Any disagreement reveals a section that needs clearer wording.
