Monitoring of emails sent with tickets and accreditations.

From bikubo we care about the deliverability of the emails with which the tickets / accreditations are sent.

A ticket / accreditation can be sent for the first time from the platform with the individual sending (from the intranet of the administrator or the distributor), or with the massive sending by uploading an excel file.

The user can forward the ticket / accreditation through the bikubo platform for the second time to the same or to another email from the attendee, requesting it from the list of ticket assistants / accreditations. These requests for email forwarding by default are limited to a maximum of five daily, although bikubo can be requested not to set limits in this regard.

With the request of sending a ticket / accreditation mail from the bikubo platform, a transactional mailing platform is used first, and we periodically check the deliverability. If the result of the check shows problems with the shipment, a second shipment of the same ticket / accreditation is made from another platform of different transactional mailing, in case there are problems of deliverability with the first one. The result of the shipment is shown in the list of attendees, and may have the following values:

• "opened". The attendee has opened the mail.
• "sent". The email has been sent to the attendee. We can not guarantee that you have gone directly to the inbox, or to spam. We have delivery reports to inbox close to 90%, however the configuration of corporate emails can limit the correct deliverability. In addition, our experience indicates that many times in the report is shown as sent, and has actually been opened by the attendee without being indicated as such (for example the reason may be not to allow the attendee the tracking pixel at the opening of the mail ).
• "clicked". The attendee has opened the mail and clicked on some link in the email.
• "bounced, hardbounced". Definitive bounces occur when the receiving server returns a code indicating that the reason for the refusal is a permanent problem with that server or address of the recipient.
• "softbounced". Temporary bounces occur when the receiving server returns a code indicating that the reason for the negative is a temporary problem with that server or recipient address.
• "rejected, blocked". The receiving server rejects the mail and the sending platform does not suppress the address to send.
• "Spam". The email sent has gone directly to the spam folder.
• "queued". The email sent is waiting to be sent.
• "deferred". The receiving mail server delays the acceptance of the mail.

In order to know the sending conditions of the emails sent with the tickets / credentials, every five minutes the transactional shipping platform used by the delivery status of the sent mails that have not had any deliverability report is consulted. collects in the bikubo database the status of the shipment.

For the emails sent as a result of the delivery report the states 'blocked', 'spam', 'softbounced', 'queued', 'sent', 'deferred', every fifteen minutes during the first 48 hours of sending, consult the transactional shipping platform used if you have changed status. And then it is consulted once a day until the 15th day after the shipment, for those states indicated. If you change status, it is collected in the bikubo database. Outside of those states, it is not consulted again and therefore the sending status of the sent mail is not modified.

Once indicated above, the user of bikubo sends an email with a ticket / accreditation, and immediately shows in the list of attendees, in the column of 'email' only the data of the email entered, without more data about the deliverable thereof. After a maximum of five minutes, a first report of mail deliverability is displayed. The next step that bikubo performs with respect to that shipment is:

• If the status is 'hardbounced', 'blocked', 'spam', 'softbounced', 'queued', 'unsub', immediately make a second sending of the same ticket / accreditation with another different transactional mailing platform, in case there are problems of deliverability with the first, and also the maximum five minutes is collected and the deliverability report is shown with this second platform, and there may also be problems with the shipment. In this case it is strongly advised to change the recipient's mailing address.
• If the delivery report result has the status 'blocked', 'spam', 'softbounced', 'queued', 'sent', 'deferred', at fifteen minutes during the first 48 hours of dispatch, the Transactional shipping platform used if it has changed status. And then it is consulted once a day until the 15th day after the shipment, for those states indicated. If you change status, it is collected in the bikubo database.
• If the delivery status is 'clicked' or 'opened', it is collected in the database and no further changes are made to the status or forwarding operations.