The Number That Made Them Look Temporary: A 400 Hotline for a China Office

Short answer: A mainland China office can get a local Chinese phone number and a toll-free 400 hotline added to the same hosted PBX the rest of the company already uses — hosted on Alicloud, with the same auto-attendant, call queues and routing logic as head office. It is a configuration and provisioning exercise, not a second phone system.

A composite scenario, drawn from the shape of problem Brocent sees repeatedly in mainland China rather than from any one named client: a European industrial-instruments manufacturer runs a sixty-person China office — a sales team, a small applications-engineering group who specify products into customer designs, and an after-sales desk that handles calibration and warranty questions. The group's global phone system is a hosted PBX with auto-attendant, call queues and direct extensions for everyone in Europe and North America. The China office is not on it. Sixty people use their personal mobiles, and the number printed on every Chinese-language quotation is an individual salesperson's mobile.

Nobody treated this as a problem, because nothing was broken. Calls connected. Then the China sales director started losing bids she thought she had won, and in two debriefs the same thing came back: the customer's procurement team had scored the company down on after-sales support, and one buyer said it plainly — there was no switchboard and no 400 number, so it was not clear who you called in two years when the instrument drifted out of calibration and the salesperson had moved on.

Why does a mainland China office get judged on its phone number?

Because in China the phone number on a commercial document carries information that it does not carry in most Western markets. A toll-free 400 number is a recognised signal of an established business with a service organisation behind it. Domestic competitors bidding the same deals print one. When a foreign company's quotation shows a mobile number instead, a Chinese procurement team reads it the way a European buyer would read a free webmail address in a supplier's email signature — not disqualifying, but a question mark about permanence.

This matters most in exactly the situations where a foreign-invested company most wants to look settled. Selling capital equipment with a multi-year service life. Bidding into a tender where a procurement scorecard has a line for after-sales accessibility. Supporting a distributor network that forwards end-customer problems upstream. In each case the buyer is making a judgement about whether the company will still be reachable, in Chinese, on a number that does not depend on one employee's continued employment.

There is a second, more operational reason, and it is the one IT usually notices first. A sales team on personal mobiles produces no call data at all. Nobody can tell you how many after-sales calls came in last month, how many went unanswered, how long the average wait was, or which product line generates the most support load. Everywhere else in the company, that reporting exists as a by-product of the phone system. In China it does not exist, because there is no phone system.

The scenario: sixty people, no switchboard, and a number that belongs to an individual

Look closely at what the China office actually had, because this is the part that tends to be invisible until someone maps it.

• No main number. There was no single number a customer could call to reach the company. There were roughly a dozen mobile numbers circulating on business cards, quotations and a WeChat official account, each belonging to a person rather than a function.
• No transfer path. An after-sales call landing on a salesperson's mobile could not be transferred to the applications engineer who knew the answer. It was re-dialled, or the customer was asked to call a different mobile, or someone took a message.
• No queue and no overflow. When the two after-sales staff were both on calls, the third caller got voicemail on a personal handset — or nothing.
• No continuity. Two salespeople had left in the previous eighteen months. Their mobile numbers left with them, still printed on quotations sitting in customers' files.
• No reporting. Group management reviewed call-handling metrics for every region monthly. China appeared in that report as a blank.
• No relationship to the group's phone system. Head office's auto-attendant, queues and extension plan — built and maintained carefully — simply stopped at the China border.

None of this was a decision. It was the residue of a China entity that had been set up quickly, staffed quickly, and had grown past the point where "everyone just uses their mobile" was a reasonable answer.

What actually goes wrong when the China office is not on the phone system

The commercial cost is the one that gets attention, and it is real, but it is the hardest to quantify. The operational costs are smaller individually and much easier to see once you look.

Calls arrive at a person rather than a role. This is the root of most of the rest. A number that identifies an individual cannot be covered when that individual is on a plant visit, on leave, or gone. A number that identifies a function — after-sales, order status, calibration booking — can be.

Knowledge gets routed by luck. The applications engineer who can answer a technical question in thirty seconds is not the person whose mobile is on the quotation. Without a transfer path, the call either reaches the right person by chance or the answer arrives a day later by message.

