Support guide

Troubleshoot print, scan and toner issues before dispatch

Use this field-service guide to capture model, serial, fault, user, network, toner and site evidence before booking support.

Request a Quote Talk to sales

Engineer-Led Support Device context before dispatch.
Rapid Response Quick. Local. Reliable.
Ricoh-Focused Support Model, toner and service context aligned.
Coverage Planning Location and response path confirmed first.

Use this for

Make the support request actionable before dispatch.

01
Capture evidence
Record the exact error, output defect, affected users, model, serial and recent changes before escalation.
02
Separate the lane
Identify whether the issue is paper path, toner, network workflow, installation, relocation or preventive service.
03
Route to support
Send the right urgency and evidence to the configured support desk so the next response is not guesswork.

Support guide

Troubleshoot print, scan and toner issues before dispatch should turn browsing into action.

The guide turns symptoms into a service-ready support packet.

Request Service

Resource workflow

01Capture the symptomRecord error, output defect, affected users, model, serial and recent changes.
02Attach evidencePhotos, video or PDF context stay private in the request record.
03Route to supportSupport receives a stronger dispatch packet before asking for more detail.

Troubleshooting guide

Capture the right fault evidence before a service visit is booked.

Most print support delays start with missing context. This guide helps teams separate user, network, toner, paper-path and machine faults before sending a request to Geodetic support.

Recurring fault

Paper jam or repeated misfeed

Separate a one-time jam from a tray, media, roller or paper-path issue before the technician arrives.

Record the jam code and where the paper stops.
Confirm tray, paper size, paper weight and whether the paper is curled or damp.
Do not force stuck paper or remove fragments that support may need to inspect.

Start this service lane

Recurring fault

Toner, colour or print-quality fault

Capture the exact colour, cartridge label, output sample and when the defect started.

Keep a sample page showing streaks, fading, ghosting, background or colour shift.
Record toner colour, SKU label and whether the cartridge was recently replaced.
Note whether copy output and print output fail in the same way.

Start this service lane

Business down

Scan, print or network workflow issue

Identify whether the problem sits with the device, the workstation, credentials, address book or network path.

Confirm if other users can print or scan from the same device.
Record the destination type: email, shared folder, USB, mobile print or print queue.
Capture recent password, domain, Wi-Fi, IP address, driver or server changes.

Start this service lane

Scheduled maintenance

Installation, relocation or preventive service

Give support the site conditions needed to plan the right visit and avoid a wasted dispatch.

Confirm office address, floor access, power, network point and device location.
State whether users need driver setup, scan destinations, secure print or meter reading.
List current faults that should be handled during the same visit.

Start this service lane

Escalation matrix

Route the issue by symptom, not guesswork.

Symptom	Capture first	Route
Device panel shows a hard stop or error code	Panel message, model, serial, photos and when it started	Book service
Wrong toner, low toner or colour mismatch	Device model, serial, colour, SKU label and delivery address	Order toner
Users cannot print or scan after a network change	Affected users, device IP or queue name, destination type and recent change	Open support ticket
Recurring jams, noise, marks or slow performance	Fault frequency, output samples, paper type and maintenance history if available	Preventive service

When to escalate

Do not turn a support request into a vague complaint.

If the device stops business output for a team, route it as business down.
If the same fault has happened more than once, include frequency and last service context.
If toner or parts may be involved, send label photos before procurement buys replacements.
If the issue follows a user or laptop, capture workstation and driver context before dispatch.

Reach the right desk