Skip to content
ViaMore The road is better, together.

Ask ViaMore

User guide index

Ask ViaMore answers questions about your saved trips and explains how to use the application. It is available to signed-in users when the site's operator enables it and the responsible account has AI allowance available.

Start a conversation

  1. Select Ask ViaMore in the top navigation. It opens beside your page on a wide screen and fills the screen on a phone. Opening and closing it preserves unsaved work on the page.
  2. Check the visible context: Using ViaMore or Trip: <name>. A first conversation opened from a supported trip screen preselects that trip. The trip picker offers your latest 100 accessible trips, including past trips, plus the current or resumed trip when it is older than that selection.
  3. To change context, select application help or a trip, then select New conversation. Choosing a different option alone does not switch the current conversation. An existing conversation keeps its context when you navigate.
  4. Read whose AI allowance applies, enter your question and select Ask.
  5. Follow the supporting record or guide links and check the saved details before acting. You may be asked to confirm leaving a page with unsaved changes.

Examples: Where are we staying on 2026-10-02?, What still needs review?, What are we cooking tomorrow?, or How do I invite a Planner?. Questions such as What about Saturday? use your conversation context. When a weekday could refer to several dates, supply the actual date. Relative dates use the trip's saved planning time zone when available, otherwise the browser's supplied zone.

Understand the answer

Answers use current saved records and the user guide. They do not check airlines, booking providers, prices, availability or websites. A missing reservation record does not prove that no real booking exists. Partial results and missing information should be stated; ask a more specific question or date to narrow a large trip.

Trip meal answers use shared recipe copies. Your personal recipe library and photos are not shared with other travelers through the assistant. Shopping answers use shared shopping information. Changed requirements may need Refresh from meals, or explicit approval of pending additions and quantities in shopping review mode, by an Owner or Planner. See food planning.

Change a trip day or overnight stay

Trip Owners can explicitly request changes to existing days or overnight stays in the selected trip. For example: Set the title of the first day to Arrival, Change the day type on 2026-10-02 to Relaxation, or Set the Lakeside overnight stay's planning status to Selected. Requests save directly after validation. The reply lists the saved changes; refresh the trip page to see them.

You can apply the same property changes to multiple records at once. For example, Change all Trip Day Types from May 3 to May 9 to Explore updates all seven days, including both endpoints. The year comes from the selected trip when unambiguous; otherwise provide the year. Set the Lakeside and Mountain overnight stays to Selected updates both stays. Specify unique names or dates when needed.

A batch supports up to 100 records and saves as a unit. If a date is missing, a record changed while the reply was being prepared, or any change is invalid, none of the batch is saved. Day ranges include every saved day in the requested range even when the chat's ordinary source excerpts omit some days. For large stay lists, narrow the request if the assistant lacks complete saved evidence. Each batch sets the same values on its selected records; requests to append text to differing existing notes should be made separately. A protected Going Home day retains its effective Travel type even if its saved day type selection changes.

Day edits support title, location, day type and notes. Stay edits support location, address, coordinates, overnight type, arrival and departure dates, planning status and notes. Unspecified properties are preserved. Ask explicitly to clear an optional property. Supply both coordinates when changing a stay's coordinates; changing its location or address without coordinates clears the old coordinates. Arrival is inclusive and departure exclusive. Changing stay dates preserves actual reservation dates and may flag linked reservations for review.

Use a date or unique stay name to identify the record. Ambiguous requests receive a clarification. How-to questions explain the workflow without saving changes. Day dates, itinerary assignments, creation, removal and other records still use the existing screens. Planners and Members retain their current screen permissions; chat editing uses the shared Owner-only day/stay save permissions.

Ask ViaMore cannot book, purchase or cancel real bookings. Stay planning status does not change reservation status. The separate Plan with AI workflow still supports reviewed planning proposals for Owners and Planners.

History, privacy and usage

  1. Open Private history to resume one of your latest 100 conversations.
  2. Use New conversation when you want a fresh discussion. Unsent question text is retained for the browser session; review it before sending in a new context.
  3. To remove a conversation, expand its deletion controls, check the confirmation and select Delete conversation. Wait for a running reply to finish first.

History is private to its author. Trip conversations become inaccessible when trip access is revoked, and are removed when their trip or author account is deleted. By default, conversations expire after 30 days without activity; the site may configure another period, shown in the panel. Reading history alone does not extend that period. Past answers reflect records at their answer time.

The usual policy charges Using ViaMore conversations to your account and trip conversations to the trip owner's account, including how-to questions in that trip conversation. The site may charge the asking account for trip questions instead; check the panel's allowance label. Trip read access does not itself require an Owner subscription. Questions and relevant source excerpts are processed by the site's configured AI provider.

Recover from a failure

  1. If a request fails, retain or edit the question and select Ask to retry explicitly. Retrying a failed provider attempt may consume additional usage.
  2. For an interrupted response, first use Reload conversation to check whether the answer was saved. An unchanged retry uses the same request identifier and does not generate another answer if the first one already succeeded.
  3. If another reply is running, wait and reload before retrying. After a server interruption, the running-request lease expires within three minutes.
  4. If allowance is exhausted or AI is unavailable, continue using normal trip screens and the user guide.
  5. If the message says allowance setup or usage review is needed, contact the site administrator. Incomplete usage must be reviewed; increasing the allowance does not clear that condition. In a trip conversation, the responsible account is usually the trip owner's, even when you are the person asking.

Uploaded documents, image interpretation, live research and cross-trip comparisons are not supported by this release.