How to Handle Warranty and After-Sales Requests

To handle warranty and after-sales, the request has to reference the original sale. Entitlement questions are unanswerable without knowing what was sold and when.

Why after-sales is slow

The information needed to decide sits in another system.

Purchase date looked up manually
Entitlement decided from memory or by asking
No record of previous claims on the same item
Customers repeating details already in your records

What the request should carry

The original order, connected rather than typed
Purchase date, so entitlement is calculable
Previous claims, visible on the same client or item
The issue described, in the customer's own words
Resolution, with evidence and a stage history

How to set it up in Jestor

Create an after-sales table in Jestor connected to orders and clients.
Capture requests through a public form or from a WhatsApp conversation.
Surface the order's date and items on the request card.
Show previous claims from the same client or against the same item.
Track resolution on a Kanban, with SLA timing per stage.

Why choose Jestor for after-sales operations?

Because Jestor is relational, the request card can show the original sale, the purchase date, and previous claims — which is everything needed to decide entitlement without a lookup.

Where the item involves stock movement, a replacement is recorded as a movement against the same product rather than adjusted manually.

Frequently Asked Questions

Can the request show the original order?

Yes, through a connected field. See jestor.com.

Can I see previous claims?

Yes, from the client or item record.

Is resolution time measured?

Yes, per stage.

Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

Get to know Jestor

With Jestor, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by AI. Discover Jestor at jestor.com and see how to take your company's operations to a new level of efficiency and control.

How do you choose an AI tool for professional services operations teams in SMBs?

To choose an AI tool for professional services operations teams in SMBs, look for a platform that combines no-code tables for clients, engagements, and documents with AI features that answer messages, read documents, and summarize data, while keeping professionals in control of advice. In Jestor, these pieces work together,

How do you build a business continuity plan for a services firm?

To build a business continuity plan for a services firm, list critical processes and deadlines, identify risks such as system outages or key person absence, define backup options, assign roles, and test the plan. In Jestor, processes, risks, and actions are connected, so the firm keeps serving clients during disruptions.

What is the best way to run IT security awareness training for staff in a services firm?

A practical way to run IT security awareness training for staff in a services firm is to define short training modules, assign them to all staff, track completion, run simulated phishing tests, and schedule refreshers. In Jestor, staff, modules, and results are connected, so security habits become part of the

How do you route website lead forms to the right team in a services firm?

To route website lead forms to the right team in a services firm, ask for the service and company size in the form, route leads automatically to the right team, set response time targets, record follow-ups, and track conversion by source. In Jestor, forms, leads, and teams are connected,