The "Send Payment Link" feature has been enhanced to provide greater flexibility and control over how payment links are distributed and communicated. This update allows both internal and external users to send payment links to any recipient, including themselves, and to customize the accompanying email content.

• Reduces operational workarounds and manual processes

• Minimizes risk of errors by allowing internal testing and redirection

• Enables personalized, branded communication

• Improves workflow efficiency and client trust

• A new "Send Payment Link" checkbox is available in System Settings → Reservation Display Settings → Reservation Menu.

• Administrators can control which user types (All, Direct, Agent) see the "Send Payment Link" option in the Actions Menu.

• This option is always visible for internal users.

  • Open

    

     

• The "Send Payment Link" menu option now redirects to a new screen, modeled after the "Send Documents" screen.

• The new screen includes:

  • To Address: Choose from existing options, with an additional "All Passengers with Email" selection.

  • From Address: Internal users can select; external users see a note that the email will be sent from the brand’s default email address.

  • Subject: Editable textbox, can be pre-populated via database rules.

  • Body: Editable HTML area, can be pre-populated via database rules. Placeholders are available for dynamic content (see below).

  • Open

    
    Open

    

     

Users will have to go to Payment → Send Payment Link to access this screen.

Open

• The process follows standard reservation email-sending workflows.

• Email history is recorded under History → Res Messages for auditing and review.

4. Data Setup and Template Placeholders

• Default subject and body can be set using booking rules:

  • Subject: DOCS-SUBJECT-PAYMENTLINK

    • Open

      

       

  • Body: DOCS-EMAIL-PAYMENTLINK

    • Open

      

       

• Supported placeholders for dynamic content:

  • [RESNUMBER] – Reservation number

  • [BRANDNAME] – Brand name

  • [BRANDPHONE] – Brand phone number

  • [EMAIL] – User’s email address

  • [PHONEEXT] – User’s phone extension (internal only)

  • [USERNAME] – User’s name

  • [PRODUCTNAME] – Main product booked

  • [LEADPAXFIRSTNAME] / [LEADPAXLASTNAME] – Lead passenger’s name

  • [CONTACTFIRSTNAME] / [CONTACTLASTNAME] – Main contact’s name

  • [PAYMENTLINK] – Payment link URL for the reservation

• Reply To RuleArea: PAYLINKREPLYTO

  • A new setting will be introduced for the reply to

    • RuleArea: PAYLINKREPLYTO

    • Rule Text: One of 3 options

      • DefaultEmail

        • This comes from the Brand’s Default Email

      • UserEmail

        • Will be the logged in user’s email

      • emailadd@email.com

        • Specific email address

5. Validation and User Experience

• The system validates that both Subject and Body are filled before sending.

• At least one recipient must be specified.

• After sending, all details are saved to reservation history for reference.

6. Backward Compatibility

• If a legacy queue rule (DirectPaymentLink) exists, the system will use the previous queue-based process. If not, it will use the new screen and workflow. IF you wish to use the above setting the DirectPaymentLinkRule must be deleted.

• Internal staff can send payment links to themselves or any recipient for testing or forwarding.

• External users can send payment links to themselves for later forwarding to clients.

• All users can personalize the email content to align with branding and client expectations.

• Reduced risk of sending incorrect or broken links

• Streamlined communication and workflow

• Enhanced ability to personalize client interactions

Related Links

• https://softrip.atlassian.net/browse/SSM-12074

This article is designed for easy copy-paste into Confluence and avoids client-specific references. If you need a more detailed breakdown or additional formatting, let me know!