By KYN AI Advisory Team — AI implementation specialists, Singapore
A custom sales system for a Hong Kong business closes one gap: the time between an enquiry arriving on WhatsApp, email or a web form and a useful reply leaving. It captures each enquiry in one inbox, sorts it, drafts a reply from the client's CRM history and logs the result, while your team approves what is sent. It works with the CRM you already have, such as Salesforce or HubSpot. Measure your own reply gap first, using the audit below, before you hire or buy anything.
How do you measure your first-reply time?
Run this audit. It takes about five minutes and costs nothing.
- Pick your last ten enquiries from WhatsApp, ten from email and ten from your website form.
- For each, note the time it arrived and the time of the first useful human reply.
- Separate acknowledgements from replies that answered the question. Only the second counts.
- Mark the slowest channel, and which channels nobody clearly owns after 6 pm or at weekends.
- Calculate the median per channel.
If your slowest channel is hours or days behind your fastest, you have a process gap, not a lead shortage. When a buyer contacts several suppliers, the first useful reply often shapes the shortlist. An answer on Thursday to a Tuesday message is often an answer to a lead someone else has already qualified.
Why do enquiries leak when volume is healthy?
A brokerage or service firm with steady demand rarely has a marketing problem. It has a small team that cannot follow up fast enough across three channels. The common leaks:
- messages arrive in a personal WhatsApp and not the shared system;
- nobody owns after-hours enquiries;
- replies are typed from scratch, with no view of the client's history;
- follow-ups depend on someone remembering;
- the CRM is updated late or not at all.
The instinct is to hire. A new salesperson needs time to learn the product and the pipeline first. A process change can start working sooner. Treat response time as a systems question first and a staffing question second, then hire into a pipeline that already captures and qualifies leads.
What does a sales system do?
| Component | Job | Who approves | |---|---|---| | Capture inbox | Brings email, WhatsApp and form enquiries into one queue | Nobody, read-only | | Qualification | Labels each enquiry: new quote, existing client, wrong person, complaint | Nobody for labels | | Reply drafting | Writes a reply from the enquiry and the CRM history | A named person sends | | Follow-up scheduler | Tracks each open conversation and raises the next touch | A named person sends | | Pipeline log | Writes every reply and step to the CRM with actor and time | Nobody, automatic | | Outreach writer | Drafts one checkable first line per target account | A named person sends |
The rule: the agent drafts, sorts and logs. Outbound messages, quotes and anything about money wait for a named person.
KYN's insurance brokerage system uses this pattern: outreach with one checkable first line at about S$0.02 per email, a reply desk that sorts each reply at about S$0.01, and a group benefits comparison to a client PDF at about S$0.03. These costs vary with the model and text length.
Can you automate without replacing your CRM?
Yes. The CRM stays the record. The system reads from it before it drafts and writes to it after each step. In the insurance brokerage build, every reply and outreach step is logged against the contact in the existing CRM, so the team keeps working where they already work.
If your CRM is HubSpot, the same pattern applies: enquiry in, history read, draft out, result logged. Check what your CRM plan allows through its API before you start, since some plan tiers limit access. HubSpot's API usage guidelines list the limits by plan.
What does a first-reply audit show in practice?
The numbers are illustrative, not from a client. A Hong Kong insurance brokerage audits 30 enquiries and records the median minutes to the first useful reply.
| Channel | Enquiries | Median to first useful reply | Slowest case | Owner after 6 pm | |---|---|---|---|---| | Web form | 10 | 5 hours | 2 days | None | | Email | 10 | 3 hours | 1 day | Shared inbox, nobody assigned | | WhatsApp | 10 | 40 minutes | 3 days | The founder's personal phone |
The audit shows two things. WhatsApp is the fastest channel and also the most fragile, because it depends on one person's phone. The web form is slow because replies wait for the next working morning. A system built on this evidence starts with a shared WhatsApp inbox and an after-hours acknowledgement that asks the qualifying questions, then queues a drafted reply for the first person in the next morning.
What does each component do in a working day?
- Capture inbox. All three channels arrive in one queue with the same fields: sender, source, time, text, attachments. Nothing lives only in a personal phone.
- Qualification. Each enquiry is labelled and given the missing questions to ask. A message in English, Traditional Chinese or mixed is handled in the language the client used.
- Reply drafting. The draft reads the whole thread and the CRM record. It states what it used, so the reviewer can check the source.
- Follow-up scheduler. An open conversation with no reply for a set number of days raises a draft for the next touch. The interval is a rule you set.
- Pipeline log. Stage changes are written to the CRM with the actor. A weekly count of enquiries by stage comes from this log.
- Owner view. A single list of open deals, ordered by age since the last touch, with the next action beside each.
How do you roll it out without disrupting the team?
- Week of the review. Inventory channels, CRM fields and who answers what. Interview two or three salespeople about how they actually reply.
- First workflow. Capture and qualification only. Replies are still typed by hand. The team sees every enquiry in one place.
- Second workflow. Drafting. The team sends drafts from the queue and records edits. Edits show where the drafting rules are weak.
- Third workflow. Follow-up and the owner view.
- Outbound, if wanted. Added last, with the suppression list, the send cap and the source log in place.
At each step, compare the median first-reply time to the audit baseline. If it has not moved, find out why before building the next piece.
What edge cases should the build cover?
- Mixed languages. A client may start in English and reply in Chinese. The record should keep both and the draft should follow the latest message.
- Voice notes and images. WhatsApp carries both. Decide whether the system transcribes or routes them to a person. Routing is the safer default.
- Duplicate contacts. One client with two numbers should not become two records. Match on more than the phone number.
- Shared numbers. A family or company may enquire from one phone. The draft should address the name in the message.
- Public holidays. Hong Kong holidays differ from Singapore's. The after-hours rule reads a calendar you control.
- Referrals. An introducer's message should be tagged, so the source of the deal is not lost.
Which numbers should you track after launch?
| Measure | Source | Why it matters | |---|---|---| | Median minutes to first useful reply, by channel | Capture log | The gap this build exists to close | | Enquiries with no reply after one working day | Capture log | Lost-enquiry count | | Share of drafts edited before sending | Review log | Quality of drafting rules | | Open deals with no touch in 7 days | CRM | Follow-up discipline | | Cost per message handled | Cloud and model bills | Running cost |
Compare each to the figure from the audit. Close rates depend on price, season and the product, so treat them as context, not as a measure of the system.
Should you hire a salesperson or build the system first?
| Question | New hire | Intake and reply system | |---|---|---| | Time to contribute | Learns product and pipeline first | Starts on the first workflow shipped | | Effect on follow-up | Adds capacity and admin | Removes reading, typing and logging | | Effect on speed | Depends on availability | Drafts within seconds of arrival | | Cost shape | Ongoing salary | One-off build fee, then a monthly retainer | | Judgement | Strong | None; stays with your people |
They are not exclusive. Fix the reply gap, then hire where judgement is needed: pricing, relationships and closing.
What do you need ready before the review starts?
Collect these items. They shorten the first 14 days.
- A list of every channel that enquiries arrive on, with the person who answers each.
- Export access, or screenshots, of your CRM stages and required fields.
- Your last ten quotes or proposals, with the reply that followed.
- The list of messages your team sends again and again, such as "documents needed" or "renewal reminder".
- Names of the people who approve quotes and prices.
The review turns these into a scope, a target state and a timeline in writing. No development starts before you have read and agreed it.
How long does it take, and what do you own?
- Review. The first 14 days are a review: an inventory of your tools and interviews with your team. You receive a scope and a timeline in writing.
- Build. A full build ships in under 90 days.
- Run. A monthly retainer of at least twelve months covers changes, monitoring and fixes.
- Price. A one-off build fee plus the retainer, quoted after the review. There is no price list.
- Ownership. Everything runs in a cloud account in your company's name. Rights in the custom code and configuration pass to you on full payment. You can revoke KYN's role and everything keeps running.
KYN delivers to Hong Kong clients remotely from Singapore. Contact is through WhatsApp.
What should you ask any vendor?
- Who owns the code and the cloud account?
- What does the retainer cover?
- Which number does the build move, and how will we measure it?
- How is my existing CRM treated?
- Which actions wait for a person?
- What do I get in writing before development starts?
What controls apply to messaging in Hong Kong?
Check the rules for the recipient's country. For Hong Kong, the Unsolicited Electronic Messages Ordinance is administered by OFCA, and personal data falls under the PCPD. Take advice on consent and opt-out before sending outbound at volume. Build the controls into the system: a suppression list checked before every send, an unsubscribe that stops contact on every channel in one run, and a daily send cap. See security.
Where KYN fits
KYN builds sales systems with the pattern above for SMEs in Singapore, Hong Kong, Indonesia and Malaysia. Agents hold their own restricted accounts. The database applies row-level security. Every action is logged with the actor. See sales systems, and for the Malaysian version of this pattern read AI lead generation in Malaysia.
Frequently asked questions
Can I automate WhatsApp and email without replacing my CRM?
Yes. The system reads from your CRM before drafting and writes back after each step. The CRM remains the single record.
Is it cheaper to hire a salesperson or build a lead response system?
They solve different problems. A hire adds judgement and capacity for conversations. A system removes reading, sorting and typing. Run the first-reply audit to see which gap you have before deciding.
How long does a custom sales system take?
The first 14 days are the review. A full build ships in under 90 days. The timeline is confirmed in writing after the review.
Checked 30 October 2026.
Curious whether Marketing agents fits your business? Talk to KYN on WhatsApp — no forms, just a conversation.