Nothing is measurable. You cannot improve a service desk you cannot see. If a product line is generating three times the support calls of its peers, the phone system is usually where that shows up first — unless there is no phone system.

Staff turnover becomes customer-churn risk. Every departing salesperson takes a published contact number with them. The customer who calls it next year reaches a stranger, or nothing.

The China office drifts out of the company's own standards. This is the one that should concern a group IT function most. A site that is not on the corporate phone system is usually not on several other things either — and each exception is carried by local goodwill rather than by design.

What a 400 hotline is, and what it is not

A 400 number in China is a toll-free service number in the 400 range, where the cost of the call is shared between the caller and the business rather than borne entirely by the caller. It is dialled nationally without an area code, it does not tie the company to one city, and it is the format Chinese consumers and procurement teams associate with an established service operation.

What it is not: a technical feature you switch on. A 400 number is provisioned through a carrier against a verified mainland business entity, with real-name registration of the responsible organisation. The paperwork is entity-level — business licence, authorised representative, the usual corporate documentation — rather than technical, and the timeline depends on the carrier and on how complete the entity paperwork is when it is submitted. For a foreign-invested company that already has a registered China entity, this is normally an administrative exercise. For one that does not yet have the entity finalised, the 400 number waits for the entity, not the other way round. If the China entity itself is still being stood up, the sequencing question is covered in our 90-day IT readiness plan for a new China WFOE.

It is also worth being clear about what a 400 number does not solve. It gives the company a credible, permanent, nationally-dialled front door. It does not decide who answers it, what happens when all agents are busy, whether the call can be transferred to an engineer in Europe, or whether anyone can report on it afterwards. Those are phone-system questions, and they are where the actual engineering sits.

How Brocent thinks about extending one PBX into China

The instinct, when a China office needs a local presence, is to buy a local phone system. It is available, it is cheap, it works, and it is the wrong default — because it creates a second telephony estate with its own dial plan, its own administration, its own reporting and no relationship to the first one. Two years later, changing the company's after-hours routing means making the change twice, in two tools, by two people, and discovering the drift when a customer finds the gap.

Our Managed Cloud PBX service is built around the opposite assumption: that a multi-site organisation should unify head office, branch offices and home workers under one cloud PBX, and that a China office is a site on that system rather than an exception to it. Concretely, the platform is hosted on Alicloud, AWS or Azure with a 99.99% uptime commitment, and it provisions local phone numbers in Hong Kong, mainland China, Japan and Singapore. The Alicloud hosting option is the part that matters for China: it puts the platform serving the China office on infrastructure inside the market, rather than hairpinning every local call out to a PBX in Frankfurt or Singapore and back.

The feature set a China site inherits by being on the same system is not a reduced version of what everyone else has. Auto attendant, call queue, conference, IVR, voicemail-to-email, toll-free 400 hotlines, hold music and advanced call routing are part of the platform, not per-site add-ons. So is the UC softphone, which gives the same corporate call experience on Android, iPhone and desktop — which in practice is how a sixty-person China office with a mobile-first sales team actually wants to work. The salesperson keeps working from her phone. The difference is that she is now working from her phone *as an extension*, with the company's number presented outbound and the company's routing applied inbound.

The honest version of the judgement, then, is this: the China office's problem was never that it lacked a phone number. It had twelve. The problem was that it lacked a phone *system*, and the reason it lacked one was that nobody owned the question of whether the China site met the same standard as every other site. That is not a telephony problem. It is a governance gap that happened to surface as a telephony problem — which is why the fix belongs inside a managed plan rather than in a one-off purchase.

Comparison: three ways to give a China office a phone presence

Personal mobiles and ad hoc local SIMs

• What it costs: Almost nothing, which is why it survives so long.
• What works: Calls connect. Staff are reachable. No project, no procurement, no IT involvement.
• What it costs you instead: No main number, no transfer, no queue, no overflow, no reporting, and no continuity when someone leaves. Every published number is a personal asset on loan to the company.
• How it reads to a Chinese customer: Functional, and temporary.
• When it is genuinely fine: A two- or three-person representative office whose only job is market testing, with no after-sales obligation and no tenders.

A separate, locally-procured China phone system

