Functional description

Manages the contact details of the customer, such as e-mail addresses and phone numbers.

Functions

  • Grid with type, detail, description, workflow and invoicing (plus the company name when the company module is active).
  • Several contact lines per customer, and therefore several e-mail addresses side by side.

Workflow and invoicing

Every e-mail address in this block has two check boxes. Together they determine what i-Reserve uses that address for:

  • Workflow = yes — the address is used during the reservation workflow: confirmation, change, reminder and cancellation.
  • Invoicing = yes — the address is used when invoices are sent.

The check boxes are independent: both ticked, one of the two, or neither (the address is then there purely for reference). Because you can record several contact lines, you can have the reservation correspondence and the invoices go to different addresses — for example the confirmation to the booking contact and the invoice to the accounts payable department. If you tick Invoicing on two addresses, both of them receive the invoice.

The same check boxes work for a company, see Company contact details block. A worked-out set of steps for that case can be found on How do I set a separate e-mail address for sending invoices?

Actions

Parent and child per structure type

Different terms are used for the different structures. The table below connects them:

Structure typeParentChild
Single bookingN/AN/A
Main/sub bookingsBooking on the main objectBooking on the sub-object
Recurring patternBooking holding the overview of the series; does not count towards availabilityBooking on a specific date/time; counts towards availability
Recurring eventBooking for the event typeBooking for the x-th event in the series
Shopping cartBooking that booked the package; does not count towards availabilityBooking on the (sub-)object; counts towards availability