Jump to content

Steve Giller

Hornbill Staff
  • Posts

    6,498
  • Joined

  • Last visited

  • Days Won

    268

Posts posted by Steve Giller

  1. There is no Auto-reply.

    The best way to create one would be to have a simple "Raise Request" action that creates a Request, emails the Customer with your required message, and closes itself, all without any Users interacting with it, or even being aware it exists.

    This can then be reported on, and you have an exact count (if required) of the number of customers who do this, who they are, whether there are repeat offenders (individual or by department) or if there are patterns (e.g. they happen out of hours or at busy times, etc.) and you can take any actions that are deemed suitable.

  2. Here is the link to Documentation on Workflows in Service Manager. You may need to review a couple of other topics depending on your existing familiarity with Hornbill.
    The Workflow's Hornbill Automation node can be configured to assign a Request, either to a Team (as it appears to now) or a User. If assigning to a User this can be a named User, or on a "Round Robin" basis with criteria that you define.

    "BPM" is an older term, it is synonymous with "Workflow"

  3. 32 minutes ago, Art at BU said:

    I see also this other thread below which seems related and is being considered

    This is already in the product.

    It's not clear what you're asking above - how would you envisage an image be indexed and searched, for example?

     

    An msg file is a Microsoft format specific to Outlook, designed to be saved from and opened in Outlook, with embedded and attached images encoded in the file, and even the text is not simply a line of characters. I'm not suggesting it's impossible, as that's not my area, but in the simple 2-line email I looked at, the text part of the .msg was split into 10 lines, and the entire file was 184 lines - most of which was similar to

    cG9ydCB0ZWFtIG9uIDIwMjQtMDItMjcgMTI6MTc6MjRaPC9zcGFuPjwvc3Bhbj48L3A+DQoNCjxw
    PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTFwdDsiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTpj
    YWxpYnJpLHZlcmRhbmEsZ2VuZXZhLHNhbnMtc2VyaWY7Ij5SYWlzZWQgYnkgQm9iIEJsYWNrbWVy

     

  4. I'm not sure I fully understand what you've said above - particularly 

    22 hours ago, Sam P said:

    I have logged in as a test user in the new domain

    Can you explain what you mean here - I'm not aware of the ability to log into a specific Domain - you can view a specific Domain.

    Secondly, the Documentation states that
     

    Quote

    Service Domains are used to define business areas where related services will be made available to users who will consume the services.

    and the Request List View is for Users who support the Services, which is a very different scenario.

  5. Hi @Jim

    This setting doesn't really apply to the UI elements, it's aimed (as the api.xmlmc. prefix suggests) at more behind the scenes uses - e.g. whether to show archived Users when displaying activity stream followers, post likes, workspace members, participants in conversations - those kind of areas.

  6. 39 minutes ago, Andrew Parsons said:

    but we want the next action (after email received) to be automated, rather than someone having to take action

    There is no requirement for human interaction at this point, the Workflow can handle the progression.

    40 minutes ago, Andrew Parsons said:

    if the user happens to email in asking for an update, this would also trigger the next action, so ideally we could add condiitons

    This can be done by collecting the last update via the Workflow, comparing that to the required conditions and placing the Request back on hold then returning to the Wait for Off Hold node until the next time.

  7. If the emails have consistent content in the fromAddress, Subject, or Body, you can catch that with an Inbound Routing Rule.

    Hornbill is also not an answering service, so if you want to respond to the sender you will need to automatically raise a "silent" request, with a Workflow that emails the sender with the required response and then closes itself. The benefit of a Request is that you can (by using Categories or specific Summaries etc.) report on this and know how many of these you are automatically fielding - and even find repeat offenders if required!

    • Like 1
×
×
  • Create New...