Skip to content
← Product Ideas Forum

Connectivity

Connectivity

Categories

JUMP TO ANOTHER FORUM

(thinking…)

What is the problem you're trying to solve?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

3 results found

  1. Booker for Distributor: The email address should not be a mandatory field

    Booker for Distributor: The email address should not be a mandatory field as the assistants do not know each single email address of all employees they are doing reservations for. At the moment they are using the same email address for different guests. So the guest profiles are overwritten anytime. If we are creating reservations manually, the email address is also not a mandatory field. It should be enough to have the email address of the booker. That is the only way to use the distributor valueable for corporate guests.

    3 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    2 comments  ·  Booking Engine API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    released  ·  Aneta responded

    Hi Mewsers,
    for all booking done by booker, you can now configure whether the guest e-mail is mandatory or optional.
    We recommend to keep guest’s e-mail required but if you need to set guests e-mail optional, here is how to do it:

    1. Go to Settings > Stay > Distributor configurations and select the configuration from the list.

    2. In the configuration scroll down to field:
    “Guest email (when booker is not a guest) *” and select “Optional” option.

    With this set up only booker’s e-mail will be required on the “Details” page.

    Have a great day,
    Aneta

  2. Restrictions managed by calendar, instead of by list

    I suggest to use as model the way Booking.com extranet manages restrictions, directly from the calendar.
    This will still allow the creation of restrictions for a period, but it will also make it simple and quick to modify a restriction for single dates or spaces or fare; for example setting up a different min stay for 2 consecutive Saturdays.
    It will also avoid having to check if in a certain period, or date, there are too many restrictions overlapping that could create confusion.

    5 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Booking Engine API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  3. Making sure packages are directly bookable through the booking engine. So that the guest only selects the date and the rest is automatic

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Booking Engine API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
  • Don't see your idea?