Jump to content

sprasad

Hornbill Users
  • Posts

    177
  • Joined

  • Last visited

  • Days Won

    5

Posts posted by sprasad

  1.  

    @Ehsan @James Ainsworth Our users are still losing unsaved work so I wonder if the this could be explored further and a prompt displayed prior to the current page being closed and.or a new page loaded.  Another example case provided to us had the below scenario:
     

    It was noticed by 1st tier from the site's response to their chasing email that Robin had put support call IDXIN00272038 on hold without sending an email and this has happened sometimes for me as well.
    One of the possible reasons for this (which for a couple of my support calls, I am certain has been the cause) is where you prepare an email but forget the final Send (or get distracted and when you come back to the support call you think you have sent it) and then you set the call On-hold, closing the tab with the support call (or open the Request List in the same tab or if at the end of the day you close the browser).
    Jira recognises that a Comment that you have started has not been saved if you close the tab or browser and you get a message asking whether you definitely want to come off the page as this would be lost (this has helped me a few times when getting distracted whilst doing a Jira Comment).
    So can we ask Hornbill if they can do similar for Emails?

    image.png

  2. Quite often, customers will continue to email us on requests which have been Resolved and closed.  We still record the correspondence on the original request (for audit purposes) and will then raise a linked request for the follow up enquiry.

    However, sometimes the analyst applying the email request do not notice that the status of the request is Closed.  Currently, it shows as Black Bold but can this be made obvious, either with an additional Pop Up message and/or Red Bold larger text please?

    image.png.ce66be171613ff2213ca28832f95c19e.png

    • Like 1
  3. Using a customer email which contains an attachment, we will create a new request.  We step through the progressive capture and on the final screen, it will show which attachments are to be applied to the request (See image below).  The attachment(s) may also include additional logos (Twitter, Facebook, etc) but as these are presented to the user towards the bottom of the page, sometimes it can be missed and get added to the Request.
     

    Users have asked if the attachments could be shown in the vacant space immediately under the [FINISH] Button (middle left part of the form) as this will be more prominent?image.thumb.png.c8f31511d1b79dbcfcf6a63173d03a43.png
     

  4. @Ehsan We currently do not see the User Availability States screen but as Gerry says, it may still be in Beta.  In the meantime, this has caused us unnecessary work and wasted internal resource.  Some of the Internal comments are:

    ·        The status 'Do Not Disturb' stopped auto allocation prior to the changes applied via the latest build

    ·        The status 'In a Meeting' and 'Training' should also stop auto allocation and worked previously

    ·        The  only status that auto assigns, should be "available" all others would have the logic to not assign.

    ·        It appears that HB are missing the point. The Availability DND used to stop auto assignment.

    ·        From my testing today, all availabilities are allowing auto assignment (incl. out of the office) except “Not At Work” and this is not how HB worked yesterday

    • Like 2
  5. Following the release of  New Update: Hornbill Timesheet Manager (148) and the below 2 features:

    Visibility of Co-Worker Timesheets.
    Visibility of Team Timesheets.

    We are seeing Archived Co-workers under the Managers timesheet view.

    Is this intentional and/or is there any way it can be removed from View?

  6. Further to release of Hornbill Service Manager (1040), which allowed you to Update multiple Requests from the Request list, it will be useful to have a similar feature where you could update multiple requests from an Email.

    We currently raise defects on a Atlassian Jira platform and link affected users/requests to it.  Where we have a number of customers affected by the same defect, it will be highly effective if we had a Multi-Select Action so that all affected requests can be updated, using the 'Apply to Request' option.

    I tried various combinations on this field and although the Apply button becomes enabled, we then get an error of [Please provide a request ID]  

    image.png.01f7e07f12f6e6820703b2a8fec29265.png

  7. Hello @Daniel Dekel this relates to the Contacts search from #1, with the results displayed at #2.  If you then click the Archived button at #3. you get a diffrent set of results.

    Our RFC was if the Archived contacts were also displayed on the original search but the accounts clearly marked as Archived so we could see at a glance, their current + past accounts plus which emails had been utilised .


    image.png.25190d9f60f12e866eb94fd4e6495a21.png

  8. In line with best practice, we are using our customers email address as their login ID

    As you cannot use an email address that is stored in the dB, it will be useful if the Contacts search returned details of the current customer AS WELL AS details of the Archived customer record, so that we can see what emails had been stored previously for this customer.

    From the results screen, a tag confirming which is the Archived customer record, will be very useful.

    Currently, you have do perform 2 separate search and open them under separate Tabs, to verify this information.

  9. This is a Request for Change, so that we have the ability to mark a service as Historic where a customer moves to another product.

    We have customer who are subscribed to a standard service but then renegotiate their maintenance Contract and go on to a Hosted solution.
    Therefore, their Service changes from  XXX to Hosted_XXX

    When customer 1st switch over to hosted, they often have open requests, so if we remove those non-hosted services, they won’t be able to view any historic incidents for that service.

    If we made the old Service "Historic" customers could still view the current Open Requests but will be unable to log any new requests.

    To add to this and to help us to get the New services linked in anticipation of go-live for the customer, it will be useful to have a service in Draft before we publish it, under the Organisation.

     

  10. @Deen Is there an update on this issue please?  The most latest customer complaint I have had is as follows:
    Please can the time allowed to be in the portal be extended to enable disturbances to be taken into account when completing requests? It is very frustrating when being timed out just as I finish submitting my request and it doesn’t save what has been input!!

×
×
  • Create New...