AI customer support agent

Rellin by Agentiqal

Customers get a clear answer. The team has time for difficult cases.

The AI customer support agent checks information about orders, deliveries and requests, prepares replies and tracks resolution steps. When a colleague is needed, it passes on the conversation and relevant documents so the customer can continue without starting again.

A customer has a delivery question.

See how customer requests are handled.Watch videos Talk to our team

Video examples

36 seconds

A clear answer about the delivery

Read transcript

0:00The customer asks: “I received eight of ten parcels. Where are the other two?”
0:05Rellin checks both shipments: eight parcels delivered, two collected by the carrier, with no receipt confirmation.
0:13The customer confirms the delivery site: the West branch. Rellin brings the order, documents and missing quantity together in one case.
0:22Rellin prepares an investigation request for the transport team and a customer update.
0:28The customer sees the next step. The case stays open until resolution is confirmed.

All data and documents are fictional.

31 seconds

A return with clear next steps

Read transcript

0:00You ordered ten products and want to return two. You ask Rellin for help.
0:05Rellin checks the delivery and return terms, then asks why you’re returning the products and what condition they’re in.
0:12You confirm they are sealed and you ordered too many. Only those two items are selected.
0:18Rellin prepares the request and shows the documents needed for review.
0:23You see the next steps. The team confirms eligibility and any costs under company rules.

All data and documents are fictional.

31 seconds

The case reaches the right person

Read transcript

0:00This is your third delayed delivery, and it is affecting your work. You ask to speak to a person.
0:06Rellin gathers the history of all three deliveries and the relevant documents.
0:11The summary shows the problem and the impact you described.
0:16Rellin routes the request to the support coordinator through the company’s escalation process.
0:22The coordinator receives the conversation and supporting documents. You continue without explaining everything again.

All data and documents are fictional.

Music: Inspired — Kevin MacLeod · Creative Commons Attribution 3.0

Choose your situation. See the result.

Explore the request, the prepared information and the effect of your choices.

Unclear delivery → documented discrepancy → handover to the owner → customer update → current case status. Returns and documents remain branches of the same after-sales relationship.

Explain delivery statusView exampleClose

The starting conversation

Customer: “The order says dispatched, but I have not received everything.”

Agent: “The order has two shipments. The first is confirmed delivered; for the second we have carrier collection but no receipt confirmation. How many parcels have you received?”

Customer: “Eight out of ten.”

The result of your choice

Choose a shipment

Shipment record

Parcels and status: Confirmed: 8 of 10 parcels · Delivered
Receipt confirmation: Confirmed: Receipt confirmation · today
Document and next step: Information: Source document: D-1042/1

Illustrative example · Fictional data

Visible result: the order split into shipments, the latest update and a verification request for the two parcels. Selecting a shipment shows its source document. Benefit: the customer gets a concrete explanation and the operator does not reconstruct the journey manually. An estimated date is not presented as confirmed delivery.

Discuss this situationLink to this example

Find the right document for the customerView exampleClose

The starting conversation

Customer: “Could you resend the delivery document for yesterday’s order?”

Agent: “I found two deliveries for your company. Do you mean headquarters or West Branch?”

Customer: “West Branch.”

The result of your choice

Choose the delivery site

Information: Delivery: West Branch
Information: Document D-1042/W · Recipient Ana
Pending: Message prepared · Access to verify

Illustrative example · Fictional data

Visible result: the document linked to the delivery, the verified recipient and prepared message. Changing the site changes the document. Benefit: less time finding and resending paperwork. Customer access and permission to send are checked before providing the document.

Discuss this situationLink to this example

Explain product use from the correct documentationView exampleClose

The starting conversation

Customer: “How do I install the cartridge for the Atlas P240?”

Agent: “I found the instructions for that model and the cartridge in your order. Here are the documented steps. If the error persists, I can prepare a technical support request.”

The result of your choice

Documentation model

Information: Atlas P240 manual · section 4
Information: Open the front cover; use the compatible P240 cartridge
Pending: If the error persists: prepare technical support

Illustrative example · Fictional data

Visible result: steps, the identified model and the source consulted. Selecting another model changes the instructions. Benefit: routine answers prepared without manual searching, leaving operators to focus on persistent problems. Unverified information is requested rather than assumed.

Discuss this situationLink to this example

Prepare an incomplete-delivery caseView exampleClose

The starting conversation

Customer: “Two boxes of paper are missing.”

Agent: “The order and transport document show ten boxes, and you confirm receiving eight. I have prepared the case with the difference and documents. At which site did you receive them?”

Customer: “West Branch.”

The result of your choice

How many boxes did you receive?

Needs verification: Ordered: 10 · Received: 8 · Missing: 2
Information: West Branch · Transport document attached
Pending: Case prepared for warehouse / transport

Illustrative example · Fictional data

