Lead Gen & GTM
Email checks have been standard on lead lists for years. Phone numbers went unchecked. ScoreMachine checks both in one pass: which numbers are in use, which channels they accept, and which addresses will deliver.
Enter a number and run a live check.
Results by phone number
Results by e-mail
eHLR status, carrier and the four channel booleans run on an account. Formatting, line type and country stay open.
123456789101112131415161718192021222324
For demonstration purposes and business use only. Terms · Data & opt-out
Prospecting tools build lists around technographics and intent signals, and the lists still come back full of dead numbers.
Enrichment vendors return numbers they can't vouch for.
Dialers burn time on landlines, disconnected lines, and wrong carriers, and you pay for every call that should have been a conversation.
Check the list before it goes into a sequence, so reps only dial numbers that can ring.
You own the CRM, and its phone and email fields decay even when nobody touches them.
A contact changes jobs and their work inbox and direct line get shut off.
Numbers are disconnected, ported to new carriers, or switched from mobile to VoIP. Domains lapse and mailboxes start bouncing.
Re-check records on a schedule and flag the dead ones before they go into a sequence.
You buy or capture leads by the thousand, and pay for every one that never picks up or never opens.
Form fills come in with typos, fake numbers, and throwaway inboxes.
Purchased lists arrive with numbers that were disconnected months ago.
Check phones and emails as they come in, so bad leads never get routed to sales, counted in pipeline, or used to judge a campaign.
A list is accurate the day it is built. Numbers get disconnected, reassigned and ported. Mailboxes close when people change jobs. The CRM row stays exactly as it was.
Most teams find a bad record only when it fails: a dial that never connects, an email that bounces, a lead that gets routed to sales and goes nowhere. By then the data vendor, the dialer seat, the email send and the rep's time are already paid for.
Bad contacts damage your sending channels. High bounce rates push email toward spam, and carriers throttle or block SMS senders with too many failed deliveries. Checking before the send keeps every channel open for the next campaign.
score.phone.scoring returns the phone side. score.email.validation returns the email side. Same account, same token.
accessibility returns valid, invalid or unknown. Formatting says a number could exist. accessibility says whether it does.
line_type and carrier, the serving network after porting.
whatsapp, telegram, facebook, instagram as booleans about the number. OTT channels only; none of the four predicts SMS termination.
The reachability score, phone_accessibility, 0–10. Sort the file on it and work the top first. -100 means undetermined, not zero.
The email side returns the deliverability verdict, the SMTP status code behind it, the provider and the mailbox type.
Full reference at doc.scoremachine.ai.
Product tour
Five steps from an empty workspace to a scored, exportable list. Plays on its own. Click any step to jump.
Seven steps from a QR code to a validated number, without leaving Telegram. Plays on its own. Click any step to jump.
Audiences are added inside the project after creation.
Reseller list, cleaned before handover · created just now
Audiences
0
Contacts
0
Scored
—
No audiences yet
An audience holds the contacts you want validated and scored.
Drop your file here
or click to browse · max 5 MB · up to 200,000 rows
3 of 4 columns auto-detected from the header row. Override any of them before continuing.
Estimated run
$212.71
24,310 contacts · eHLR + MNP
Scoring in progress · eHLR + MNP
0%
0 / 24,310 contacts scored
eu-leads-sep · run took 18s
Per-contact verdicts are on the audience screen and in the export.
Share Your Phone Number?
The bot will know your phone number. This can be useful for integration with other services.
⚠ Warning! Never enter your Telegram login codes in mini apps.
Scan the QR
The bot is the fastest way in. Nothing to install, and the same account works in the workspace and the API afterwards.
Created your account in Telegram? Use Forgot password with the email you gave the bot.
The live bot prints the time zone as a UTC offset. The prototype uses the IANA name so the value matches the timezone field shown elsewhere on the site.
Contacts you submit should be ones you are entitled to contact. See Terms and Data & opt-out.
Start with a file in the workspace, or walk through your stack with our team.
Check lead phone numbers one at a time with sequential methods as they come in, or run a whole list through the batch methods before it goes into a sequence.
CSV or XLSX, up to 5 MB and 200,000 rows. Columns are detected on upload.
Start free →JSON-RPC 2.0, up to 20 requests a second, up to 10,000 records in one request. Email validation takes 2,000 addresses at least.
Developers →Telegram and WhatsApp bots, Zapier, Make, n8n, and CRM connectors.
CRM integrations →"Our SDRs used to work leads by cold call and LinkedIn. Now every list shows which numbers are on WhatsApp Business, so we can message a business on the channel it already uses with its customers."
Raunak Datt
CEO and founder, Superable
Phone number validation confirms the format, the numbering range, and whether the number is in use. ScoreMachine also returns the line type and the serving network after porting. The four OTT channel booleans and a reachability score come back on the same request.
An HLR lookup queries a mobile operator’s subscriber register over SS7. The query returns whether the subscriber is provisioned and where the subscriber is being served. eHLR is ScoreMachine’s own check, combining telecom network signals with digital footprint data. eHLR returns a verdict on ranges and in markets where a register query returns nothing. The response is valid, invalid or unknown.
phone_accessibility ranks how reachable a number is, on a 0–10 scale. Carrier, network and channel signals feed the score. Sort a file on the score to work the reachable part first. Fraud and risk scoring is a separate category, built on different data.
Yes. CSV or XLSX upload takes up to 5 MB and 200,000 rows. The API takes up to 10,000 numbers per request.
Most CRM validation checks format and the numbering plan. It confirms the number could exist and returns the carrier the range was allocated to. It does not say whether the number is in use, which channels it carries, or where it ranks against the rest of the list.
Yes. Both run on one account, with one token and the same request envelope. Integrate one and the other is already integrated.
No. The API validates one phone number at a time on a signup form, and the batch path takes up to 200,000 rows when you want the whole file done at once.