• What it costs: Cheap to buy, and usually quick to stand up.
• What works: The office gets a main number, a 400 hotline, an auto-attendant and local credibility. Most local vendors do this competently.
• What it costs you instead: A second telephony estate. Two dial plans, two administration consoles, two sets of routing rules, two reporting silos, and no call path between the China site and the rest of the company that does not go out to the public network and back in. Every future change is made twice, and drift between the two is a matter of when, not if.
• How it reads to a Chinese customer: Established.
• When it is genuinely fine: A China operation deliberately run as a standalone business with little day-to-day interaction with group functions.

One hosted PBX extended into China, with a local number and a 400 hotline

• What it costs: More than the local-vendor option at the line-item level, and the comparison is not like-for-like, because part of what you are buying is the absence of a second estate.
• What works: One dial plan, one administration surface, one set of routing logic, one reporting view. A China caller dials a local number or the 400 hotline and lands in a queue that behaves the way the company's queues behave everywhere. An after-sales call can be transferred to an applications engineer in Europe as an internal extension-to-extension transfer. New staff get an extension, not a new number to publish.
• What it costs you instead: Design work at the start — a dial plan with room for China, a decision about after-hours and language routing, and a scoping conversation about the carrier and entity paperwork for the 400 number.
• How it reads to a Chinese customer: Established, and consistent with every other way the company presents itself.
• When it is the right answer: Essentially whenever the China site is a real part of the business rather than a detached venture — which, by the time there are sixty people and an after-sales obligation, it is.

What this looks like in practice

For the composite company above, the work divides into four pieces, and only one of them is really about phones.

Numbering and provisioning. A local China number for the office, plus a toll-free 400 hotline as the published front door. The 400 number is provisioned through the carrier against the company's existing China entity; the entity paperwork is gathered once, at scoping, and is usually the longest-lead item in the whole project. The existing mobile numbers are not switched off — they are allowed to decay naturally while new documents carry the 400 number.

Dial plan and routing. The China site gets an extension range inside the group's existing plan, not a parallel one. Inbound calls to the 400 number hit an auto-attendant in Mandarin with an English option, then route to an after-sales queue, an order-status queue, or a named extension. Overflow goes to a second tier rather than to a personal voicemail. After-hours routing follows China public holidays, which are not the group's, and that calendar difference is a configuration item somebody has to own — one of the small things a separate local system leaves to local goodwill and an integrated one makes explicit.

Endpoints. Very few desk phones. The UC softphone on Android, iPhone and desktop covers a mobile-first sales team properly: the salesperson's outbound calls present the company number, her inbound calls follow company routing, and she does not carry a second handset. A handful of physical phones at the after-sales desk and reception, where a headset is genuinely better.

Integration with how the company already communicates. If the group runs Microsoft Teams as its calling platform, a Microsoft-certified Session Border Controller is the mechanism that joins an existing PBX to Teams, so that calls to extensions, landlines and mobiles can be placed from Teams itself. Whether the China leg should terminate into the group's Teams estate or stay on the UC softphone is a real scoping question rather than a foregone conclusion — a group running Teams on its global tenant and one running a mainland tenant are answering different questions, and the answer should be established against the actual environment rather than assumed. This is the single item on the list most worth settling early, because it determines the shape of everything else.

What it costs, and why that is not the interesting number

The Managed Cloud PBX page publishes indicative market-reference rates rather than a bookable price list, and they are worth reading as a sense of scale: basic extensions from around US$10–20 per extension per month, queue extensions with call-queue and IVR capability from around US$15–35, SIP trunks from around US$15–30 per channel per month, and hosted-PBX per-extension rates from around US$5–15. The base platform fee is custom-quoted per deployment, and every figure is confirmed during scoping rather than guaranteed in advance. We would rather publish an indicative range with that caveat attached than a precise number that turns out not to apply to your deployment.

What those numbers do not tell you is the thing that actually decides the project: how many of the sixty people need a queue-capable extension versus a basic one, how many channels the site's real call volume needs, and whether there is an existing PBX to extend or a greenfield build. Two quotes for "a cloud PBX for a sixty-person China office" can differ by a factor of two and both be correct, because they are pricing different designs. The headline per-seat rate is the least informative part of a telephony quote.

