Support

AI agent for customer support and handoff

An AI agent gives the first answer from approved information and hands complex cases to a person with the conversation context.

Viber

A damaged item gets a ticket number, not another round of questions

The AI agent collects the problem details and opens a support ticket through the connected system. The customer gets a reference and the team gets context for a replacement decision.

Dom Plus support Viber
  1. Customer

    The Luna lamp from order PR-410 arrived with a cracked base.

  2. Telp

    Sorry about the damage. Is only the base affected, and which email address is on the order?

  3. Customer

    Only the base. The order email is [email protected].

  4. Telp

    Ticket Z-905 has been opened for the Luna lamp from order PR-410 and sent to support. The replacement response will go to [email protected].

Website

Support picks up exactly where the customer left off

When routine instructions are not enough, the AI agent opens a ticket and hands the conversation to a person. It does not ask for passwords or claim access has been restored before the team acts.

Lingua support Website
  1. Customer

    I cannot open my course. I changed my password, but it still says the account is inactive.

  2. Telp

    An inactive account needs help from support. What is your name and which email do you use for the course?

  3. Customer

    Ana Primer, [email protected]. The German A1 course.

  4. Telp

    Ana, ticket Z-906 is open and the conversation has been sent to support. It notes that A1 is still unavailable after the password change. The reply will go to [email protected].

The customer context

An AI agent gives the first answer from approved information and hands complex cases to a person with the conversation context.

Resolves repeat questions from approved knowledge and hands complex cases to an operator without making the customer repeat everything.

What this workflow can cover

  • Search approved knowledge for grounded answers
  • Collect the identifiers and details needed for follow-up
  • Keep conversation history across AI and operator replies
  • Hand off with a reason, transcript and customer context

Support

How it works

  1. 1

    A customer asks a support question through a connected channel.

  2. 2

    The agent answers from approved knowledge or collects the details required for the case.

  3. 3

    If the request needs a person, the conversation moves to the operator inbox with context intact.

What your team gets

Faster first response

Fewer repeated questions for operators

Cleaner handoff between AI and the team

Telp

How your team keeps control

Business rules stay explicit

Instructions, required details and allowed actions are configured for the selected workflow.

Sensitive steps can wait for confirmation

The agent can prepare a structured request while a person remains responsible for the final action.

Handoff keeps the conversation

Operators receive the customer context, collected data and the point where help is needed.

Answer routine questions and leave exceptions to people

The AI agent uses approved information about services, delivery and support procedures. When details are missing, it first clarifies the request. Repeated questions are grounded in answers from business knowledge.

A problem does not have to be resolved in the first reply for the conversation to be useful. An order number, problem description and transcript prepare an employee to continue. A dedicated workflow handles returns and exchange requests.

The policy does not contain an answer

The agent does not extend business policy with its own assumptions. The question remains for a team member who can check the facts and decide on an exception.

The customer asks for an employee

The conversation enters the human handoff process. Its transcript stays available, while employee availability depends on how your team is organised.

FAQ

Frequently asked questions

What information does the AI agent use for support?

Approved business knowledge and data from permitted connected systems. The freshness of those sources determines which information it can reliably use.

What happens when the agent does not know?

It clarifies the question or leaves the case for an employee. It should not invent a price, deadline, order status or unavailable policy.

Can it resolve a complaint without an employee?

Collecting details and explaining a published process do not approve a complaint. Refunds, replacements and exceptions require a separate decision and permitted action.

Can employees read the previous conversation?

Yes, the conversation remains in the shared inbox. An employee can continue without asking the customer to repeat the entire problem.

Can it check a particular order's status?

Only with an appropriate data source and the necessary access checks. General delivery information does not establish the status of an individual order.

Does support also work on social channels?

It can operate through supported, separately connected channels. Each channel has its own reply rules; connecting one does not automatically activate the others.

Want to validate this workflow with your own examples?

Tell us the channel, current process and first result you want to improve. We will suggest a focused rollout path and the cases your team should test.

View pricing