Three Extra Sentences That Changed Which "Got Racks?" I Replied First
Two "got racks?" messages in a Telegram group, separated by ten minutes. Only one carried power, location, and timeline. For a data center presales engineer scanning group chats, that difference decides whether you are checking inventory or building a proposal.
Signals to watch
- Power figure (kW per rack) and quantity appear together
- Geographic target is named
- not implied
- Delivery timeline is stated
- not open-ended
Eight forty in the morning. You sit down, open Telegram. The colocation industry groups you follow already have hundreds of unread messages. You scroll chronologically and stop at one:
“Got racks?”
Your finger hovers. Reply, and it could be a waste of time if the person is just fishing. Skip it, and you might miss an actual lead.
You keep scrolling. Another one:
“Got racks? 12 cabinets at 8 kW each, Hong Kong, need to go live within 45 days.”
Both messages ask the same core question, but your gut reaction is completely different. Why?
This article uses a simulated pair of Telegram group exchanges to unpack what turns “got racks?” from a vague stock check into a request you can price. All dialogue, figures, and scenarios below are illustrative or composite and are used only to demonstrate the evaluation method.
Two messages, ten minutes apart
Imagine you are in a Hong Kong colocation matching group. One morning two messages appear (simulated/composite scenario):
Message A (10:02 AM)
User A: Got racks? User A: Hong Kong. Send me a quote.
Message B (10:12 AM)
User B: Got racks? 12 cabinets at 8 kW each, Hong Kong, need to go live within 45 days. Off-the-shelf or custom build?
If you are three months into the presales role, the two messages look similar — both want Hong Kong cabinets, both want a quote. You might reply to Message A first, since it came earlier.
But a more experienced colleague will answer Message B first. Not because of favoritism. Message B carries three extra sentences.
Those three sentences turn a vague stock inquiry into a request with basic parameters.
Message A: just a price check
Look back at Message A. The user said two things: ask if there are racks, ask for a quote. That is it.
You may have dozens of cabinet resources — Hong Kong, Singapore, Jakarta — power from 4 kW to 12 kW. But you do not know what this person needs: not the power, not the quantity, not the timeline.
“Send me a quote” in the colocation industry says almost nothing useful. A single cabinet’s monthly rate depends on a dozen variables: power feed type (single or dual feed), power capacity, bandwidth bundle, contract length, whether a fixed IP is included, facility tier (Tier III or Tier IV) … A price quoted without these parameters is meaningless when the recipient tries to compare vendors.
More importantly, you cannot tell whether this person is actually sourcing colocation. They could be asking “are Hong Kong cabinets expensive” for a friend, or collecting price lists from multiple providers without any real project timeline.
If you drop your current ticket to check resources, look up pricing, and build a quote, the most likely outcomes are: the person says “I’ll take a look” and goes silent, or you ask “what power do you need” and they cannot answer.
None of this means Message A should be ignored. But with limited time and limited resources, it should not come before Message B.
Message B: three extra sentences
Message B adds three critical pieces of information right after “got racks?”.
First: 12 cabinets at 8 kW each.
“12” and “8 kW” together draw a concrete requirement profile. 8 kW per cabinet is medium-to-high density — suitable for high-performance computing or dense deployments. Twelve cabinets is not a handful; it needs a full or half row of floor space.
With that number, you can immediately match it against your Hong Kong resources: which data halls can deliver 8 kW per cabinet? Those that cannot are out.
Second: Hong Kong.
The location is locked. You do not need to scan your entire Asia-Pacific inventory. You focus on Hong Kong facilities. This also reveals an implicit signal — the person asks “off-the-shelf or custom build,” which means they care about delivery speed and do not want the timeline that comes with a new build.
Third: need to go live within 45 days.
This is the easiest sentence to overlook and the most important. A 45-day window tells you several things:
- Standard delivery cycles run 30 to 60 days. Forty-five sits right at the edge.
- You need existing floor space with vacant cabinets, not a new build circuit path.
- The person’s project may already have a customer contract pushing the deadline.
Put the three sentences together, and your brain can do far more work than with Message A. You are not checking “do I have stock.” You are judging “can I satisfy this specific set of requirements.” Only after power, location, and timeline all check out do you move to pricing.
Three numbers turn “check stock” into “build a proposal”
Compare what the two messages do to your workflow:
| Decision point | Message A | Message B |
|---|---|---|
| Do you know what resources to look up? | No — Hong Kong cabinets could mean any power range | Yes — Hong Kong, 12 cabinets at 8 kW each |
| Do you know the go-live timeline? | No — not mentioned | Yes — 45 days, urgent |
| Can you make a first pass on feasibility? | No | Yes — check whether your Hong Kong halls have 8 kW capacity |
| How many questions before you can quote? | At least 3–5 (power, quantity, timeline, bandwidth, contract term) | 1–2 (bandwidth and contract term, to confirm) |
Message A gives you a vague inquiry. You have to invest effort in follow-up questions before you can start evaluating. Message B gives you three core parameters. You can complete a first-round match in under thirty seconds.
This is why presales time should go to Message B first. Not because the person who wrote Message A is “less serious.” The message with more complete information costs less to evaluate, and reaches a quotable stage faster.
More data, but each point needs a sanity check
More information does not mean you skip validation.
The three numbers in Message B — 12 cabinets at 8 kW, Hong Kong, 45-day timeline — need at least three checks before you start building a quote.
First, who is this person?
Have they spoken in the group before? Is their Telegram account new or established? Have they posted the same message in other groups? None of these are about judging whether they are “a fraud.” They help you understand context: the person could be an internal project manager at the client, a competitor price-checking on the side, or an agent asking on behalf of a customer whose channel policy differs from yours.
Second, does the 45-day timeline have a contract behind it?
Is forty-five days a soft target or a hard deadline driven by a signed contract? The latter means the window is rigid; the former may leave room. You can ask directly: “Is forty-five days a customer requirement or an internal goal?” The answer tells you how urgent the follow-up needs to be.
Third, are the power and quantity estimated or confirmed?
Is 8 kW the design load per cabinet, or the expected draw after the servers are fully populated? The two numbers can differ meaningfully. Some clients say “8 kW” based on nameplate ratings when actual满载 (full-load) draw is closer to 6 kW. If you design power distribution and cooling for 8 kW and the equipment only uses 6 kW, the client’s overpaid electricity bill becomes a future dispute point.
You do not need to resolve all three before the first round of quoting. But keep each as an open question in your head. When you reply, you do not fire every question at once. Confirm the most important one: “Is 8 kW the design target or the expected draw?” That question sounds professional without making the person feel interrogated.
You now have a decision rule
Back to the two messages from the start.
Message A is not unanswerable. But before you reply, you need to invest in follow-up questions to figure out what the person actually needs. Message B carries enough information density that you can decide “can I handle this requirement” in a short time, then focus your energy on the solution and the price.
The decision rule is not about how friendly or talkative the person sounds. It is whether three parameters — power, location, timeline — have been mentioned. All three present, and the shift from “check stock” to “build a proposal” is ready. Missing any one, and the inquiry stays in the vague zone. Your reply should lead with clarifying questions, not a quote.
The next morning, you open Telegram. A new “got racks?” lands in the group. One line, nothing else.
You do not close it. But you know: before you reply, wait for the next message from that person. Quantity, location, timeline. Three sentences, that is all.
How a Signal worth attention is found
See how Top Prospect finds and organizes Signals worth checking, keeps the original Telegram context, removes duplicates, and helps you decide what to review first. You decide whether to follow up and what to do next.
