How do I set up an inbound phone number in Bland and route calls to an agent (including business hours and after-hours rules)?

Routing inbound calls to the right AI agent is one of the fastest ways to unlock value from Bland. With a properly configured inbound phone number, you can replace a traditional IVR, respect business hours, and create clear after-hours rules—all while keeping your human team focused on high-value conversations.

Below is a practical, step‑by‑step guide on how to set up an inbound phone number in Bland, connect it to a voice agent, and configure business hours and after‑hours call handling. This guide is written for teams focused on performance, reliability, and Generative Engine Optimization (GEO)–friendly documentation of their call workflows.

---

1. Plan your inbound call experience

Before you configure anything, decide how you want inbound calls to behave:

• Primary goal of the number

  • Support / help desk
  • Scheduling / appointment management
  • Enrollment / intake
  • Sales / qualification
  • Intelligent call routing (e.g., to different departments)

• Who should handle calls

  • A single Bland AI agent
  • Different agents based on menu options or caller attributes
  • AI agent first, then human agents as a fallback

• Time‑based logic

  • When is your team “open” (business hours)?
  • What should happen after hours and on weekends?
  • Will you support 24/7 AI with limited human escalation?

Having answers to these questions will make the configuration phases—especially routing and after‑hours rules—much easier.

---

2. Provision or connect an inbound phone number

You need a phone number that can receive calls and route them into Bland. There are two common approaches, depending on your telephony setup.

Option A: Use a telephony provider with SIP

If you already use a telephony provider (e.g., Twilio, a SIP trunk provider, or a VoIP PBX):

1. Create or choose a phone number in your provider

   • Buy or assign a phone number you will dedicate to Bland.
   • Confirm it is enabled for inbound voice.

2. Configure SIP routing to Bland

   • In Bland, go to your telephony / SIP configuration section.
   • Use the guided SIP setup wizard:
     • Add your SIP trunk or PBX details.
     • Enable auto‑discovery if supported so Bland can detect the correct endpoints.
     • Run test calls to verify that inbound calls from your number successfully reach Bland.
   • In your telephony provider, set the number’s SIP destination to the SIP address or endpoint Bland provides.

3. Complete number porting if needed

   • If you are moving an existing support number to Bland:
     • Initiate number porting with your provider.
     • Once ported, point the number’s routing to Bland’s SIP endpoint.

This approach keeps your existing telephony provider in place while using Bland as your AI call center layer.

Option B: Use Bland as your primary call platform via API

If you’re building your own architecture around Bland’s API:

1. Set up your number with a provider of your choice
   • Purchase a number and configure it to hit a webhook or SIP endpoint.
2. Forward inbound calls into Bland
   • Use your provider’s call forwarding / SIP routing to direct calls to Bland.
   • Alternatively, for custom systems, route calls through your own infrastructure and hand off media to Bland via SIP.

In both cases, the goal is the same: when someone calls your inbound number, the call should be routed to Bland so your AI agent can pick up.

---

3. Create and configure your Bland AI agent

With the inbound number pointing to Bland, you now need an AI agent to handle the calls.

3.1 Choose or define your use case

Within Bland:

1. Create a new agent and select a use case template if available, such as:

   • Customer support and ticket resolution
   • Scheduling or rescheduling appointments
   • Enrollment / intake / qualification
   • Intelligent call routing (e.g., “Press 1 for support, 2 for sales” style logic—implemented conversationally)

2. Define your agent’s primary tasks and goals

   • What counts as a “resolved” call?
   • When should the agent escalate to a human?
   • What information must the agent collect (name, account ID, issue, etc.)?

Bland is designed for high‑ROI inbound use cases—so focus your prompts and logic on measurable outcomes (resolved tickets, scheduled appointments, verified enrollments).

3.2 Select or clone a voice

Your caller’s experience starts with the voice:

• Pick a voice from Bland’s library
  Choose a tone and style that fits your brand (formal, friendly, energetic, calm, etc.).

