Quick answer: Anabon provides B2B support through installers, integrators, dealers and approved commercial accounts. Use Technical Support for technical issues and the Contact route for project, documentation or account-routing questions. Agree the available scope and next step for the actual request. Keep one case history, identify the exact devices and versions, and share only the information needed. Warranty and returns follow the applicable purchase terms, eligibility, assessment and written authorization.
On this page
Who is Anabon support for?
Anabon is a North American B2B security camera distributor supporting installers, integrators, dealers and approved business accounts. The approved channel wording is: “Anabon supports installers, integrators, dealers, and approved business accounts with CASE product distribution, technical support, warranty coordination, and project guidance.”
For a system supplied through an installer or reseller, that company normally leads the end-user service relationship while Anabon supports the eligible business account. Agree any distributor participation and authorized customer contact for the case. If an organization purchased directly as an approved commercial customer, confirm its claim route against the actual Anabon invoice and purchase terms rather than assuming a reseller supplied it.
Which support channel should you use?
Contact Anabon if you need help identifying the right route for a project, documentation or account request. Use the dedicated technical route for a fault, and continue an existing case through the agreed channel. Include the actual deadline and impact; sending duplicates to several inboxes does not establish a faster response commitment.
| Request | Where to send it | Include |
|---|---|---|
| Configuration, troubleshooting, firmware, compatibility | Technical Support | Full SKU, firmware version, NVR model and channel, symptom with timestamps, what you tried |
| Warranty or RMA for a unit in the field | Technical Support for a suspected defect, then the authorized RMA process; ask Customer Service about an eligible discretionary return | Full SKU, serial, order or project reference, fault description and the troubleshooting already done |
| Project review or design support | Contact Anabon | Drawing, site notes, draft camera schedule, owner requirements, deadline |
| Compliance documentation for a bid | Contact Anabon | Project name, buyer type, SKU list with quantities, the clause the specification names, the question deadline |
| Private pricing, quotes, orders, account details | Business account | Business account or order reference; exact SKU/revision, quantities and quote requirements. Never send passwords, access codes or session details. |
| Approved demo products | Contact Anabon or your business account | The proposed test package, site and full SKUs; confirm actual approval, exclusions, conditions and written return terms |
The Technical Support page currently advertises round-the-clock availability, including 24/7/365 wording. Confirm the actual channel, account eligibility and urgent-case arrangements with Anabon. Availability is different from a guaranteed response, repair, replacement or delivery time; agree the next update for the case rather than inferring a service-level commitment from the website heading.
What is in scope, and what is handled differently?
The table helps route a request and identify what needs agreement. Product assistance, remote access, engineering decisions, procurement acceptance and the applicable purchase or warranty terms are separate matters; confirm the actual scope instead of treating every topic as an automatic entitlement.
| Topic | How it is handled |
|---|---|
| Product selection and full-SKU questions | Request guidance using the complete SKU, lens and actual revision documents; resolve conflicting identifiers or specifications before committing. |
| NVR and camera configuration, adding cameras, PoE and network issues | In scope; see the checklist in Before You Call Support |
| CASE Connect setup | Request support for the actual supported device and version. Android is available; iOS is forthcoming. Confirm functions, permissions and remote access for the actual system; no unverified web URL or feature parity is promised. |
| Third-party VMS or recorders | Confirm ONVIF conformance for the exact model and firmware in the official database where required. Test discovery, streaming, events and recording with the actual platform/version; a profile label alone does not establish every function. |
| Warranty and RMA | Eligibility depends on the applicable purchase terms, original commercial purchaser, matching invoice/serial, assessment and account status. Obtain written RMA authorization before shipping. |
| Project review and compliance documentation | Agree the available product-selection, sizing and documentation scope and timing; obtain clause-specific evidence and record gaps for the actual project. |
| Future features or release dates | Not answered as promises; support states only what is supported today |
| Legal questions (privacy, audio recording, signage) | Not legal advice; verify with counsel and the local code, in the US and Canada |
| Service to the end user | Your company leads the service relationship; agree any distributor participation and authorized customer contact for the case. |
What warranty support looks like
Use the warranty and RMA guide to prepare the claim and distinguish defects, discretionary returns, approved CASE test packages and Advanced Replacement. Check the actual purchase agreement, exact item and revision, invoice, exclusions and account status. The October 2026 policy states its acceptance and document-priority conditions; it does not automatically replace earlier purchase terms. A category label or an RMA number is not approval of coverage, refund or shipping costs.
What should you have ready before you open a request?
Find the matching ip camera user manual and actual model/revision documents before recording your checks. Gather the details below so the case begins with reproducible observations. Share serials, account/order references and necessary logs only through the agreed route, with passwords, session details, unrelated personal data and unnecessary footage removed.
- Record the complete SKU, series letter, suffix, lens and hardware revision for each device, for example CS-I8XQ II-2.8mm or CS-N220 P16H-AI. These are identifier examples, not a statement that a particular pair or firmware file is compatible. Match the actual device and approved revision documents before applying settings or updates.
- Firmware versions of the camera and the recorder, copied in full.
- Where the device connects: NVR PoE port number, or the switch and port, for example port 12 on a CS-POE33024PF.
- A five-line topology: internet, router, switch or NVR, camera, cable lengths.
- The exact symptom, when it started, how often it happens, and what changed recently.
- Provide relevant label/cabling photos and supported diagnostic exports through the authorized route. Redact credentials, access codes, public-facing network details that are not needed, unrelated personal data and unnecessary identifiable footage.
- What you already tried, in order, with the result of each step.
- Your business account, project or order reference and serial numbers.
End users: what is the redirect?
For an end user who obtained the system through an installer or reseller, use the approved handoff wording below. Help identify the supplying company if the property changed hands; do not assume that a new owner acquired the original Anabon commercial purchaser’s contractual warranty. A direct approved business purchaser should confirm its own route under the applicable agreement.
For warranty and service, please contact the installer or company that supplied your system. Anabon supports warranty and technical service through our installer, dealer, and business-account network.
Make the service contact easy to find at handover, with the actual provider, agreed service scope and authorized contacts recorded. Use the handover checklist to organize access, recording checks, documentation and maintenance responsibilities. Keep the customer’s credentials and any private account information out of public labels and shared documents.
- Put your company name, phone and service email on a label inside the rack or on the NVR, and on the handover sheet.
- Record your company as the support contact in the customer’s documentation and O&M binder.
- Give the customer one written route for service requests, so a failure in year five comes back to you, not to a search engine.
- Keep the as-built, serials and order references in your job folder; the warranty request starts there.
How do you escalate a request that is not moving?
Escalation is a request for more attention on the same case, not a new case in a different inbox. Opening duplicates splits the history and slows everyone down.
| Situation | What to write when you escalate |
|---|---|
| Site has no recording, or evidence is at risk of being overwritten | State the observed recording outage and timestamps, the known retention/evidence risk and what has been preserved through an authorized process. Ask for escalation. |
| Same fault returns after a replacement | Both serials, both case references, the symptom and what was ruled out |
| Several units show the same symptom | Every SKU, serial and firmware version; whether they share a switch, recorder or batch |
| Bid deadline depends on a document or an answer | Project name, the question or submittal deadline, the SKUs and clauses involved |
| Answer received but it does not solve the problem | What you did with the answer, the result, and new evidence |
- Reply on the existing case and quote its reference.
- State the business impact and your deadline in one sentence.
- Add the new evidence since the last reply, not the whole story again.
- Ask explicitly for the request to be escalated; if no case exists yet, open one through Technical Support first.
- Tell your customer what you have done and when you will update them; the customer conversation stays yours.
How to use this with your customers
Explain who provides the customer’s agreed service and who submits a claim under the actual purchase terms. Give the warranty for the exact item/order with its exclusions and process, rather than one category number. Agree distributor participation, account eligibility and the next customer update; do not promise an automatic replacement, direct end-user warranty or response deadline.
FAQ
Does Anabon provide technical support to end users?
Anabon’s normal service model is B2B. An end user whose system came from an installer or reseller should contact that supplying company using the approved handoff wording above. If the purchaser is itself an approved commercial business that bought directly from Anabon, confirm eligibility and the claim route against the actual invoice and purchase terms. Do not infer a transferred warranty for a subsequent owner.
What are Anabon’s support hours and response times?
The current Technical Support page advertises 24/7/365 availability. Ask Anabon for the actual channel, eligibility and urgent-case arrangements, then agree the next update. This wording does not establish a guaranteed first response, repair or delivery time, and it does not remove the applicable account and warranty conditions.
Which channel should I use for a warranty claim?
Use the RMA policy and request page after the appropriate troubleshooting or return discussion. Supply the actual company/contact details, Anabon invoice, full model, serial, quantity and clear reason through the agreed process. Obtain written authorization and shipping instructions before dispatch. Acceptance, account status and document priority matter; a customer resale invoice is not a substitute for the original Anabon invoice under the current policy.
Does support cover third-party VMS platforms and recorders?
Confirm ONVIF conformance for the exact model and firmware in the official database where required. Test discovery, streaming, events and recording with the actual platform/version; a profile label alone does not establish every function. Send the camera/recorder SKU, firmware, platform version and observed symptom with your request.
What should I do when a case is not moving?
Use the before-you-call support checklist to organize the new information, then reply on the same case with its reference, observed impact, deadline and results since the last reply. Ask for escalation and an agreed next update without creating duplicate cases. Keep the customer informed through the agreed service relationship; an escalation request is not a guaranteed resolution date.
References
- Anabon Technical Support
- Anabon product manuals and downloads
- ONVIF Conformant Products database
