Igor S.

Hi there,

If I’m not mistaken, you have also submitted a support ticket to our support platform and one of our support agents fixed the issue for you.
Please confirm.
Thanks.

The latest update of Restrict has this issue addressed. So, if you haven’t already, you should update it to the latest version 2.2.1

Hi there,

By default, Tickera does not have attendee email address ticket template element. However, this can be achieved with a custom add-on that is available upon request and which we can send you if you contact us via our contact form.

Hi there,

I’m afraid that won’t be possible as ticket codes (based on which QR codes are generated) are generated only once the ticket is purchased.
We do, however, have this on our roadmap and our developers are looking into possible solutions to make this happen so we will let you know as soon as we make any progress regarding this.

Hi there,

We’re sorry to learn about your experience.
Can you please let us know what exactly have you had issues with and our support agents weren’t able to help you?
Thanks.

Hope to get back from you soon.

Hi there,

We’re sorry to learn about your experience.
Now, regarding pricing of our add-ons, there is quite a difference between prices of different add-ons and each is priced based on its complexity. Also, add-ons don’t need to be purchased separately as we’re offering Bundle and Lifetime packages both of which include a set of add-ons with discounted pricing. Our pricing page contains information about which add-ons are included with each of the available licenses.

Hi there,

If I’m not mistaken, you have submitted support ticket to our support platform with the same question. Now, given that the issue is related to Seating Charts add-on which is a premium add-on and not related to free version of Tickera, I suggest we continue our correspondence within support ticket you have submitted.

Hi there,

Tickera works with any well-coded WordPress theme as it doesn’t have its own styling but rather follows the styling of a theme that you’re using and blends in its content as seamlessly as possible.
So, in short, Tickera itself does not have any special requirements in regards to themes and can work with any WordPress theme.
The only exception is if you will be using Tickera alongside WooCommerce via our Bridge for WooCommerce in which case ticket types are created as WooCommerce products and WooCommerce takes care of the whole checkout part. That said, if you will be using Tickera like this, you should make sure that the theme you intend on using declares WooCommerce compatibility (as WooCommerce requires specific templates that are not supported by all WordPress themes).

Hope this helps a bit.

Hi there and thank you for your feedback.

Now, the issue you’re referring to is most likely related to the available resources on the server where your website is hosted. Tickera itself does not have any limitations on how many tickets can be purchased at the same time nor the amount of data that can be collected during checkout. However, given that all this information is being stored in the database during checkout, depending on the amount of data and available resources on the server where your website is hosted, you have most probably started hitting the resource limitations on your server. In this case, we typically suggest our customers to increase the available resources and see if that helps.

Hi there,

From what we can see on our support platform, we have answered all of your questions and provided explanation where needed. Some things are simply not doable with Tickera and I believe we have provided in-depth explanation why is that. Therefore, I’m not quite sure I understand what you’re referring to by not being helpful. If there is something we failed to help with, please let us know exactly what it is.
In regards to refunds, I’m afraid we’re in no position to issue partial refunds and I have explained in my previous reply why our refund policy is limited to seven days (although we’re often making exceptions if refunds are requested few days after that period).

Hi there,

I believe we have explained this matter in your support ticket but I’ll write it here as well.
Duplicating of both events and seating charts is, of course, possible.
The only thing that cannot be done is to have seats in duplicated seating chart automatically assigned with the ticket types that belong to newly selected event. This is because each event has its own set of ticket types which makes it pretty impossible to determine which seat should be assigned with what ticket type.
Therefore, after duplication of the seating chart and assigning a new event to it, you need to assign seats with ticket types that belong to newly selected event.

As for the refund policy, we admit it is strict. However, we’re always offering and encouraging all of our potential customers to request access to our playground website where they can test everything for as long as they want prior committing to purchasing their license. Also, we’re always open to answering any questions before, during and after testing on the playground website and our supporting agents are doing their best to explain in as many details as possible any questions you may have regarding Tickera so that once you decide to purchase the license, you know exactly what you’re getting.
The reason why we have rather short time span during which we’re issuing a refund is because it happened many times before that customers were purchasing their license, created event, sold tickets for it and then asked for refund once their event has passed. Now, I’m not telling by any means that this was your intention whatsoever but am rather explaining the reason behind strict refund policy.

Thank you so much for your kind words.

Feedbacks like these are always valuable to us and help us great deal in shaping Tickera to fit the needs of as many customers as possible and it’s always exciting to learn about the new stuff our customers come up with. We will be more than willing to test and learn more about the custom add-ons you have created for Tickera and give you our thoughts.

Thanks again for your feedback!

Hi there,

We’re sorry to learn about your experience.
Can you please let us know how exactly your website was broken after installation of Tickera? Were there any errors or something else?
Please let us know as many details as possible so we could check what might be wrong.

Thanks.

Hi there,

We’re sorry to learn about your experience. However, as we’re always striving to get better and learn from our mistakes, can you please let us know what exactly have you found difficult while setting up and what exactly have you found in Tickera that was bloating and slowing down your website?

Thanks.

First of all, thank you so much for your kind words!
Yes, we have invested a lot of time making Tickera what it is today and we’re always listening closely to our customers and adding features based on their feedback.

Now, I feel I need to address one thing: Early Bird ticket pricing actually can be done. The trick is to create a separate ticket type and call it eg. Early Bird and set its pricing to whatever lower pricing you need for it. After that, set start and end date and time during which this ticket type will be available for sale.
Next, create a Standard ticket type, set its pricing and all that but when setting up ticket selling availability, make sure it’s start date and time matches the end date and time of the Early Bird ticket type.
That way, as soon as the Early Bird ticket type expires and becomes unavailable, Standard ticket type will become available for purchase.
Of course, you can create as many ticket types as you want and schedule ticket selling availability for each.

As for reserving a whole table in a single go, you’re unfortunately, right. This is not possible yet and each seat must be selected individually and ticket for it added to the cart. However, our developers have this on their roadmap but given the complexity of the Seating Charts add-on, as for now, we cannot tell when this might be expected, I’m afraid.