Skip to main content

Last Dive

In client profile it asks for date of last dive. It would be nice to have this catch the date and offer up a refresh dive or private divemaster. Selectable date by dive center but for example -

1 year ago was last dive offer a refresh dive

2 years ago from last dive a refresh or private DM is highly recommended

3+ years ago from last dive and a refresh or private DM is required

Something that tosses up a pop-up warning or something. And if people refuse the refresh dive they get a box to tick saying they agree to policy blah blah blah I understand the DM has 7 other divers and he cant babysit me blah blah blah if I struggle to descend I will be asked to surface and miss the dive no refund blah blah blah

Status: Completed9 comments

Log in to comment and vote

Comments9

  • David Aidekman

    Team•

    Oct 23

    A step toward this is now live: a diver's last-dive date now uses dives they've logged with your shop (the new dive logs), so it's more accurate. The refresher prompt itself isn't built yet.

  • David Aidekman

    Team•

    Oct 23

    Hi Henry, a small addition: dives your guides record in the new dive logs now count as the diver's dives with your shop. Your team gets a real last-dive date for returning divers as well as the one the diver gave you.

    Is this what you meant?

  • David Aidekman

    Team•

    Sep 28

    Hi Henry,

    This is now live: any question in a document can be set to appear only when an earlier question gets a particular answer.

    To build your "last dive" flow, go to Experience → Documents, open the document, and add three questions:

    1. "Has it been more than 2 years since your last dive?": make it a Yes/No question.
    2. "Will you add a refresher or a private divemaster to your booking?": another Yes/No. Under Show only when, pick "Has it been more than 2 years… — Yes".
    3. The acknowledgement: add a Choices block with the Acknowledgement style, using your own wording (for example, "I understand that without a refresher I may be asked to…"). Mark it Required. Under Show only when, pick "Will you add a refresher… — No".

    Then publish the document. A diver who has dived recently never sees questions 2 or 3. A diver who takes the refresher never sees the tick box. A diver who says no has to tick it before they can submit. If a diver goes back and changes an earlier answer, any follow-up questions that no longer apply disappear and stop being required.

    The ticked acknowledgement is saved with each diver's completed document, so you have a record of who agreed to what.

    Let me know how it goes, or if you'd like me to set it up with you.

    • Henry Schultz

      •

      Sep 28

      Excellent thank you will dig into this today.

    • Henry Schultz

      •

      Sep 28

      That looks perfect thanks!

  • David Aidekman

    Team•

    Sep 2

    @Henry Schultz Do you envision this warning for (a) the reservations agent; or (b) the customer; or (c) both?

    It sounds like a customer-facing item that you are describing.

    • Henry Schultz

      •

      Sep 4

      Yes customer facing.

      We generalyl require a refresh after 3 years of no diving, or a private DM. We do get pushback though, especially from “old-timers.” So eventually we giveup and let them dive without a refresh, but then they get on the boat and it becomes an issue somewhere. Asking for more help than should be required, or unable to descend on dive one because anxiety, etc. Then they message us and want a refund and it becomes an argument of no refund we recommended a refresh and you refused, etc.

      So just a pop-up of some sort that tries to mitigate that before its an issue. We say yes, you say no, so click this so you understand what saying no means.

      • David Aidekman

        Team•

        Sep 24

        @Henry Schultz Thanks for your patience as I’m slow to catch up on responses on this one. Is this something that you want to have a “document” record about? Would it work to have this as part of their “Trip Hub” document requirements?

        That would be a bit of a work-around, but I’m curious how important it is to record their decline of the refresher.

        I know that this is a very common requirement, so it could be good to fully build this in as a native feature on the dates and not need to set up a document requirement.

        • Henry Schultz

          •

          Sep 25

          I dont think we necessarlly need it to be in document format, but if that is the best avenue forward then Im fine with it.

          I was more thinking a simple pop-up box. Read and tick box to agree. When we were using Gravity Forms we just added it as a “conditional logic” option. When client said 2+ years the next questions was refresh. If they said no refresh, conditional logic gave them the next box agreeing to understanding what no means.

          Its not terribly important for me, but maybe other shops might find a value in it. More than anything its a customer srevice thing. I dont care if that 1 person that said no to a refresh has a shit dive. I do care if that 1 diver ruins the dive for 7 other competant divers.