Jump to content

Call import and business process


Recommended Posts

Hi All,

I'm hoping someone is able to help with this question!

My business processes are set to wait for a priority, wait for an owner and then send a notification to the customer.

I'm preparing to do the call import and am setting up the conf files. As I was going through the priority mapping section, it occurred to me that once imported, the business process I have set up may kick in. If so, that could result in it triggering emails to anybody who has an open call.

Will that happen?

Do you have any advice from you own call imports?

Thanks in advance.


Link to comment
Share on other sites

Hi Chris,

 it's great to hear you're preparing to migrate your calls into Hornbill. When working with the Supportworks request import utility, Business Processes will only be associated with calls that are imported with a status of "Open". Business Processes will not be associated to closed or resolved calls.

As you have identified, there are various core-actions that can be carried out in Business Process such as Team assignment and email notifications. It is important to consider if associating a BPM to these imported open calls is even appropriate. Decide if all BPMs should be deactivated prior to the import or if a new BPM is required especially for these open imported calls (a new BPM can be used to great effect in helping inform customers of their new Hornbill reference number). 

What I mean by "appropriate" is I think what you're concerned about, i.e. if a call has been open for a number of days/weeks etc. it will be confusing to the customer if they all of a sudden get a new-call-confirmation email. To deal with this (and similar situations), you could create a BPM especially for use against these imported calls, or you could modify your existing BPM with various decision branches to by-pass or perform different operations if the call is identified as an imported one. In terms of identifying imported calls, a good method is to hard-code a custom field such as "custom q" with a value of "imported" or something similar that you can use in these BPM decision branches.


Link to comment
Share on other sites

@chrisnutt it will spawn BP for active requests (i.e. not closed or cancelled). My suggestions:

  • temporarily disable the BP (deactivate them) if you don't need a BP on imported requests;
  • if the above not possible/feasible temporarily remove the email to customer nodes from BPs.
    Link to comment
    Share on other sites

    Thanks for the swift replies, Dan and Victor

    Some interesting thoughts. I may just try the disable all Bus Pros route while testing, but for the day before go live, I'll maybe have put in some decisions into them.


    Link to comment
    Share on other sites

    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now
    • Create New...