How to Set Up IVR in HubSpot Calling

What IVR in HubSpot is designed to do

IVR is an automated phone menu that asks callers to make a selection, usually by pressing a number on their keypad. Each selection then sends the call to a defined destination, such as a user, team, queue, external number or voicemail path, depending on the options available in the account.

For example, an inbound business number might offer:

• Press 1 for sales enquiries.
• Press 2 for customer support.
• Press 3 for billing questions.
• Press 0 for a general operator or fallback route.

The important design question is not how many options HubSpot can display. It is whether each option represents a real business need with a clear owner. A caller who selects support should not enter an undefined queue, and a billing option should not depend on someone manually noticing a message later.

Plan the call flow before changing HubSpot settings

Do not begin by writing the greeting. Begin by documenting what should happen to each common type of inbound call. This separates the operating logic from the product interface and makes testing easier.

1. Identify the caller’s likely intent. Group requests into a small number of categories that callers can recognize quickly.
2. Assign an owner to each category. Decide which user, team or external destination is responsible for the next action.
3. Define the unavailable path. Decide what happens when the owner is offline, busy or unable to answer.
4. Define failure behavior. Specify what happens after no input, invalid input or repeated failed attempts.
5. Define the business outcome. Decide whether the call should be answered, queued, recorded as a message, routed elsewhere or ended with useful instructions.

This sequence prevents a common systems problem: configuring menu choices first and discovering later that no one owns the resulting calls.

Requirements to check before setting up HubSpot IVR

Before configuring the menu, confirm that the account has the required calling capability and that the inbound number is connected. You should also have permission to edit the relevant calling settings.

Prepare the operational inputs as well:

• The inbound phone number that will use the menu.
• The users, teams or destinations that should receive each option.
• The greeting text or audio file.
• The regular business hours and time zone for the number.
• The after-hours destination and message.
• A test phone that is outside the HubSpot calling setup.

Subscription requirements and interface labels can change. Verify the current product availability and account permissions in HubSpot before treating a feature as part of the design.

How to set up an IVR menu in HubSpot Calling

1. Select the inbound phone number

Open the HubSpot settings area for calling and locate the inbound number that should use the IVR. If several numbers exist, confirm the number’s business purpose before editing it. A sales line, support line and regional line may need different greetings and ownership rules.

Record the current behavior before making changes. This gives you a reference point if the new menu creates an unexpected routing result.

2. Enable the IVR or call menu option

Within the selected number’s calling or routing settings, look for the available option for interactive voice response, an automated menu or similar call-handling behavior. Enable it only after confirming that the selected number is the correct inbound entry point.

The available configuration fields depend on the HubSpot account and current product interface. If the option is not visible, check the number type, subscription, permissions and current calling configuration before redesigning the process around an assumption.

3. Write a short, usable greeting

The greeting should tell callers what they can do and how to do it. Use the same words that appear in your internal routing plan. For example: “Thank you for calling. For sales, press 1. For customer support, press 2. For billing, press 3.”

Avoid internal terms that callers may not understand. If a category is too broad for one team to own, split it before recording the message. Keep the first menu focused on the most common decisions and provide a clear route for callers who do not fit a listed option.

4. Configure keypad options and destinations

For each selected digit, choose the appropriate destination from the options available in HubSpot. Depending on the account, this may include a specific user, a team or queue, another number or voicemail.

Map each route in a simple table before saving:

• Key: the number the caller presses.
• Intent: the reason the caller selected it.
• Owner: the team or person accountable for the next step.
• Destination: where HubSpot sends the call.
• Fallback: what happens if the destination cannot answer.

This table is also useful for future maintenance. When a team changes, you can update the owner and destination without guessing what the option was intended to accomplish.

5. Define no-input and invalid-input behavior

Some callers will not press a key, press the wrong key or wait until the menu repeats. Configure the available rules for these situations. Decide how many times the greeting should replay and where the call should go after repeated failures.

A sensible fallback might route to a general team, voicemail or a recorded instruction. Avoid a loop that repeatedly plays the menu without giving the caller a way forward. If a caller cannot use keypad input, consider whether the greeting should offer an alternative path, such as speaking to an operator or leaving a message.

6. Configure business-hours and after-hours behavior

Business hours should change the destination when availability changes, not merely change the greeting. During open hours, a selection may route to a live team. Outside those hours, the same selection may route to voicemail, an on-call number or a message explaining when a response is expected.

Check the time zone and review what happens around opening and closing times. A call that arrives just after closing should not be sent to a team that cannot answer it unless the process includes a reliable fallback.

7. Save and test the complete call journey

Test the IVR from an external phone after saving the configuration. Do not test only the intended route. Validate the exceptions that reveal whether the operating model is complete.

Test again after material changes to users, teams, numbers, business hours or routing rules. An IVR can appear correctly configured while still failing at the handoff point.

Operational rules for maintaining an IVR

An IVR is part of the call-handling process, so it should be maintained when the business process changes. Review it when a team is reorganized, a number changes, business hours change or a service is no longer supported.

Use call activity and feedback to identify practical problems, such as callers choosing the general option because the menu categories are unclear, repeated transfers caused by unclear ownership or high voicemail volume outside business hours. The purpose of reviewing this information is to support a decision, such as changing a menu option, reallocating ownership or improving the greeting.

For broader work involving HubSpot setup, CRM architecture, routing logic and reporting, see HubSpot consulting. If the calling process depends on connected tools, CRM consulting can help clarify the records, ownership rules and handoffs around the call.

As a hypothetical example, a support line may initially route every caller to one team. If call review shows that billing requests require a different owner, the process can be improved by adding a billing path, defining its after-hours behavior and testing the handoff. The improvement comes from clarifying the business state and owner, not from adding menu complexity.

When a HubSpot IVR should be redesigned

Consider redesigning the menu when callers regularly choose the wrong option, teams transfer calls repeatedly, no one owns a fallback queue or the greeting no longer matches the services you provide. A growing menu is not automatically a better menu. More choices can make the first decision harder and create more routes to maintain.

Before adding another option, ask three questions:

1. Is this a distinct caller need or only an internal team distinction?
2. Does the destination have a named owner and a workable availability rule?
3. Will the new route improve a decision or simply move complexity into the phone menu?

If the answer to the second question is no, fix the ownership process before changing the IVR. Technology can execute a routing decision, but it cannot supply a missing business decision.