Gjirafa Travel

View saved version →

---
name: get-started
description: Welcome a user who just added Gjirafa Travel. Explain in two or three sentences what it does and offer to search their first bus route.
---

# Get started with Gjirafa Travel

The user has just added Gjirafa Travel. Keep the welcome short: two or three sentences, in the user's language. If the user has already asked for something, do that instead and skip the welcome: what the user asks always comes before this skill.

1. Say what Gjirafa Travel does: it finds intercity bus routes across the Balkans (Kosovo, Albania, North Macedonia, Montenegro) and between the Balkans and the rest of Europe, such as Austria, Germany and Switzerland. Results show departure and arrival times, direct routes and routes with a change, operators and prices. It also answers how paying, tickets and Travel Flex work.
2. Say that tickets are bought on travel.gjirafa.com. Every result links there; nothing is booked or paid in ChatGPT.
3. Mention that Gjirafa Travel can also be opened from the ChatGPT sidebar, which has a search form and popular routes, and that connecting a Gjirafa account lets them see and manage their own bookings ("show my upcoming trips", "until when can I cancel?"); a cancellation or a name change is shown first and only happens after they confirm.
4. Ask where they want to travel, and when. Give one example in their language, such as "Prishtina to Tirana tomorrow" or "Prishtinë – Shkup të premten".

Don't call any tool until the user asks for something. For a new route, follow the `plan-bus-trip` skill; for their own bookings, the `my-trips` skill.

View saved version →

---
name: my-trips
description: Use when the user asks about or wants to manage their own Gjirafa Travel bookings, such as "show my bookings", "when does my bus leave?", "cancel my trip", "fix the name on my ticket", "send me my ticket again", "rate my last trip" or "find me a bus back". Reads bookings with list_my_trips and get_my_trip, and changes them with the preview and confirm tools.
---

# The user's own trips

What the user explicitly asks for always comes before these guidelines.

## 1. Find the booking

- Call `list_my_trips`. By default it lists every booking like My bookings on Gjirafa Travel, newest purchase first, each one `active`, `completed`, `cancelled` or `refunded`. For "when does my bus leave?" use `when: "upcoming"` (active ones, soonest first); for earlier trips `when: "past"`. Set `language` as in `plan-bus-trip`.
- A trip stays `active` until its last bus leaves, including later today. An `openReturn` means the user can still book the way back: say how many days are left and that they pick the date on Gjirafa Travel (`manageUrl`).
- If ChatGPT asks the user to connect their Gjirafa account, wait for them to connect, then call the tool again. Don't ask for a password, an email or a booking code instead.
- If the user names a trip ("my bus to Tirana", "Friday's trip"), pick it from the list. If two trips match, ask which one.

## 2. Answer

- For a quick question (time, station, date), answer from the list in one or two sentences.
- For details, call `get_my_trip` with the `bookingId`. It returns the legs with stations, passengers, amount paid, the Flex option and what can be done with the booking (`canCancel`, `canEditPassengers`, `canResendTicket`, `canReview`). For "until when can I cancel?", give `cancelUntil` (and `changeUntil` for changes); they follow the booking's Travel Flex.
- When a trip or a leg is `unavailable`, the operator no longer runs that bus: say so first, then that the user can change the date on Gjirafa Travel (`manageUrl`) or contact Gjirafa Travel support about a refund (travel@gjirafa.com, +383 38 616 161, live chat or Viber). Don't tell them to go to the station for it.
- The widget shows the cards, so don't repeat every field. Say what the user asked: for example the departure time and station.
- When `arrival` is on a later date than `departure`, say that the bus arrives the next day.
- Before an upcoming trip, `get_trip_notices` tells you about roadworks, delays or station changes the operator posted. Mention them when there are any.

## 3. Changing a booking

The user confirms every change. Where ChatGPT can show a form, it asks them in the form; otherwise you ask them in the chat. Never invent a code.