Visible result: an incident record with products, quantities, site and owner. Changing the quantity recalculates the difference. Benefit: the warehouse or transport team receives a complete case with fewer intermediate questions. Reshipment and compensation are decided through the authorized process.

Discuss this situationLink to this example

Prepare a return with the conditions in viewView exampleClose

The starting conversation

Customer: “I ordered ten products but want to return two.”

Agent: “I identified the delivery and return conditions. I need the reason and product condition to prepare the request.”

Customer: “They are sealed; I ordered too many.”

The result of your choice

Condition of the two products

Information: 2 products · Reason: ordered too many
Information: Return conditions and documents assembled
Pending: Request prepared for review

Illustrative example · Fictional data

Visible result: selected products, applicable condition, required documents and return request. Changing product condition may route the request for review. Benefit: the customer knows the steps and the team avoids incomplete requests. Final eligibility and any costs are confirmed under company rules.

Discuss this situationLink to this example

Document a damaged or faulty productView exampleClose

The starting conversation

Customer: “The product arrived damaged.”

Agent: “I found the order. Which product is affected and what did you notice on receipt? You can attach the documents required by the complaints procedure.”

The result of your choice

When did you notice the issue?

Information: Case: damaged on receipt
Pending: Needed: description, delivery document, photos
Information: Owner: delivery complaints

Illustrative example · Fictional data

Visible result: a case file with product, receipt date, description and available attachments. Choosing “damaged on arrival” or “problem during use” changes the questions and responsible team. Benefit: the specialist starts with the necessary information. The agent does not promise replacement before case review.

Discuss this situationLink to this example

Hand over an urgent situation without losing contextView exampleClose

The starting conversation

Customer: “This is the third delay and it affects my work. I want to speak to someone.”

Agent: “I prepared the history of the three deliveries and the impact you described. I am routing the request to the responsible person through the escalation process.”

The result of your choice

Explore the handover

Needs verification: Three delayed deliveries · History assembled
Information: Stated impact: work affected
Pending: Summary and documents for handover

Illustrative example · Fictional data

Visible result: summary, documents, stated impact and handover owner. Urgency follows company rules. Benefit: the colleague can begin resolution and the sensitive conversation directly. The customer can reach a person without being trapped in a sequence of automated replies.

Discuss this situationLink to this example

Follow up on the step promised to the customerView exampleClose

The starting conversation

Operator: “We promised an answer today. What is still missing?”

Agent: “The warehouse confirmed the discrepancy; we are waiting for a delivery proposal. I prepared the follow-up message and a reminder for the owner.”

The result of your choice

Replacement delivery timing

Confirmed: Warehouse confirmed the discrepancy
Pending: Awaiting a delivery proposal
Pending: Message: we will update you after timing is confirmed

Illustrative example · Fictional data

Visible result: case timeline, delayed step and prepared communication. Confirming a deadline updates the message. Benefit: fewer lost commitments and less time tracking separate conversations. Closing the case requires the result specified by the procedure, not just sending a reply.

Discuss this situationLink to this example

Finish the day with case status up to dateView exampleClose

The starting conversation

Coordinator: “Which cases remain open, and what keeps recurring?”

Agent: “Four cases await customer documents and two await transport. Three requests concern the same installation instruction. I prepared the summaries and a proposed clarification of that instruction.”

The result of your choice

Which cases will you review?

Pending: 4 cases await customers
Pending: Owners and missing documents indicated
Pending: Follow-up messages prepared

Illustrative example · Fictional data

Visible result: cases with owners and a sourced summary of recurring issues. You can open each case before updating it. Benefit: less administration and more time to improve service. A recurring problem is a signal to investigate, not a proven cause.

Discuss this situationLink to this example

Less repetitive work. More time for what matters.

A faster, more useful first response. The agent checks the situation and asks for missing information instead of leaving the request without a next step.
Less repeating the same story. History and documents accompany the request when it reaches a colleague.
Fewer manual checks across systems. The order, delivery and relevant conversations are brought together in one case.
Requests followed through to the next result. The owner, missing documents and follow-up deadline remain visible.
More complete support records. The summary, category, actions and status are prepared for the support system and CRM.
More time for resolutions that preserve the relationship. People can handle sensitive complaints, exceptions and service improvements, with less time spent copying and searching.

For your team

For customer service teams, distributors, service companies and businesses with many after-sales enquiries. Rellin supports both the customer response and preparation for the human operator.

From the request to the next step

Order information and documents. The customer learns the status and receives a relevant explanation.

Handling requests after the sale. Delivery, return and product issues are documented and routed correctly.

Continuity and follow-up. The case reaches the right person with context and remains visible until closure.

Ellory prepares the next commercial action. Rellin handles the support request and follows its resolution. Both can use the same authorized context while retaining the owner of each process.

What could this look like in your team?

We’ll show you Agentiqal agents using scenarios prepared by our team.

Together, we discuss Rellin’s role and configuration for your company.

Talk to our team