Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • type – to determine appropriate content in the dynamic template, one of values:

    • bookingConfirmation – Customer created booking

    • remindedAboutBooking – Booking reminder for customer

    • bookingActivated – Booking is activate and is a queue ticket now

    • positionCancelled – staff removed future booking created by the customer

    • notifiedToApproach - notify customer that it’s him turn soon

    • positionCalled – Position called by staff

    • positionRetry – staff pressed ‘Retry’ because customer did not show up

    • positionRejected – staff pressed ‘Reject’ to remove ticket

  • position – ticket information, including dates, labels, language and more information that can be should be used in the template

    • id - internal ticket identifier

    • location - queue display name (store, department and others info)

    • type - ticket type, possible values: anonymous (walk-in ticket), booking (pre-booking), manual (tickets issued by staff)

    • priority - internal value

    • locale - customer preferred language (en, ar, sv)

    • notification - customer contact information

      • type - type of notifications that customer subscribed to (phoneNumber or email)

      • settings.from - not relevant/internal use

      • settings.to - customer phone number

      • settings.recipient - customer email (in case of email notifications)

    • booking.start - timeslot start in case of bookings, local timezone

    • booking end - timeslot end in case of bookings, local timezone

    • status - ticket status, possible values: draft (pre-booking created but not active), pending (ticket is inside queue), notified (ticket called out by staff), fulfilled (ticket checked in by the staff), completed (ticket has been served), rejected (ticket was cancelled either by customer or staff)

    • label - assigned ticket number (A1, B2 and such)

    • queue - queue identifier, can be used to correlate data

    • createdAt - ticket creation time, ISO string

    • fulfilledAt - customer checked-in datetime, ISO string

    • bookingReminderAt - if configured, when the booking reminder will be sent to customer, ISO string

    • QRCodeCheckInPositionId - value of the QR code to render to allow check-in by the staff

  • actionLink – link to present to customer, link depends on email type (see below)

...