1. What Does "Response Time" Actually Mean?

There are four different SLA stages that should be separated.

Many suppliers only guarantee:

"We will acknowledge the ticket within 4 hours."

That does not mean your AGV is running again within 4 hours.

Recommended Contract Language

Instead of:

❌ Response Time: 4 Hours

Use:

✅ Critical Incident Acknowledgement: 30 minutes

✅ Qualified Engineer Engagement: 4 hours

✅ Root Cause Analysis: 24 hours

✅ Corrective Action Plan: 48 hours

2. How Should AGV Support Tickets Be Classified?

A mature SLA should define severity levels.

Severity 1 (System Down)

Examples:

• Entire AGV fleet stopped

• RCS unavailable

• Production halted

Recommended SLA:

Severity 2 (Major Degradation)

Examples:

• 20%+ fleet unavailable

• Routing failure

• Charging system issue

Recommended:

• 4-hour engineer response

• 24-hour recovery plan

Severity 3 (Minor Issue)

Examples:

• UI bug

• Report generation issue

• Non-critical warning

Recommended:

• Next business day

3. What Penalties Should Apply If SLA Is Missed?

Many Chinese suppliers resist direct penalties.

A practical compromise is service credits.

Example:

Better Than Cash Penalties

Many buyers negotiate:

• free support extension

• free onsite visit

• free software upgrade

• free spare parts package

These are often easier to obtain than cash penalties.

4. Is Support Based in China or the US?

This is one of the most important questions to ask.

There are generally three models.

Model A — China Only

Pros:

• Lowest cost

Cons:

• Time zone gap

• Delayed escalation

• Language barriers

Typical coverage:

China business hours only.

Model B — China + On-Call Rotation

Pros:

• Better coverage

Cons:

• Night support may still be limited

Common among mid-sized AGV vendors.

Model C — Local Support Presence

May include:

• US engineer

• US integrator

• US distributor

Pros:

• Faster onsite response

• Better communication

Usually preferred for fleets above 10–20 AGVs.

5. Should You Request a Dedicated Support Engineer?

For the first 90 days after SAT:

Absolutely.

This is often called:

• Hypercare Period

• Stabilization Phase

• Go-Live Support

Typical Hypercare Coverage

Weeks 1–4:

• daily monitoring

• priority ticket handling

Weeks 5–8:

• weekly review meetings

Weeks 9–12:

• transition to normal support

Recommended Requirement

For the first 3 months after SAT:

✔ Named support engineer

✔ Backup engineer

✔ Weekly review call

✔ Priority escalation path

✔ Direct phone / messaging access

6. Questions Experienced Buyers Put in the Contract

Instead of asking:

"Do you provide support?"

Ask:

Staffing

• How many English-speaking support engineers are available?

• Is support 24/7 or business hours only?

• Where are they physically located?

Escalation

• Who is the escalation manager?

• What is the escalation chain?

Availability

• What holidays affect support coverage?

• Is weekend support included?

Access

• Remote support tools used?

• VPN requirements?

• Read-only or full access?

7. Contract Clause Example

A strong AGV contract might specify:

Supplier shall provide 24/7 remote support for Severity 1 incidents. A qualified English-speaking engineer shall engage within four (4) hours of ticket creation. Failure to meet SLA three times within a rolling twelve-month period shall entitle Buyer to service credits equal to 10% of the annual support fee.

Procurement Recommendation

For a US warehouse importing China AGVs, the minimum support package I would negotiate is:

✅ 30-minute critical ticket acknowledgement

✅ 4-hour engineer engagement

✅ 24/7 Severity-1 coverage

✅ Named support engineer during first 90 days after SAT

✅ Monthly SLA reporting

✅ Escalation manager identified by name

✅ Service-credit mechanism for repeated SLA failures

The biggest mistake buyers make is assuming that "4-hour response" means "4-hour repair." In contracts, those are completely different obligations and should be written separately.