Jump to content
2600Hz Community

Holiday Schedule That is the same but different hours per location


TJ Forsman
 Share

Recommended Posts

We do work for a bank that takes the same days off across all  8 of their branches but has different hours for for each branch for the most part. One or two are the same hours.  

 

Two questions on this. Could we use smartpbx for the holidays and send the call to an advance callflow for the hours and somehow make them flow to the right place

or 

Option two build all the holidays in once call flow and then send the calls to another callflow and be able to have the numbers go to the right place based on what number was called. 

 

The problem i see on either one of these is you would have to assign the numbers either to smartpbx or the first holiday callflow and when the call hit the second call flow you couldn't tell the call flow if the number is xyz do this and if the number is abc go this way instead. would the only way to do this be to build a callflow with the same holidays for every branch and then assign the correct number for it to that call flow? it would just be nice not to have to edit holidays in 8 different callflows when they all take the same day. Let me know if anyone has any ideas. 

Link to comment
Share on other sites

Do they have a specific message that plays on holidays, or does it go to just a generic "we're closed"?  If a generic, you could route to branch specific time "checker" call flow and then route to a single holiday flow.  If you have a specific message, though you'd have a situation where the office is closed but it is still a holiday.  Since it happens in that order you'd hear the closed message.

 

Link to comment
Share on other sites

I think the plan is to just route the caller to the after hours message for the branch if they are closed and the same after hours message if it is a holiday. Each branch will be a little different on the message that is played as each branch has a separate auto attendant to reach people at the specific branch. Basically each branch has their own open and closed callflow that has an auto attendant that would need to play to router a caller to the correct place. 

Link to comment
Share on other sites

Wouldn't it be easier to give each branch their own account and tie them together using DIDs and landline devices? I.e. ext 9000 is a callflow with a landline device that reaches the main DID of another branch where the caller can be greeted by the auto-attendant of that branch and then enter an extension. You will need to pay the 2600hz DID and device fee but it's a solid solution and provides separation of operating hours. I do wish 2600hz would give us the ability to call between accounts without that tax. If 2600hz is reading this, we don't need BLF across accounts just an inexpensive way to tie accounts together. ;)

Alternatively, create callflows using vars and branching which is not available through the UI and would need to be implemented programmatically using the API. I don't recommend as changing callflows modified this way would be difficult.     

Link to comment
Share on other sites

We have many multi-loc businesses with branch locations. We take an unused area code and assign each device at each branch a DID in that unused area code. Then we simply create a callflow to grab exts not in the account and prepend the number with the DID to route to a resource that loops back into the system. So all you need in each account is a custom callflow and resource. Easy Peasy :) Been working wonderfully.

Here are the 2 docs as examples assuming the extensions are 6 digits (You can make the length whatever. Just make sure you fill in the DID with whatever to match 10 digits. in this example, i used a 9 as the filler) You can also create failover resources for your multiple zones.

PUT /resources

 

{

    "data": {

        "classifiers": {

            "unknown": {

                "enabled": true,

                "prefix": "+16739",

                "suffix": ""

            }

        },

        "flags": [],

        "gateways": [

            {

                "progress_timeout": 8,

                "privacy_mode": "sip",

                "server": "SERVER IP",

                "channel_selection": "ascending",

                "enabled": true,

                "endpoint_type": "sip",

                "force_port": false,

                "invite_format": "route",

                "port": 5060,

                "skype_rr": true

            },

            {

                "progress_timeout": 8,

                "privacy_mode": "sip",

                "server": "SERVER IP",

                "channel_selection": "ascending",

                "enabled": true,

                "endpoint_type": "sip",

                "force_port": false,

                "invite_format": "route",

                "port": 5060,

                "skype_rr": true

            }

        ],

        "media": {

            "audio": {

                "codecs": []

            },

            "video": {

                "codecs": []

            },

            "fax_option": false,

            "encryption": {

                "enforce_security": false,

                "methods": []

            }

        },

        "template_name": "Vinix East",

        "name": "Vinix East",

        "ignore_flags": false,

        "require_flags": false,

        "format_from_uri": false,

        "notes": "",

        "emergency": false,

        "enabled": true,

        "grace_period": 5,

        "rules": [],

        "weight_cost": 50

    }

}

 

 

 

 

 

 

PUT /callflows

 

{

    "data": {

        "flow": {

            "data": {

                "caller_id_type": "internal",

                "ignore_early_media": false,

                "outbound_flags": [],

                "use_local_resources": true

            },

            "module": "resources",

            "children": {}

        },

        "numbers": [],

        "patterns": [

            "^(\\d{6})$"

        ],

        "ui_is_main_number_cf": false,

        "name": "INTERNAL MULTI-LOC CF",

        "contact_list": {

            "exclude": false

        }

    }

}

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...