A bit more about our beta launch

Posted by Luca on June 28th

As James announced yesterday, in 20 days time (eeek), we are planning to launch the first beta version of Juvely. In this post I am going to go over what features will be available with this beta, what we still need to do, and what we are going to do to help the beta.

For now with this version of the beta we are going to just have the ticket section functional. The knowledge base section is mostly done, but needs a redesign and the chat section hasn’t even been started. The ticket section is the main bit though, so we think this will be alright. We are going to make a few minor changes to this to get it finished off (mainly just changing text around to make it clearer) and also add a couple of settings pages. The beta will be free so we don’t need to worry about billing or different types of account just yet.

Here are a list of features we hope to have available for the first beta:

  • Users can create tickets by accessing the support centre or sending an email to the support address.
  • Staff members can then reply to these tickets, change the priority, reassign them or close them.
  • Users will recieve an email reply when a staff member replies to a ticket, and can then reply by email or by accessing the support centre.
  • Staff members can opt to recieve an email when users reply to a ticket, otherwise it will be shown at the top of the ticket list as being updated.
  • Tickets in the staff centre can be filtered by various options and also ordered by various fields.
  • Tickets can be searched or live filtered by entering terms into the relavent boxes.
  • Users and staff members can subscribe to RSS feeds of their tickets.
  • The support centre that users access can be customised, and by default is a white label system. No Juvely logos or any mention (execpt for T&Cs and other legal mumbo jumbo). You will be able to customise this and add your own company logo.
  • A smart, simple and elegant user interface that uses modern techniques such as AJAX to enhance the page, but not restrain usability.

In the near future we also plan to add SMS replies, but at the moment we still need to look more into it and the best way of charging for its use.

Right that is what we are going to have for Juvely, so let me also tell you what we are going to have to help the beta along. First of all we are going to get a proper website for Juvely rather than just a holding page. James is working on it as we speak trying to decide what design to use. He is also going to put together a press package with various info on Juvely so interested parties don’t have to trawl through the blog. We will also probably be moving to the MediaTemple DV (Dedicated Virtual) server as their GS (Grid Server) system sucks….. (see comments below)

To enable us to get feedback on the beta and for users to get support we will be putting in links to non entrusive forms that enable us to send us a message. We will also be setting up a forum for users to discuss any issues they are having, this will probably not require registration so you don’t need to remember yet another username and password. On the day of the launch we were thinking about setting up a Campfire room so that if anyone has any questions they can easily get in touch with us.

As things progress we will go more into detail about what we are doing so keep watching!

4 Comments »

  1. Um..just want to jump in here…The Grid does not suck. It may not be ideal for developing your particular software, but it kills in other areas..mostly this depends on the user and their knowlege of development variables.

    the (dv) is a MUCH more suitable environment for software development.

    Just a little note from the (mt) team

    Jason Mcvearry
    Partner Director
    (mt) Media Temple
    jason@mediatemple.net

    Comment by Jmcvearry — 29th of June, 2007 @ 12:57 am

  2. Hi Jason, I don’t think he meant it in such a slanderous way, we just find it a little slow, we do love the Mediatemple services, your control panel & support kicks ass, and yes we can’t wait to upgrade to (dv) which we’re sure will be suited better toward our needs!

    Comment by James — 29th of June, 2007 @ 1:12 am

  3. No Worries Guys! We’re thrilled to have you!

    J

    Comment by Jmcvearry — 29th of June, 2007 @ 1:22 am

  4. Hi Jason,

    Thanks for reading, and apologies for over exagurating a little. The problems we have been experiencing are slow file and database access which has caused nightmares for our application in terms of speed, as CakePHP, the framework we use, caches database queries to disk in order to speed things up. Even the blog sometimes seems slow to me, but it could just be my connection acting up.

    I am sure the (dv) will be much better, and if not I expect your excellent staff will be able to sort it out!

    Cheers,
    Luca

    Comment by Luca — 29th of June, 2007 @ 5:52 pm

RSS feed for comments on this post. TrackBack URI

Leave a comment