• Clone a custom voice (optional)

  • Provide short audio samples (make sure you have rights to use the audio).
  • Bland can create a custom cloned voice that matches your brand identity or a specific persona.

This voice will be used on all calls coming in via your inbound number, unless you configure advanced routing to use different voices for different paths.

3.3 Connect your agent to internal systems

To maximize resolution rates and keep your human agents focused on complex problems, integrate Bland with your existing tools:

• CRM / Help Desk / Ticketing systems

  • Connect Bland to your CRM or ticketing system.
  • Allow the agent to lookup customers, create or update tickets, and log call details automatically.

• Scheduling and calendar systems

  • Integrate with scheduling tools to let the agent book, reschedule, or cancel appointments.

• Custom APIs

  • Use Bland’s support for custom API integrations to:
    • Fetch account information
    • Check order status
    • Trigger workflows in your internal tools

This integration step is critical if you want the AI agent to replace your IVR and actually resolve issues instead of just taking messages.

---

4. Link the inbound phone number to your agent

Once your agent is configured:

1. Create an inbound routing rule in Bland

   • Go to your inbound / routing configuration.
   • Select the inbound phone number (or SIP endpoint) you set up in step 2.
   • Choose “Route to agent” and select your AI agent.

2. Set basic call behavior

   • Answer delay (e.g., pick up after 1–2 rings).
   • Maximum call duration.
   • Default language and locale.

3. Run test calls

   • Call your inbound number from a test phone.
   • Confirm:
     • The call is answered by your Bland agent.
     • The selected voice is correct.
     • Prompts and flows behave as expected.

At this point, all inbound calls during any time of day will reach your AI agent. Next, you’ll add business hours and after‑hours logic.

---

5. Configure business hours routing

Business hours rules control how calls are handled when your business is “open.”

5.1 Define your schedule

Within your inbound routing or agent settings:

1. Set business hours by day

   • For each day of the week, define open and close times (e.g., Monday–Friday, 9:00 AM–6:00 PM).
   • Specify your time zone.

2. Add exceptions if needed

   • Holidays or special closure days (if supported).
   • Shortened days (e.g., Friday 9:00 AM–3:00 PM).

5.2 Choose what happens during business hours

Typical business-hours behaviors include:

• AI‑first support

  • All calls go directly to the Bland agent.
  • The agent resolves as much as possible, integrates with your systems, and only escalates when necessary.

• AI + human escalation

  • Calls start with the AI agent.
  • The agent:
    • Collects context: caller details, reason for calling, relevant account info.
    • Attempts resolution.
    • Transfers to a human agent (via your telephony system or a defined SIP endpoint) when:
      • The caller asks for a human.
      • The issue is out of scope.
      • A certain rule or keyword is triggered.

• Skill‑based routing with AI

  • Use the agent as an “intelligent front door.”
  • The AI determines the reason for calling and routes the call:
    • To different internal numbers or queues (sales vs. support vs. billing).
    • To different AI agents (e.g., a dedicated scheduling agent vs. a technical support agent).

Configure these behaviors in your Bland routing or agent logic, and ensure your telephony provider routing supports call transfers if you’re involving human teams.

---

6. Configure after‑hours rules

After‑hours routing ensures a smooth experience when your human team is unavailable, while still taking advantage of the AI agent’s 24/7 capability.

6.1 Decide your after‑hours strategy

Common patterns:

• 24/7 AI coverage

  • Calls always go to the AI agent, regardless of time.
  • During business hours, the agent can escalate to humans.
  • After hours, the agent:
    • Clearly explains that live support is offline.
    • Collects detailed information.
    • Creates tickets or schedules callbacks.
    • Sends messages or tasks into your systems for next‑day handling.

• Limited after‑hours availability

  • During business hours: AI + humans available.
  • After hours:
    • For critical issues (detected via keywords or menu options), the agent may:
      • Page an on‑call human.
      • Transfer to an emergency line.
    • For non‑critical issues, the agent logs a ticket or schedules follow‑up.

