|
Wonderful2016
|
March 5, 2016 at 7:44 am
This happens with Bank Draft Payment Method:
User is buying a ticket with Bank Draft, where we provided Bank Details for money transfer.
– What happens is, registrant get email with a link for paying, instead Bank Details within the email.
– Again the link in this registrant email lead to the same formular with additional info and Bank Details there – with annoucement of invoice, which never comes.
Where is this workflow process described and how to change it?
This is far too complicated, there is no overview what happens with all email sendings. And anyway, what about invoice email? Is there something to manage for this?
We have to use a process with one email and Bank Detail, after receiving money ticket is going out. We do not see how this works….
Is there a way to get ticket as attachement on email and not a URL to the registrant? I did not find description, that a ticket is just a Link.
|
|
Wonderful2016
|
March 5, 2016 at 4:43 pm
Now I worked through most of doc pages and fact is, your doc are far too unspecific, and looking into forum mostly any questions are outcome of this. This Bank Draft is described as such, nobody understand it in depth, because it is so trivial, but the system makes it complicated. Why not give Bankdetails right away with registering?
So after spending hours of time to get an overview, i come to conclusion, you do a good support, but no good software-usability and a good starter guide with samples and screenshots. What is there right now is somehow marketing text…
|
|
Tony
|
March 7, 2016 at 3:19 am
Hi there,
Where is this workflow process described and how to change it?
I’m sure what you would like to have changed here?
The EFT payment instructions should be displayed on the thank you page once the user finalizes the registration, here – http://take.ms/PnS9W
The email is to provide details of the registration and show that it is pending payment, the user can also use the link within the email to make an online payment at a later date (should they chose not to use EFT).
So do you not see the EFT details on the thank you page after finalizing the registration?
We do not include the EFT payment instructions before the use has finalized, for example here – http://take.ms/zufLy
Because we found the users would take note of the EFT details and then never finalize the registration, this caused further problems for both yourself (the event admin) and the user themselves. So we only display the details on the thank you page after the registration has been finalized.
This is far too complicated, there is no overview what happens with all email sendings. And anyway, what about invoice email? Is there something to manage for this?
Which invoice email? Event Espresso does not send an email with the Invoice, can you post a screenshot showing where you see this please?
We have to use a process with one email and Bank Detail, after receiving money ticket is going out. We do not see how this works….
The tickets are sent out when the registration has been ‘Approved’, with the EFT payment method this will be when you have verified the payment and applied this within the admin.
Is there a way to get ticket as attachement on email and not a URL to the registrant? I did not find description, that a ticket is just a Link.
No your currently can not include the ticket within the email as an attachment.
This Bank Draft is described as such, nobody understand it in depth, because it is so trivial, but the system makes it complicated. Why not give Bankdetails right away with registering?
As mentioned above, we do. Do you not see the bank details on the thank you page when you register?
|
|
Wonderful2016
|
March 7, 2016 at 6:17 am
Thanks in the first place – I have to say, this system does a good job, but as I am new to this, we have to understand the roadmap, which theoretical is fine – but the whole usability in the backend is hard to follow. On top comes, that many features are running only with workarounds, this is concerned to outside countries like germany, and i do not mean translation. But the workflow and managing the backend handling. Maybe you think this is well done, this is for those, who followed the path and went through all this.
All docs and helpfiles are very basic and can some only can be followed when you are programmer.
One good example for misleading is a basic task: List of countries, as after installation i only find canada, us and somehow my homecountry. So there are different helpfiles which differ from each other. Just by chance i came across the video, which tells me, how to integrate each single country into the dropdown menu. After all i get a link to many single plugin country files from support, and later another plugin file for all countries from github. This is no clear step by step documentation, all in all confusing, and i did not find a Roadmap with an profound overview for this ticket system.
Other example, we miss the understanding for price tables, how to use and take effect to a calculation, which we can follow and does work 100%
The workflow of each step is only easy, when you have a map in mind – usabiltiy is – sorry to say this – not userfriendly at all, except some stages…
But, support is helpful and fast!
|
