That "Network Is Slow" Telegram Message — Count the Empty Fields Before You Quote
A sales engineer spots a Telegram message with locations, an app name, and a latency number. It reads like an opportunity — until you open the quote template and see how many lines are still blank.
(All dialogue, timestamps, and numbers below are illustrative composite scenes used only to demonstrate a judgment method.)
You are scrolling through a Telegram group when a voice-to-text message catches your eye:
“Shanghai to Frankfurt, ERP latency 280ms in the afternoon, customer is asking if they can use SD-WAN. SD-WAN is software-defined wide area networking — it uses software to manage multiple links and route traffic based on application needs.”
You know the person who posted it — you worked together at a previous company. You read it twice. It feels complete: city pair, application name, latency number, technical direction. Your finger is already moving toward the input field.
Then you stop and ask yourself one question: if I open the quote template right now, how many lines can I actually fill in?
The answer: the message filled about two and a half fields. Six are empty. Two of those, if left blank, will stop your quote dead halfway through.
Location and latency — each half missing
“Shanghai to Frankfurt” sounds specific. But Shanghai might have three office addresses. Frankfurt could be the headquarters data center or a sales office.
Say Shanghai has three sites and Frankfurt has two. Which pair is “slow”? If only the R&D center to the HQ data center link is congested and every other combination runs fine, the troubleshooting direction would point one way — a link issue rather than a routing problem. Cross-border SD-WAN pricing stacks by node count and bandwidth. If you do not know which two nodes are affected, you cannot estimate how many sites to quote. One node you forget to include could mean the month you sign the deal, that cost comes out of your margin. As of this message, this field is empty.
280ms is RTT — Round-Trip Time, the time a data packet takes to go out and come back. The straight-line distance between Shanghai and Frankfurt is roughly 9,000 kilometers. The physical limit for an optical signal through fiber is about 90ms one way. A direct international private leased line — a dedicated point-to-point circuit — typically runs between 180 and 220ms RTT. Over the public internet with a VPN, 280ms is within expected range.
A single 280ms reading tells little on its own. What could matter is whether this number went up compared with last week. If it was 180ms last week and climbed to 280ms, one possible cause is rerouted traffic or congestion from full bandwidth. If it has been running at 280ms for six months, the real question would be why it came up today — a new business launch, a supplier change, or a fresh complaint from someone who finally escalated.
“Just got slow today” and “It has been this slow for a while and someone finally complained” would lead to different next steps. The message contains one data point. As of this message, this field is also empty.
Current link and operation context — guess wrong and you head the wrong way
“Customer is asking if they can use SD-WAN” — this statement assumes the customer already has a link running and finds it insufficient. But the message does not say whether they are on a public VPN or a private leased line today. The two cases would point in different directions.
If they are on the public internet with a VPN, the 280ms comes mostly from internet unpredictability, and switching to SD-WAN to aggregate multiple links could be one way to address it. If they are already on a private leased line and still seeing 280ms, one possible root cause is bandwidth saturation — investigate first, then propose. There is also the contract timeline: if they still have 18 months left, the SD-WAN question could be research. If the contract expires next month, the priority of this message would be different. As of this message, this field is empty.
“ERP latency 280ms in the afternoon” — ERP systems support a wide range of operations. Looking up a material code at 280ms: you can feel the lag but it is still usable. Transmitting dozens of production orders: every extra millisecond of latency multiplies the total transfer time — an operator might think the submission did not go through and click again, causing duplicates. Running a financial report sync: it may time out entirely and break the month-end close.
These three scenarios would point to different approaches. The first might be improved with TCP optimization alone. The second may need a dedicated link for that specific site. The third could require service guarantees across the whole route plus redundant circuits — one outage during the month-end window can cost more than the bandwidth itself. The message only says “ERP.” No operation type, no number of affected users, no stuck module. As of this message, this field remains empty.
Decision-maker and deadline — what decides how much time you invest
“Customer is asking if they can use SD-WAN” — this “customer” could be an IT manager who heard a complaint and is checking options. It could be an overseas branch head who got frustrated by a disconnection and asked someone to find answers. Or it could be a procurement officer collecting vendor names for a routine price comparison. These three people would each have different levels of urgency, budget authority, and follow-up rhythm.
If you build a solution without knowing who is pushing it, one possible outcome is that your proposal ends up filed as a reference document by someone who cannot sign. There is also a possibility that the person who posted the message is passing along secondhand information and has never spoken directly to that “customer” themselves. This chain of relay happens in Telegram groups. As of this message, this field is also empty.
A cross-border SD-WAN project — from initial contact through POC (Proof of Concept, a small-scale trial to see if the solution works), contract signing, and circuit activation — can take 4 to 8 weeks even when things go smoothly. The message contains no timeline. “As soon as possible” is not a timeline. “The customer is urgent” is not a timeline either. Only calendar-anchored dates — “needs to be live before next month’s audit” or “must be stable before Singles’ Day” — are signals that the procurement process could start moving. A “network is slow” message with no deadline may not get past the first review after you send the quote. One possible explanation is not that the solution is wrong, but that the organization has not put this item on a priority list. As of this message, this field is still empty.
Fill these two first
Six fields fully populated would be ideal. But two gaps make it difficult to build a quote.
The first is the specific sites — which two nodes are involved. Quote one node too few and your pricing misses a real cost; you can only guess when writing the proposal. The second is the specific operation that is slow — what exactly is the user doing when it lags or fails. Without it, the optimization section of your proposal may read like “improve cross-border access experience” — a sentence you yourself would not find specific enough to sign a contract on.
The next two fields — current link type and deadline — can help you decide whether this project belongs in your next two weeks of scheduling or can wait.
The remaining two — latency trend and decision-maker identity — you can fill in while chatting. They may not affect whether you reply.
Your next step is not to open the quote template. It is to run through one question in your head: in this message, how many of the six fields are actually filled? If the number is below four, get the two critical ones first.
This topic connects to an earlier discussion about how to pick which messages in a busy group are worth your time: How to Identify High-Intent Leads in Telegram Business Communities. That piece was about picking three out of three hundred. This one is about what to do when one of those three is in front of you — count the empty fields before you quote.
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.