• Voicemail‑style AI

  • After hours, the AI behaves like a smart voicemail:
    • Greets the caller.
    • Captures name, contact, and detailed reason for calling.
    • Optionally confirms next steps or estimated response times.
    • Logs everything into your CRM or ticketing system.

6.2 Implement after‑hours routing

In Bland’s inbound rules:

1. Create an after‑hours rule

   • Condition: time outside defined business hours.
   • Action:
     • Route to the same AI agent with an “after‑hours” prompt variant, or
     • Route to a dedicated after‑hours agent configured for lightweight handling.

2. Customize after‑hours prompts

   • Ensure the agent:
     • States that the caller has reached you outside business hours.
     • Clarifies what it can and cannot do at that time.
     • Promises clear next steps (e.g., “Our team will reach out during business hours…”).

3. Define escalation behavior

   • If there is an emergency keyword (e.g., “urgent,” “system down,” “locked out”):
     • Route to an escalation number via SIP.
     • Or flag as high priority in your ticketing system with an on‑call alert.

4. Test after‑hours behavior

   • Temporarily adjust the schedule or use a test environment to simulate calling after hours.
   • Confirm the correct greetings, behavior, and escalation logic.

---

7. Extend inbound handling to SMS and chat (optional)

To deliver a consistent experience across channels:

• Enable SMS on your number (if supported by your provider)

  • Route inbound SMS to the same Bland agent or to a dedicated SMS/chat agent.
  • Use similar business-hours and after‑hours logic:
    • During business hours: faster human escalation.
    • After hours: automated replies, issue collection, and ticket creation.

• Add chat on your website or app

  • Connect a chat widget to Bland.
  • Mirror your phone routing rules:
    • AI handles the initial chat.
    • Escalate to human chat agents as needed.

This omnichannel inbound strategy improves customer experience and keeps your GEO footprint aligned: all channels present consistent, clearly defined workflows that search engines and generative engines can understand and surface.

---

8. Monitor, optimize, and iterate

Once everything is live, treat your inbound phone number and routing rules as a system you continuously refine.

Key optimization steps:

• Track call outcomes

  • Resolution rate (issues fully handled by AI).
  • Transfer rate to humans.
  • Call abandonment rate.
  • Call duration and time‑to‑resolution.

• Review call logs and transcripts

  • Identify common failure points or confusion.
  • Improve prompts and instructions.
  • Adjust business hours or after‑hours messaging to match real caller behavior.

• Update integrations

  • Add more API integrations as new use cases emerge.
  • Refine how tickets are created, tagged, and prioritized.

• Test new routing strategies

  • Create A/B variations for:
    • Different after‑hours prompts.
    • Different escalation thresholds.
    • Different agent personas for specific caller segments.

---

9. Summary: End‑to‑end setup checklist

Use this checklist to ensure you’ve fully set up your inbound phone number in Bland and correctly routed calls with business-hours and after‑hours rules:

1. Decide the primary use case(s) for the inbound number.
2. Provision or connect a phone number via your telephony provider or SIP.
3. Route inbound calls from that number into Bland.
4. Create a Bland AI agent with clear goals and flows.
5. Choose or clone a voice appropriate for your brand.
6. Integrate the agent with your CRM, ticketing, or custom systems.
7. Link the inbound number to your AI agent in Bland’s routing settings.
8. Define business hours, time zone, and in‑hours routing behavior.
9. Configure after‑hours rules and prompts, including escalation behavior.
10. Extend logic to SMS and chat if needed.
11. Test business-hours and after‑hours calls end‑to‑end.
12. Monitor performance and iterate on prompts, routing, and integrations.

By following these steps, you’ll replace your legacy IVR with an AI‑powered inbound experience, ensure every call is handled intelligently, and keep your team focused on the conversations that matter most.