Contact

AI customer support in Pharen Hub

Every customer request lands in one list and an agent sorts it. For common questions it drafts the reply from your help articles, bugs go to engineering, and complaints go straight to a person.

AI customer support: the support requests list in Pharen Hub with customer, category, priority, status and owner.
The support requests list in Pharen Hub. Labels are in German.

The same questions, every day

Forgot my password, got the invoice twice, how do I export the list? The team has answered most requests many times. In between sits the one bug that has to be fixed today.

In Pharen Hub an agent sorts first. What is in the help articles, it answers in a draft. What is urgent reaches engineering right away.

How it runs in Pharen Hub

  1. Process

    Step 1: Every request lands in one list

    Requests from the inbox and the customer portal become rows in the support requests list. The board shows what is new, what waits as a draft and what sits with engineering.

    Board of support requests in Pharen Hub with the columns new, draft ready, answered and with engineering.
    The requests by status, from new to with engineering.
  2. Agent

    Step 2: An agent sorts and drafts

    The agent reads the message, sets category and priority and searches your help articles. If one fits, it drafts the reply.

    Below the draft it names the article the answer comes from.

    Open support request in Pharen Hub: the customer's message, the agent's reply draft and the help article as source.
    A request with a reply draft and the help article it comes from.
  3. Person

    Step 3: It only answers with your knowledge

    The agent only knows the help articles you give it. If no article fits, it writes no draft.

    So no reply contains anything you did not write yourselves.

    Knowledge sources of the support agent in Pharen Hub: linked help articles with read access.
    The agent's knowledge sources: your help articles, read only.
  4. Rule

    Step 4: A workflow routes

    High-priority bugs go to the engineering channel. Complaints go to a person in support, questions about new features to sales.

    Everything else waits as a draft for approval.

    Workflow for new support requests in Pharen Hub: search help articles, support agent and three branches for bug, complaint and other.
    Search the help articles, sort, then three paths: engineering, a person or a draft.
  5. Process

    Step 5: Engineering sees bugs right away

    In the engineering channel the agent reports the bug with customer and urgency. Engineering replies in the thread, and everyone sees when it is fixed.

    Engineering channel in Pharen Hub: two bug reports from the support agent and replies from engineering.
    The agent's bug reports in the engineering channel, with engineering's replies.

What the agent does not do

It sorts and drafts. Your team talks to customers.

More use cases

Questions about AI customer support

What are your plans for AI? Let's talk about it.

Whether it is strategy, training or delivery, you talk to our founder Johannes for 30 minutes. There is nothing to prepare.

We have already worked with more than 50 clients.

How the call works

1

Your topic

You tell us what it is about and where you stand with AI.
2

Our assessment

We tell you whether AI helps with it, and how.
3

Your next step

You get a proposal and decide for yourself.