Skip to content
  • There are no suggestions because the search field is empty.

How to create a client portal in Ezus

OVERVIEW

The goal is to define the process for setting up the Client Portal during various stages of the client onboarding process and who is responsible for each step. Reference the main bullet point for the following information: Pipeline Stage - Role Responsible - Relevant Pipeline.

DESCRIPTION

    • At Quotation - KTB Responsible - Sales Pipeline
      • Service Info 
        • Sub-Tab
          • Terms and Conditions 
          • Service level breakdown
          • Travel guard insurance info 
          • Pygmy Benefits 
      • Map 
        • Double check that the locations are accurately identified on the map.
        • Hide for Now 
      • Proposal
        • Template: PROPOSAL (w/out price)
        • Name of doc: Proposal v1, v2, etc. 
        • Add '- Approved' to the finalized version, ex. 'Proposal v3 - Approved’
      • Quote
        • Template: Pygmy Quotation
        • Name of doc: Estimated Pricing v1, v2, etc. 
    • Documents Pending - KTB Responsible - Sales Pipeline
      • Waiver
        • iFrame automatically generated
      • Questionnaire
        • Either with or without Passport - select relevant one 
        • iFrame automatically generated 
    • Deposit Pending - KTB Responsible - Sales Pipeline
      • Deposit Link 
        • WeTravel Link as iFrame
  • Send First Client Update - Reservations Responsible - Reservations Pipeline
  • Hide Map Tab
  • Hide Waiver Tab
  • Hide Questionnaire Tab
      • Reservations
        • Template: Reservation Overview OR Patagonia Reservation Overview
        • Name of doc: Reservation Overview v1
  • Send Second Client Update - Reservations Responsible - Reservations Pipeline
      • Reservation Overview v2
        • This should be added as an additional doc to the Reservations tab, we want to keep all records so that the client can review 
  • Ad Hoc throughout the process 
      • New proposal document, each successive one should be labeled as v1, v2, v3, etc. - Reservations Responsible 
      • Updated “Quotes”. This will require mini Ezus review from reservations person and then KTB will generate it. Keep all quotes listed with 1.0, 2.0, etc. - KTB Responsible.
      • Hike Details document
    • Invoice Sent - KTB Responsible - Invoice Ticket Pipeline
      • Final Pricing
        • Name of template: Pygmy Quotation
        • Name of doc: Final Pricing Breakdown
      • Invoice Link
        • WeTravel link as iFrame
  • In Creation - Handbook creator responsible (after completing the handbook) - Handbook Creation Ticket Pipeline
    • Handbook
      • Template: .HANDBOOK
      • Name: Group Name' - 'Trip Code' Handbook (ex. Erik Ryan - CB Handbook, Leslie Smith - TMB Handbook, etc.)
    • Gaia GPX Links 
      • Template: GAIA GPX LINKS
      • Name of doc: GAIA GPX Links v1
    • Stage Videos - TMB ONLY
      • Template: STAGE VIDEOS
      • Name of doc: Stage Videos v1
    • Reservations Owner should double check all of these elements have been updated before moving it onto the print ready stage.