Account and job support
Job status, exports, result questions, balance checks, and account access all resolve inside the dashboard, next to the file or job they concern.
Log inEmail, WhatsApp, and Telegram all reach the same team. Email keeps a record you can point back to; chat is for short questions. Tell us which product or job the request is about and it reaches the person who owns it.
Replies go back to the inbox the message came from, in English, on business days.
Write to supportThree routes answer a whole class of question on their own, with the record already open in front of you. Reaching for them first is usually faster than waiting for a reply.
Job status, exports, result questions, balance checks, and account access all resolve inside the dashboard, next to the file or job they concern.
Log inThe endpoint reference covers request shape, status codes, and error codes. If a call still fails, it tells you which four details to attach when you write.
View API referencePer-check and per-batch rates, minimum order sizes, and what a credit buys are all listed before you pay. Credit top-ups are also started from there.
View pricingThere is one mailbox, but the request type decides who picks it up and which record they open first. Sending it to the right place is the difference between one exchange and three.
Anything about a job you already ran: a file that did not finish, an export you cannot find, or a result you want explained. The support team opens your job history before replying.
Integration failures, unexpected status codes, or questions about an async task. Include the endpoint and the request ID so the exact call can be pulled from the logs.
Missing credits, an invoice question, or a payment you want traced. Billing replies depend on the payment being confirmed first, so include the reference and the date you paid.
Lookup-deletion requests, questions about what a job stored, and vulnerability reports. Data-handling detail sits on the Security & Data Handling page; the rules on how lookups may be used sit in the Terms of Service.
Support email is not routed through a sales funnel or a ticket robot. A person reads it, and replies come from the same address the message was sent to.
Before answering, the account, the job, or the payment being asked about is opened in the dashboard. That is why including identifiers shortens the exchange rather than slowing it down.
You get either the explanation and what changed, or a request for the one detail still missing. Nothing about your numbers is sent anywhere by asking a question.
This page covers reaching a person, by email or chat. The rest of the company information lives on three pages, and each of them owns one topic.
Open ZelNum in your preferred AI assistant to review its bulk WhatsApp, Telegram, phone validation, carrier lookup, social account, crypto exchange, CSV upload, and API workflows.
The prompt points assistants to ZelNum.com, live pricing, product pages, and API documentation.