Emails are not sending

1. Confirm that the property utilizes b4checkin emails.
   
   
   1. If the emails being referred to are in a PDF format: there are not b4checkin email.
      
      
2. Which email templates are not sending (confirmation, change, cancellation, pre-arrival, post-stay, paperless receipts, mid stay)?
   
   
3. Have the property send specific confirmation numbers of reservations that have not sent.
   
   
4. b4checkin to confirm if these emails are in the copies@b4checkin.ca email account.
   
   
   1. If they are, emails are likely being blocked by the property and/or guests. The property will need to review with their email provider why these emails are being blocked.
      
      
5. If they are not:
   
   
   1. b4checkin to confirm what email address these emails are sending from.
      
      
      1. Is this email set-up and authorized for auth.smtp?
         
         
      2. If no: follow the auth.smtp for the sending email address. Action required from the property and b4checkin team.
         
         
   2. b4checkin to confirm if the property sends emails based on segment or origin codes.
      
      
      1. If so, what segment or origin code are these emails associated with? The segment/origin code is likely missing from the list.
         
         
      2. b4checkin must adjust the codes & have the property confirm if emails are sending.
         
         
   3. b4checkin to confirm if the property has the auto emailer/b4mailer product.
      
      
      1. If so, is this running?
         
         
         • If not, b4checkin must turn the application on.
           
           
      2. Which emails are set to send with this product?
         
         
         • Confirm that these are set to send.
           
           
   4. b4checkin to confirm if the property has the manual emailer product?
      
      
      1. If so, is the property team utilizing this to send emails?
         
         
         • If so, is the tool generating an error? Please send a screenshot of this error.

Change History