01 Answer first
What information helps technical support diagnose a bottling line problem?
Start with machine identity, component or station, observed condition, alarms, operating mode, materials, recent changes, photos or video and actions already attempted. Accurate evidence lets the correct manufacturing resource review the issue without assuming the cause.
02 Where it fits
Position in the project journey
A connected project step whose timing and completion evidence are confirmed for the specific order.
03 Buyer inputs
What the buyer should prepare
- Machine and component identification
- Clear description of the observed condition
- Alarm, mode, material and recent-change information
- Photos, video and actions already attempted
04 Allot Tech and manufacturing-resource inputs
What should be clarified or provided
- Triage and routing to the relevant manufacturing resource
- Requested diagnostic checks and evidence
- Parts or service options within confirmed terms
- Action status and closure communication
Allot Tech coordinates requirement, quotation and project communication. Detailed engineering, manufacture, testing, documentation and confirmed service are performed by selected manufacturing resources according to the signed scope.
05 Technical scope
Questions and work to control
Start With Accurate Equipment Information
A support request should identify the machine, component, observed condition, operating context, alarm information, recent changes, and available images or records. This helps technical review begin with useful evidence.
Define Support for the Specific Project
Remote guidance, parts supply, site service, maintenance advice, and additional training may have different commercial and practical conditions. The applicable support scope should be confirmed in the project agreement.
- Named contact and escalation route
- Equipment and issue identification checklist
- Clear boundary for buyer, supplier, and third-party actions
Send a Support Request That Can Be Diagnosed
Identify the plant, equipment, serial or project reference, software and document revision, affected format, operating state, time, alarm or symptom, recent changes, product status, safety condition, photographs or video where appropriate, logs, checks already completed, and the requested urgency. Do not send passwords or unrestricted remote access in an ordinary message.
- Preserve evidence before repeatedly resetting the fault
- State whether production can continue safely
- Use the authorized company and project contact route
Define the Support Boundary Before Handover
The signed agreement should state warranty start, covered equipment and services, exclusions, normal contact route, response method, remote-support conditions, site-visit authorization, travel and local support, spare-parts ordering, software access, data handling, and responsibility for safe plant state. A response time is not the same as a guaranteed repair or production-restoration time.
- Keep buyer maintenance and operating duties visible
- Require backups and rollback before approved remote changes
- Close support actions through documented tests and updated records
Buyer questions answered
Practical answers before you request a quotation
Should after-sales support be defined before the purchase order?
Yes. Agree support channels, hours or response process, languages, remote-access conditions, escalation, site-service terms, parts ordering, warranty notifications and evidence needed for diagnosis before commitment.
Can remote support replace a site visit?
It can resolve some documented settings, operating or diagnostic issues, but it cannot replace qualified on-site inspection, measurements, repair or safety control when physical conditions or regulated work require them.
Are all breakdowns covered by the warranty?
No universal rule applies. Coverage follows the signed warranty, accepted operating and preservation conditions, exclusions, notification process and evidence. Separate warranty obligations from paid service, consumables, wear and buyer-caused conditions.
How should the warranty-start event be defined when site readiness or SAT may be delayed?
The signed agreement should name the trigger for each equipment or service package and state how buyer delay, supplier delay, storage, preservation, installation, commissioning and conditional acceptance affect it. Keep the trigger separate from shipment, payment and risk transfer unless the contract deliberately links them.
Does a stated support response time guarantee that production will be restored?
No automatic equivalence should be assumed. Define response acknowledgement, diagnostic access, escalation, part availability, remote and site-service boundaries, buyer authorizations and the conditions for any restoration commitment separately in the project support terms.
06 Responsibility
Assign the owner before the work is due
Land, building and civil work, permits, import and customs, local taxes, site utilities, unloading, lifting, local labor, travel support and commissioning materials are not automatically included. Confirm every responsibility before order.
07 Common risks
What commonly creates avoidable uncertainty
- A support request says only "machine not working"
- Safety-critical work is attempted without the correct procedure
- Commercial service conditions are assumed from generic website wording
08 Acceptance or completion
How to know the stage is complete
The issue record identifies equipment, condition, evidence, assigned action, applicable commercial boundary and closure status.
09 Required documents
Records that support the decision
- Equipment identification record
- Diagnostic evidence and alarm history
- Action and communication log
- Parts or service confirmation
10 Next project step
Turn this decision into a reviewable project brief
Share the product, container, target output, destination and available site information. Unknown inputs can remain open for the first review.
Explore this topic cluster
Turnkey scope is project-specific and is defined by the signed technical and commercial agreement.