# Your contact center. Connected.

Keep the queues, agent workflows and customer context your contact center runs. Use Bird for the telephone connection, numbers and call evidence, with an integration plan that covers normal traffic and the calls that need another path.

[Start for Free](/dashboard/signup?returnTo=%2Fdashboard%2Fw%2Fvoice%2Fonboarding)

[Contact sales](/demo?product=voice-contact-center)

## Set up with your agent

[Read the agent setup guide](/docs/ai/set-up-your-agent)

Copy this prompt into your coding agent:

```text
Bird connects customer communications, data and automation. Help me build with Bird using my coding agent.
1. Read https://bird.com/docs/ai/set-up-your-agent.md and follow its setup workflow for this client. Use an existing connected Bird MCP server or signed-in CLI when available.
2. Read the product guide for the task I want to complete and inspect my existing integration. Identify the workspace, available operations and required setup.
3. Help me complete a first example for the product and destination I choose. Follow the operation through to its actual result, explain any uncertainty, and help me choose the next step.

First task: Inventory the PBX or contact-center application, queues, transfers, conferences, numbers and current carriers. Prepare an integration, capacity and rollback brief for a Voice specialist. First use the connected Bird MCP server or signed-in CLI for a read-only inventory. Discover the available tools and read their schemas or help; do not invent call-control operations. If neither surface is available, follow https://bird.com/docs/ai/set-up-your-agent.md. Read the linked guides through their .md alternatives. Present the exact target and configuration before changing routing, placing calls, recording audio, purchasing numbers or submitting a port. Obtain my approval for those actions.

Use this Bird page as the starting context: https://bird.com/products/voice/contact-center
Read its Markdown alternative and linked guides. Keep the first example relevant to this page and the customer outcome I choose. Preserve the supplied campaign context when following Bird signup or sales links.
```

Your contact center, connected

Bird Voice

Numbers · SIP connectivity · call records

Your contact center

Queues · transfers · conferences · agents

Your business systems

Customer context · actions · outcomes

Trusted every day by teams that build world-class software

[Read more customer stories](/customers)

- [Airwallex](/customers/airwallex)
- [Glovo](/customers/glovo)
- [Zillow](/customers/zillow)
- Uber
- [Binance](/customers/binance)
- Adobe
- Meta
- PayPal
- Pinterest
- Square
- [Al Jazeera](/customers/aljazeera)
- [Aramex](/customers/aramex)
- [Bazaar Technologies](/customers/bazaar)
- [ComparaOnline](/customers/compara)
- [Emma](/customers/emma)

## How does Bird connect to a contact center?

Connect a SIP-capable contact center or PBX to Bird trunks. Incoming numbers route calls to your delivery gateways; the contact center handles queues, agent selection, transfers and conferences. Outbound calls use the trunk and an eligible caller identity. Evaluate these boundaries together before moving traffic.

## Plan for the calls that cross a boundary.

### From a queue to a person

Keep the queue, routing rules and customer record in the system that already owns them. Test what happens when no agent answers, a queue closes or a gateway becomes unavailable.

### From an agent to a conference

Conferencing and transfer behavior depend on your PBX or application. Check signaling, participant changes, caller identity and media on every leg. A working basic call is only the first integration check.

### From an AI assistant to your team

Define the point where a conversation moves to a person and the context that accompanies it. Test interruption, transfer failure and the experience when nobody can take the call.

## Bring an operating brief, then prove one complete journey.

Document peak concurrent calls, calling rate, countries, number inventory and the service requirements your team works to. Review the proposed architecture with a Voice specialist. Run a representative journey through connection, handling, recording where needed and final reconciliation before widening the rollout.

Name the systems responsible for queues, conferences, recording, speech and customer data. Assign an operational owner to each handoff.

Keep a tested route back to the existing service. Agree on the signals that stop a rollout and the person who can restore the previous route.

Measure answer rate, audio behavior, failure stage and customer task completion separately. Review results by destination and call path.

## Questions before you connect

### Does a SIP trunk replace my contact center software?

A trunk supplies telephone connectivity. Your contact center application continues to own its agent desktop, queues, workforce processes and conference behavior.

### Can the Bird browser phone replace a full agent desktop?

The browser phone provides a controlled outbound calling path. Scope a contact center integration around the agent, incoming-call, queue and transfer capabilities your application needs.

### How should we plan a larger migration?

Start with the current number and application inventory, capacity requirements and a test plan. Verify provider-specific dependencies, agree on continuity and expand from a controlled set of calls.

## Build the rest of the calling path

[Voice overview](/products/voice) Choose the calling path for your customer journey.

[SIP trunking](/products/voice/sip-trunking) Connect your PBX, softphone or SIP application to the telephone network.

[Voice numbers](/products/voice/numbers) Coordinate number routing and caller identity.

[AI Voice](/products/voice/ai-voice) Bring a conversational runtime to the phone, with your context, tools and handoff.

[Voice pricing](/pricing/voice) Review the current destination rates and call components.

## Bring your contact center architecture.

Share your PBX, number inventory, destinations and peak traffic. Work through the integration and evaluation plan with a Voice specialist.

[Read the SIP integration guide](/docs/guides/voice/sip-trunks)



## Related resources

- [Voice overview](/docs/guides/voice/overview) (docs)
- [What is a voice API?](/explained/voice/what-is-a-voice-api) (answer)

[Get an implementation brief](/learn/workspace?topic=voice)
