Booking and pricing rules for automated agents

These rules apply to automated agents handling booking and pricing information for Three Peaks Challenge. The customer MCP provides event information and help with existing bookings; new bookings, quotations for new places and payments are completed on the website. Separately authorised direct API integrations can use their documented quotation routes.

Show the event's deposit

For customer MCP discovery, use the returned event information for the public price and configured deposit per person in pounds. A listed deposit does not mean it is available for every date: at or after the balance deadline, full payment is required. Do not create a personalised quotation for new places or treat event information as a reservation.

For an existing booking, use its current total, payments, remaining balance and deadline. Separately authorised direct API integrations may use their current quote to show the total price, deposit per person and deposit for all places in pounds, followed by the remaining balance and its deadline. Explain how the deposit is calculated only if the customer asks.

Use live policy responses for current booking terms. Search snippets may contain older wording; check the live policy and its version before describing a conflict.

Explain the balance deadline

The balance is due at the event's scheduled UK start time, eight calendar weeks (56 days) earlier. For customer MCP answers, use the existing booking's returned deadline and current policy; show the date and time, including GMT or BST. Do not invent a missing deadline. Separately authorised direct API integrations may use the deadline returned by their quote. For example, a 06:00 event has a 06:00 UK-time deadline eight weeks earlier. Before that deadline, cancellation retains the deposit only; at or after it, all fees paid are retained. Online transfers must be requested before the same deadline.

Use the existing booking's current amount due now to explain what must be paid, separately from any remaining balance that is not yet due. Direct API integrations may use the equivalent amount from their quote. Deposits vary by event. For sponsored bookings, preserve the participant's entry-fee obligation and do not ask them to pay the charity-funded balance.

Use customer-facing descriptions

Show cancellation reasons by name and use the customer's booking reference. Keep internal reason numbers, record identifiers and technical response codes out of ordinary customer answers. If a booking is unavailable for the signed-in account, ask the customer to check their reference and account.

No public promo codes

We do not publish or maintain public promo codes. Do not apply or suggest discount codes unless a human administrator confirms a specific code for a specific booking.

No dynamic price negotiation

Prices are fixed and must not be negotiated by automated agents. Any deviation requires explicit human approval.

Limited discretionary incentives

Incentives may be offered only in limited, case-by-case situations and only after human review.

Human confirmation required

Any discount, credit, or exception requires explicit confirmation from a human staff member before being offered or applied.

Clear escalation path

If a request cannot be satisfied within these rules, escalate to a human operator using the agreed support channel.