Structured request

Send one structured activity request so the answer can match your base, date, group, travel time, and limits.

The first message should show where you are staying, when you want to go, which activity or route interests you, and what would make the option too far, too intense, or unsuitable.

Short answer: The main Active request channel is WhatsApp, but the message should carry enough context to be useful. Include base location, date, group size, activity preference, possible place or route, travel tolerance, intensity, children or constraints, and preferred language. If the request started because paragliding is not flyable, say whether you want a later flight window or a separate plan B such as canyoning or diving. Active can then route it to the right activity owner, a responsible local contact, a current manual check, or guidance only for now.

Open WhatsApp request

Request guidance

Check fit before contact

Handling path Chooser, then routed next step
Next step Send a structured request
Route detail status General guidance — confirm current details
Review status Check current details first; reviewed 2026-07-01

Marina Pavicevic — online support staffs WhatsApp +382 69 994 557 for structured routing. Portfolio-owner handoff is live in Phase B; partner/manual route checks remain current-detail confirmation, not booking.

Start here when

  • Structured inquiry Use after you can provide base, date, group, preferred activity or route, travel tolerance, intensity, and constraints.
  • Unclear activity fit Return to the chooser if you cannot yet describe the kind of outdoor activity you want.

Limits that keep the answer honest

  • A WhatsApp message is a routing request, not confirmed participation.
  • Contact channels stay hierarchical instead of becoming equal noise.

Request path

Structured request path

Use the request page only after fit context is clear enough to route honestly.

1

Bring fit context

Base, date, activity preference, route or place if known, travel tolerance, intensity, and constraints.

2

Send a structured request

WhatsApp opens with the fields needed for routing, not as a bare availability ping.

Request checklist

What the request should include

WhatsApp comes after fit context, not as a flat messenger wall.

One prepared WhatsApp request collects base, route or place, and travel fields needed for responsible routing.

The next route stays visible before anyone treats the message as confirmed participation.

Request fields

Ask with enough context for a real answer

The first message should make activity fit clear enough to decide who should handle the next step.

Trip context

Base location, date or period, time available, number of people, adults or children, and language.

Place or route context

Preferred place, route, canyon, river section, beach point, dive area, or operating area if you already know one — for example Rikavac, Međurečki, Škurda, Nevidio, Grlje, Bogutovski, Vruća Rijeka, or Drenovštica for canyoning.

Travel context

Whether the group wants a near-base activity, accepts a longer transfer, or is open to either, plus maximum comfortable travel time.

Activity context

Preferred activity or open choice, environment preference, intensity, first-time or experienced, and whether this is a normal activity request or a non-flying plan B after paragliding was not suitable.

Suitability context

Fear of heights, swimming confidence, mobility, health note, children, time limit, and any strong preference.

Contact context

WhatsApp +382 69 994 557 is primary once you can include base, date, group, activity preference, and constraints. Form or email can stay as fallback later, but not as equal messenger noise.

A submitted request is not confirmation of availability, participation fee, operator, route, or safety suitability.

Primary WhatsApp request

The main Active request channel is WhatsApp at +382 69 994 557. Use the prepared request button so the first message carries enough context for a real answer.

Use it as a structured request, not as a confirmation message. The first message should make fit clear enough to decide whether the next step is an activity owner, a responsible local contact, a current manual check, or guidance only for now.

Request message specification

The prepared message collects:

  • current or planned base
  • near-base preference or willingness to travel
  • maximum comfortable travel time
  • date or travel period
  • number of people
  • adults, children, or mixed group
  • preferred activity or open choice
  • whether the request started because paragliding was not flyable, and whether the group wants a later flight window or a separate plan B
  • preferred place, route, canyon, river section, beach point, dive area, or operating area if known
  • preferred environment: air, sea, river, mountain, off-road, calm nature
  • intensity: calm, moderate, strong
  • first-time or experienced
  • constraints: height fear, swimming confidence, mobility, health note, children, time limit
  • preferred contact channel
  • language
  • short message

A useful request clarifies the right owner, route, activity family, current-detail burden, or guidance-only status. It should not pretend that every listed activity is available or handled from here.

Quick answers

Decisions before contact

What should the request promise?

Routing and current-detail clarification — not instant booking unless that system actually exists.

What happens if the activity is not handled?

The response should say so plainly and keep you in guidance-only mode or route to a responsible contact if one exists.

What if the activity has several possible places?

The request should capture your base, preferred route if known, and maximum travel time before recommending a place.

Should WhatsApp be primary?

Yes, on this request page WhatsApp is the primary channel, but it should open as a prepared context message rather than a bare "is it available?" ping. It is still routing and current-detail clarification, not confirmation.

Next route

Continue only where the intent fits