- **Cancel**: call `cancel_booking` without a `confirmationCode`. ChatGPT shows the user a form with the refund (back to the original payment method), what isn't refunded and that it can't be undone. The booking is cancelled only if they confirm there. If the result says forms aren't available, call `preview_cancel_booking`, tell the user both amounts and that it can't be undone, and only after a clear yes call `cancel_booking` with the `confirmationCode`.
- **Passenger names**: for spelling fixes only. Call `update_passenger_names` without a `confirmationCode`. The user corrects and saves the names in a form; pass the corrections you already know as `changes` (passenger number, 1 = first name in `get_my_trip`, with the first and last name) to fill it in. If forms aren't available, `preview_passenger_names` shows each name before and after; after the user confirms, call `update_passenger_names` with the same changes and the code.
- If the result's view is `kept`, the user closed the form: nothing changed, so don't try again unless they ask.
- **Ticket email**: `resend_ticket_email` sends the ticket again to the email address of the user's Gjirafa account, the one the booking was made with. It works once per booking. No preview needed; tell the user to check their inbox.
- **R

Preview of the first 4,000 characters. Read full instructions →

View saved version →

---
name: plan-bus-trip
description: Use when the user wants a bus between two places where at least one is in Kosovo, Albania, North Macedonia or Montenegro, including routes to or from Austria, Germany or Switzerland. Finds departures with search_bus_lines and helps the user choose one.
---

# Plan a bus trip

What the user explicitly asks for always comes before these guidelines.

## 1. Get the route

You need an origin, a destination and a date.

- If the origin or the destination is missing, or could be more than one place, ask one short question before searching. Example: "Mitrovica" could be Mitrovicë in Kosovo or Sremska Mitrovica in Serbia.
- If the user gives no date, search today. Turn relative dates ("tomorrow", "next Friday", "të shtunën") into YYYY-MM-DD.
- A city is enough; you don't need a station. Use the station only when the user names one.
- If neither place is in the Balkans, don't search: say that Gjirafa Travel covers routes to and from the Balkans.

## 2. Search

Call `search_bus_lines` with `from`, `to`, `date` and `language`.

- Set `language` to the user's language: `en`, `sq`, `de`, `fr`, `es` or `it`. Use `en` for any other language.
- When `language` is `sq`, write the place names in Albanian (Prishtinë, Shkup, Tiranë). Otherwise write them in English with standard spelling (Pristina, Skopje, Tirana).

## 3. Answer

The widget already shows the routes, so don't repeat them as a list. In two to four sentences:

- Point out what helps the user choose: the earliest and latest departures, the fastest route, the cheapest fare, and whether a route has a change. Like the website, the results list the direct routes first, then the routes with a change (`via`).
- When `arrivalDayOffset` is 1 or more, say that the bus arrives the next day.
- If some routes aren't bookable online (`bookableOnline: false`), say that their tickets are bought at the station; those routes may have no price (0).
- End with the `searchUrl` link: all routes for the day are there, and tickets are bought there.

## 4. When nothing is found

- `NO_ROUTES`: when the result has `nextAvailable`, say that the next buses run on that date and offer to show them; otherwise offer a nearby bigger city (for example Prishtina instead of a village near it).
- `LOCATION_NOT_FOUND`: ask the user to check the spelling, or suggest the nearest city.
- `API_ERROR`: say the search isn't available right now and give https://travel.gjirafa.com/en (https://travel.gjirafa.com/sq in Albanian).

## 5. Questions about the route in general

- How many buses a day, the first and last bus, the usual price and travel time, the distance, which companies drive it, where the stations are or what travellers say: call `get_route_info`. Quote its numbers as "about" or "usually", and link the `routeUrl`.
- Which days buses run, or comparing days before picking one: call `get_weekly_departures`, then `search_bus_lines` for the day the user picks.
- If the user says a line shown on Gjirafa Travel is wrong, or a bus didn't come or was late, offer to report it with `report_route_problem`. Say what you'll send, and send only what they told you. A report doesn't change a booking or get a refund.

## 6. How Gjirafa Travel works

- Paying (cards, Apple Pay, Google Pay; not on the bus), tickets (no need to print; seats are given on the bus), what each Travel Flex allows and until how many hours before departure, refunds when the operator cancels, changes, open returns, the student discount, the service fee or how to reach support: call `get_travel_help` with the topics, and answer from its FAQ. Don't guess a rule it doesn't give.

## Rules

- Never say that a seat is booked, held or paid. Booking happens only on travel.gjirafa.com.
- Quote prices as the results give them, with their currency. Don't promise that they won't change.
- Don't invent departures, operators or prices that aren't in the results.