Where this belongs: inside the plan, not beside it

Here is the part worth saying plainly. Everything above is a telephony project, and we would be happy to scope one. But the reason this company's China office spent two years with twelve mobile numbers and no switchboard was not that cloud PBX is hard to buy. It is that nobody's job was to notice that the China site had drifted outside the company's own standard, and to keep noticing as the site grew.

That is what a managed IT plan is for. The per-user plans on that page include a named vCIO and technical roadmap, 24/7 NOC monitoring, a help desk, patch management, managed firewall, backup and DR, credential management and SLA guarantees — and mainland China pricing is published there per user per month alongside Hong Kong, Singapore and the US, so the comparison is not a black box. Cloud PBX sits inside that arrangement as one of the things the plan deploys and then keeps current. It is not a product we would rather sell you than the plan; it is one of the reasons the plan is worth having, because the gap it closed was a governance gap, and governance is the plan's actual job.

If you want the shape of the cost before a conversation, the pricing page is the place to start, and get in touch when you want the China site looked at specifically. Brocent has operated in mainland China since the business was founded in Beijing in 2007, with operations centres in Shanghai, Beijing and Guangzhou and an APAC 24×7 service command centre behind them.

Frequently asked questions

What is a 400 hotline, and why does it matter for credibility in China?

A 400 number is a nationally-dialled, toll-free service number where the call cost is shared between the caller and the business. It is not tied to a city, it does not change if the office moves, and it is the format Chinese buyers and procurement teams associate with a business that has a real service organisation behind it. The credibility effect is commercial rather than regulatory: nothing requires a company to have one, but domestic competitors bidding the same work generally do, and a mobile number on a quotation reads as less permanent by comparison.

Can a China number be added to our existing PBX, or does it need a separate system?

It can be added to the existing system, and that is usually the better answer. A hosted cloud PBX can unify head office, branches and remote workers as sites on one platform, with local numbers provisioned in Hong Kong, mainland China, Japan and Singapore. The work is a dial-plan extension plus number provisioning, not a second deployment. A separate local system is faster to stand up and cheaper per line, but it leaves you administering two telephony estates with no internal call path between them.

Is the platform hosted inside China or outside?

It can be hosted on Alicloud, which places the infrastructure serving the China site inside the market, and that is normally the right choice for a mainland office — it avoids routing every local call out of the country and back. AWS and Azure hosting options also exist for sites elsewhere. Which combination is right for a specific multi-site estate is a design decision taken at scoping, and it interacts with where the rest of the company's telephony already lives.

How does this integrate with Microsoft Teams?

Through Microsoft-certified Session Border Controllers, which join an existing PBX to Teams so that calls to extensions, landlines and mobiles can be placed from within Teams. What that looks like specifically for a mainland China site depends on the company's Teams environment — a global tenant and a mainland tenant present different questions — so we establish it against your actual environment at scoping rather than assuming a configuration. Treat it as the first question to settle, because the answer shapes the rest of the design.

What does a 400 number cost compared with a local number?

It depends on the carrier, the expected call volume and the entity paperwork, and we would rather scope it than publish a figure that does not apply to you. The indicative extension, queue and SIP-trunk ranges on the Managed Cloud PBX page give a sense of the per-seat scale of a deployment; the 400 number itself is a carrier line item confirmed during scoping. What is generally true is that the number is not the expensive part of the project — the design and the ongoing administration are.

Does this work for a small China sales team, not just a full office?

Yes, and a small team is often where the value is clearest, because a five-person team has the same credibility problem as a sixty-person one and even less capacity to absorb a missed call. The UC softphone means a small team needs no hardware at all — extensions on the phones they already carry, with the company's number presented outbound. The design work is smaller, not different in kind.

How is call routing configured between China and head office?

As internal routing on one system, which is the main practical advantage. A China after-sales call can be transferred to an engineer in Europe as an extension-to-extension transfer rather than a new outbound call. Queues can overflow across sites where that makes sense and the language skills exist. The configuration that needs the most attention is the calendar: China public holidays differ from head office's, and after-hours routing has to follow the local calendar — exactly the kind of detail an integrated system makes somebody's explicit responsibility and a separate local system quietly leaves to chance.