OPERATOR & CLIENT GUIDE
From public event to real sales action
Trigger-Ledger watches Hong Kong business registers for events that change what an SME may need. It turns those events into client-specific opportunities, blocks unsafe or unusable routes, and learns from every real outcome.
What the system does
A government event is evidence for “why now,” not proof that the prospect will buy. The need remains a hypothesis until a real conversation confirms or refutes it. The system deliberately distinguishes an evidence-verified signal from a sales-ready opportunity.
| Gate | What it proves | What failure means |
|---|---|---|
| Evidence | The source file, hash, record, dates and mapping agree. | The record cannot enter the client system. |
| Entity | The event is resolved to a business or reviewable premises. | Human resolution may be needed. |
| Client fit | The target kind, territory and economics match this client. | It is not a lead for this client. |
| Contact | A usable field, mail, call, email or permissioned WhatsApp route exists. | It needs enrichment. |
| Suppression | The business is not an existing customer or excluded account. | It is suppressed automatically. |
| Policy | The exact playbook version and channel conditions are approved. | No touch may be recorded. |
Set up a client
Create the client profile
Open Clients → Add client. Choose what the client sells, the target business kinds and districts, average deal value, gross margin, selling cost, weekly capacity and allowed acquisition routes.
Use real economics
Enter gross contribution, not vanity revenue. The score subtracts the expected operational cost. If a field visit costs more than its probability-weighted margin, the result should be negative.
Add CRM suppressions
Add current customers, open opportunities, competitors and excluded addresses. The system recomputes matching opportunities immediately. This prevents embarrassing duplicate prospecting.
Review each route playbook
Open Policy & playbooks, choose Edit exact content, then record the reviewer and exact review note. Approval applies only to the displayed content hash; any later edit resets it to draft and blocks that route again.
When the offer, territory, capacity or economics change, choose Edit profile and requalify on the Clients page. The system recalculates the whole opportunity book and removes records that no longer fit.
Daily workflow
Start on Today
Work from Sales-ready, not total event volume. The queue ranks opportunities by expected gross contribution, then urgency. Click any row for its dossier.
Read why now and why fit
Check the trigger date, evidence locator, need hypothesis, target type, district, offer and remaining action window. Open the government dataset when a client or salesperson wants to audit the event.
Inspect all six gates
Green gates passed. Amber gates need an explicit action. The server—not only the page—blocks acceptance or touches that violate required gates.
Use the selected route
For physical SMEs, open Field routes and group visits by district. Print the route sheet, take the client’s approved sample or checklist, mention the truthful public event, and leave if the contact is unwelcome.
Record every result
Accept, assign, touch, reply, meeting, won, lost or reject from the opportunity drawer. Every held meeting asks whether the inferred need was confirmed, partly confirmed, refuted or still unknown. Rejections need a reason; wins should include attributed revenue. The append-only ledger retains the history.
Contact and channel rules
Field visit or direct mail
A premises address can be a real acquisition route even when no phone exists. The route still requires an approved client playbook and truthful sender identity.
Live call or email
Adding a phone or email does not clear it. Record its source, confidence, and the client’s documented DNC/legal-basis check before the route can be selected.
WhatsApp is post-permission. A phone contact needs both a recorded DNC/legal pass and explicit opt-in evidence. A number discovered on a register, website or social profile does not itself constitute opt-in.
Opt-outs
Record a blocked/DNC status immediately and add a suppression where appropriate. Never rotate numbers or change channels to evade an opt-out.
How scoring works
The client score is transparent:
P(entity) × P(client fit) × P(reach) × P(touch before expiry) × P(reply) × P(meeting) × P(close) × gross contribution − operational cost
Every opportunity shows the factors, the calibration sample size, and an approximate 90% range. At the beginning the probabilities are priors. Real touches, replies, held meetings and wins replace those priors through the ledger.
Source and system operation
Source health shows the latest stored snapshot, parsed record count, cadence, content hash context and legal-basis note. Sync evidence imports the latest verified JSON pipeline output into the transactional client database; it does not fetch the internet.
To fetch current sources and rebuild everything from the command line:
C:\Python311\python.exe -m engine.run_pipeline --with-history
Then press Sync evidence. The Python service binds privately to 127.0.0.1. The hosted installation is shared only through its HTTPS reverse proxy and password gate; never bind the Python service directly to a public interface.
A good first client pilot
- One client vertical and two trigger classes, not “all SMEs.”
- A weekly capacity the salesperson can actually work.
- One approved field route and one permission-capture route.
- Every rejection and outcome logged from day one.
- Success judged on held meetings, confirmed needs, gross contribution and one attributable sale—not dossier count.