Jump to content

Ken

Members
  • Posts

    316
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by Ken

  1. I edited my post a couple times but yea.  Originally I meant just the Ticket Created email which the Weclome Email system in packages would work out fine.  But now I see problems where all tickets from all departments are going to end up coming from set of email templates with one email address.  I'd like them to be isolated so that if someone emails billing they get emails from billing.  Not email billing and then get replied to by support.

     

    Reason is clients may want to route their incoming email within the organization or even on their email client.  I'm not sure if it'll throw people off getting emails from support when it was a billing or sales question, etc.

  2. Currently all support departments use the same set of email templates.  Would you guys be interested in adding the ability to set different email templates for different departments?  Rather than just indicating that we got their ticket I'd like to add other useful information that pertains to that department.

     

    This would also allow the system to respond back to the client from the email address of that department.

  3. When changing email addresses in email templates you have to go into each one individually and edit them or update them from the database

     

    Would anyone be interested in a function to add system contacts?   Then we can use drop down menus in email fields and allow us to change system email fields swiftly. 

  4. I too have used HostBill for more than 2 years now and just like I told you in the other thread, HostBill writes modules.  That's the highlight of their software, it's why people buy it.  Unforuntately those modules come out of the box broken from functionality to visuals.  He does not fix them.  And when he updates them he updates them so that they continue to work with his billing system.  He does not update to improve them or add the newest basic features that you'd expect from a module update.  His orderforms are equally buggy and some of the features on them are redundant!

     

    The billing system core is almost never updated or improved.  It's got that same useless interface.

     

    Lastly, like it was pointed out in this thread already, he'll disappear one day.  He keeps his communications limited and hides behind his new support model which is for you to pay to even reach him.

     

    No one is speaking "ill" about anything.  We're just talking a competing product.

  5. If you 404 at the root directory it redirects you to the login page.  Is there a way to make it redirect to a 404 page instead?

     

    The reason is I have static pages setup in the install directory (instead of using the portal plugin).  Even with index.php removed in apache as a default directory index it will still redirect to the login page.  If you 404 under the /client/ URL it gives a 404 page within Blesta and that's fine.

     

     

     

    EDIT:  No longer needed.  Delete if you want.

  6. More importantly, where would Blesta get impression data from?  One of the things I'm after is metered billing to which Blesta would pull the report using an API call.  So this may fall under "metered" billing if I'm not mistaken.

  7. They used to be all included in HB until the owner flipped his head. He now charges for everything he can stick a price tag on. But because Blesta isn't as big, Blesta's getting slated here and there from WHM** customers to HB customers. Until they have to move.

    I know.  I've had my license since the beginning just waiting for it to mature.  I refused to use it in the state that it's been in this whole time.  He's definitely flipped his head... charging 200-300 for these modules and order forms broken out of the box.  Then he wants $75 USD just to talk to him and have them fix it.  They want $75 to talk to you about quotes on new development.  The billing system itself hasn't even been touched as far as updates or features.  And community support?  They had it but then got rid of it since customers used it to vent frustrations and no one could ever solve anything there.

     

    The reason I kept it around was to potentially make our own modules for it.  Blesta v3 is out now and not only can we build modules for it now but they came out with the Universal Module.  I'm satisfied with QA from the Blesta team but the community as well.

×
×
  • Create New...