"They Said It Was Just Adding a Language" — Then Three Messages Changed Everything
A SaaS sales rep sees three consecutive questions in a Telegram group — company name input, tax number format, and support time zone. Each alone seems minor. Together, they trace a full onboarding blockage map. The question: when do you call this an opportunity, and when do you stop and verify first?
Your customer just asked three questions in the group — at least you think he is your customer.
You are watching a Telegram group where GCC (Gulf Cooperation Council — Saudi Arabia, UAE, and four other Arab states) enterprise service buyers and vendors discuss tools, compliance, and operational pain points. Around four in the afternoon, a message from @al_najjar appears.
Illustrative group conversation | The exchange below is a composite drawn from multiple similar scenarios, not a single captured message.
@al_najjar：We tried your SaaS platform. When we enter Arabic characters in the company name field, they show as question marks. Does this not support Arabic, or did we misconfigure something? — 16:23
Your first instinct: a translation pack issue. You are about to type “scheduled for the next release.” Then the second message arrives.
@al_najjar：Another thing. Our finance team tried to generate an invoice, but the tax number field only accepts digits. Saudi Arabia’s tax ID is 15 characters — it includes letters. Finance spent two days on this and could not get through. — 16:34
Then a third.
@al_najjar：Does post-sales support cover our time zone? Our operations team is based in Riyadh. We are five hours ahead of your support window. If something breaks after launch, we would wait overnight for a reply. We cannot absorb that in the first month. — 16:42
Nineteen minutes. Three messages. You stop and read the screen again.
The first message is not about translation. It is about the field rejecting input.
The sentence ends with “show as question marks” — this is not a missing language pack. It is a character validation rule (the mechanism that checks whether input meets the field’s criteria) blocking Arabic script from being written into the database.
Fixing this field typically involves the database character encoding, column type definitions, and export formatting. In other words, it touches the infrastructure layer, not the interface language bundle. That is a different order of work from “adding an Arabic menu translation.”
The person speaking has already hit a real blocker: he cannot create a customer record because the legal company name of his client is in Arabic. If his client list includes any locally registered business, this system is unusable in his context.
But at this point, it is still a single-point problem.
The second message turns “can we enter data” into “can we stay compliant”
Eleven minutes later, the topic jumps to the tax number.
Since 2020, Saudi Arabia has mandated e-invoicing standards. The tax identification number format is 15 characters combining digits and letters. UAE’s VAT registration number follows a similar alphanumeric structure. If the system’s tax number field only accepts pure digits, any company registered for GCC compliance cannot use it to issue invoices.
There is another signal in this message: “Finance spent two days on this” — at least a second role has been involved, and the blocker has been formally escalated within the organization.
For someone selling into the Middle East market, the phrase “Finance spent two days” may carry more weight than the tax format detail itself. It tells you the information is already circulating internally.
But two questions together could still be a coincidence.
The third message adds the post-launch perspective
The third message points to support coverage — time zone and language support.
The first two landed on basic data entry and financial compliance. The third lands on live operations support. Three questions covering the front, middle, and back stages of an onboarding process.
Someone who only wanted to ask about Arabic translation would not think about post-sales time zones. A team running a pre-launch assessment would go through checkpoints like this one by one. The phrase “the first month after launch” is particularly telling — it suggests a concrete go-live timeline, and the person is already estimating operational pressure.
When form input (company name), invoicing (tax number format), and support (time zone and language coverage) appear in the same person’s same session, these three questions do not describe three independent bugs. They trace a staged resistance map of the entire onboarding pipeline.
Before you take this to the product meeting, one question must be answered
At this point the impulse is natural: screenshot the messages, drop them in the internal channel, declare that a Middle East customer is about to onboard, and request Arabic support on the roadmap.
Stop.
None of these three messages mentions a product name. We do not know whether the “platform” @al_najjar refers to is yours. He could be testing three different systems simultaneously and consolidating his findings into one message. In that case, these three messages are not a delivery opportunity — they are a vendor comparison note.
What we still do not know includes:
- Whether his company has already signed a contract. If yes, at what stage is it stuck? If not, is this a procurement evaluation or market research?
- Whether the three issues came from his own testing or from a task list assigned by his team.
- Whether the problems he encountered are already being addressed — or already resolved — by the current vendor.
There is at least one other explanation: this person could be running a competitive technical evaluation, merging blockers he found across different products into a single post. Three questions across three stages would actually suggest he is doing a systematic comparison.
Also, the fact that no one replied to @al_najjar carries no signal about demand intensity. Reply density in a group is influenced by topic, time of day, and member relationships. Silence alone does not translate to commercial value.
Look back at those 19 minutes. Start with this one step.
A single message about “cannot enter the company name” grew into a blockage list covering data entry, finance, and operations — all within 19 minutes. The change itself is worth noting, not because there were many questions, but because the three sentences happened to land on different segments of the onboarding flow. The person speaking was likely working through an internal checklist.
But the next stop after noticing this pattern is not the product meeting. It is confirming whose product is being discussed.
Scroll back through @al_najjar’s history in this group. Check whether he has mentioned a specific product name before. If yes, decide whether to schedule a technical compatibility review with the product team. If not, mark it as an unverified lead and keep watching. Either result is valid.
You do not need to decide within those 19 minutes whether this is an opportunity. You only need to decide whether it is worth the next 15 minutes to find out.
Market and risk discussion is supporting evidence
Top Prospect is primarily a Telegram lead-generation product. Market and risk discussion can add context to a candidate lead, but it does not become a verified incident, trend, or sales opportunity automatically.
