Entexia | Intelligent ecosystem
Built into the platform

Support ticket system

Manage customer requests, assign agents, track statuses and reply with AI assistance — all in one place.

No external helpdesk tool needed. The ticket system is part of the Entexia platform and integrates with CRM, customer portal, and billing.

How the ticket system works

From the first request to resolution — every step is tracked and documented.

01
Intake
Request arrives via portal, email, form or manual entry.
02
Classification
Request is categorised, given a priority, and assigned to an agent.
03
AI assistance
AI suggests a reply which the agent reviews and sends.
04
Reply
Agent replies. Customer sees the reply in the portal and via email.
05
Resolution
Request is closed, credits are deducted, audit is saved.

Request statuses

Every request goes through clearly defined phases from intake to closure.

Open

New request awaiting assignment

In progress

Agent is actively working on the request

Waiting

Request awaiting customer reply

Resolved

The matter was resolved with a reply

Closed

Request is archived and locked

Ticket intake channels

Requests come from different sources — the platform automatically unifies them into a single flow.

Customer portal

Customer logs in and submits a request through the secure web portal.

Email

Customer email is automatically converted into a ticket with all metadata.

Web form

Embedded form on your website directly opens a new request.

Manual entry

Agent manually opens a request for a phone call, in-person meeting, or internal task.

Two views — one system

Agents see the complete overview, customers see only their own requests.

Agent view
Intranet interface
  • All requests with filters and search
  • Agent assignment and priorities
  • Internal notes visible only to the team
  • AI reply suggestion with one click
  • Customer credit balance in real time
  • Complete communication history
  • Statistics and SLA reports
Customer view
Customer portal
  • Overview of all personal requests
  • Submit a new request with description
  • View agent replies
  • Request status in real time
  • Email notification on change
  • View credit balance
  • Requests protected with password

What it looks like in practice

Realistic preview of the agent interface, customer portal, and statistics.

Ticket overview and counters

Agent sees the state of all tickets with live counters.

app.entexia.com/tickets
12
Open
5
In progress
3
Waiting
48
Resolved today
#1047Cannot log in to the systemIn progress2 min
#1046Error exporting PDF invoicesOpen14 min
#1045Question about VAT settingsWaiting2 h

Agent replies to a ticket

Conversation thread with replies, internal notes, and AI button.

app.entexia.com/tickets/1047
JN
John Smith14:22
Hello, when I click the export PDF invoice button I get an error: Error 500. Please help.
Internal note14:31Team only
Check in CRM - customer has Enterprise plan, likely a server-side font library issue.
MK
14:35Maja K.
Hello! We identified the error - it is a library update issue. The fix will be available in 2 hours. We apologize for the inconvenience.
Write a reply...
0 / 2000

Customer adds a comment in the portal

The customer portal is a private page, password-protected, separate from the agent interface.

support.entexia.com/portal
Ticket #1047
Cannot log in to the system
Credits: 42In progress
Vi
You14:22
Hello, when I click the export PDF button I get an error...
14:35Support team
Hello! We identified the error. The fix will be available in 2 hours. Thank you for your patience.
Thank you for the quick reply! Will this also affect Excel file exports?
67 / 2000

How it all works in practice

Below are all the key steps explained - from the customer's first message to closing the ticket and deducting credits. Everything is designed so no message goes through the wrong channel.

Customer portal

How a customer adds a reply to a ticket

Once a customer submits a ticket, they don't lose contact with it. They can return to the customer portal at any time, review the full conversation with the agent, and add a new message. This is especially useful when the customer forgot to mention something, wants to confirm the solution worked, or when the issue reoccurs.

Steps for the customer
  1. 1
    Log into the portal
    Customer visits the customer portal and logs in with their credentials.
  2. 2
    Finding the ticket
    In the list of their tickets, they find the one they want to add to.
  3. 3
    Writing the message
    At the bottom of the page is a text field. The customer types their message in any length - short or longer.
  4. 4
    Click Add comment
    The message is immediately visible to the agent. The ticket status automatically returns to Open so the agent notices the new message.
What happens after
The agent in the intranet system sees a notification about the new customer comment.
The ticket status is automatically set back to Open so the ticket doesn't remain unnoticed in the Waiting for reply status.
Every comment is marked with a timestamp and the customer's name so the chronology of the conversation is clear.
The customer can add as many comments as they want. There are no limits on the number of messages per ticket.
Note: The customer cannot add comments to closed tickets. Once the agent closes a ticket, the conversation is locked and the customer must open a new ticket for a new question.
Team only

What is an internal note and why it exists

An internal note is a special type of message that an agent writes within a ticket, but it is visible exclusively to members of the support team. The customer absolutely never sees it - neither in the portal nor in any email. It is intended for team communication: logging phone calls, agreements, warnings for colleagues, or internal instructions.

How the agent adds one
  1. 1
    Opens the ticket
    Agent opens the ticket in the intranet system.
  2. 2
    Clicks Internal note
    Instead of the Send reply button, they click the Internal note button. The text field turns yellow as a visual cue that the message will not go to the customer.
  3. 3
    Types the note and saves
    The note is saved and displayed in the conversation with a yellow background and lock icon.
When to use it
Customer called by phone - agent logs the call content so the team has context.
The ticket needs to be escalated to a colleague - agent writes what they have already checked and what the next step is.
Customer is on a waiting list for a refund - agent notes when it is scheduled.
Internal information about the customer: VIP customer, special agreement, sensitive situation.
Security guarantee: The system technically prevents an internal note from ever reaching the customer. It is not shown in the customer portal, is not included in any email, and is not visible in any customer-accessible history.
Email notification

What happens when the agent clicks Send reply

When an agent writes a reply and clicks Send reply, the system simultaneously does two things: saves the reply in the ticket conversation thread where the customer sees it in the portal, and immediately sends the customer an email with the reply content. The customer does not need to constantly check the portal - the email notifies them that a new message has arrived.

What the customer email contains
Email subject
[Reply] tag + ticket number + ticket title
[Reply] #1047 - PDF export error
Sender
Your organization's email address, which you set in the system
podpora@vasepodjetje.si
Content
Greeting, name of the agent who replied, full reply text, and a button to view in the portal
Email example
From:podpora@vasepodjetje.si
Subject:[Reply] #1047 - PDF export error

Dear John,

agent Maja K. has replied to your ticket.

Hello! We have identified the error - it is a library update issue. The fix will be available in 2 hours.
View in portal
Customer receives an email when:
  • agent sends a reply to the ticket
  • ticket status changes
  • ticket is marked as resolved
Customer does not receive an email for:
  • agent internal notes
  • changes to internal ticket settings
  • agent assignment (not visible to customer)
Credit model

When and how a credit is deducted from the customer's balance

The credit model is designed for businesses that offer paid services - for example fortune-telling, personal consulting, coaching, or legal assistance. Each customer has a credit balance that they top up in advance through a subscription or one-time payment. A credit is deducted when the agent adds a comment or reply to the customer's question - that is, when the agent actually does their work and delivers a solution or explanation to the customer. Submitting a ticket and customer comments do not consume credits.

When credits are deducted and when not
Customer submits ticketCredit: unchanged

Customer writes a question or problem description and clicks Send. Nothing is deducted - submitting a ticket is free, regardless of how much text is written.

Customer adds commentsCredit: unchanged

Customer writes new messages, clarifies the issue, adds images or information. Customer comments never deduct credits - the customer is the one seeking help, not providing it.

Agent adds a comment or replyCredit deducted

When the agent writes a reply and clicks Send reply - that is, when they actually deliver their solution, advice, or explanation to the customer - the system deducts the configured number of credits from the customer's balance at that moment. Credits are only deducted for agent replies, not for internal notes. Sending an email to the customer is just a consequence of the agent's reply, not a separate step.

Balance visibility

The customer sees their credit balance in the portal next to each ticket. The agent sees the customer's balance in the ticket sidebar before writing a reply - so they know if the customer has enough credits.

Insufficient credits

If the customer does not have enough credits, the agent sees this in the sidebar before replying. The decision whether to send a reply anyway or first notify the customer about the empty balance is in the agent's hands.

Manual adjustment

Administrator can manually add or remove credits from a customer's balance. Suitable for error corrections, compensation, or promotional credits.

AI

AI suggests a reply in seconds

When an agent opens a request, they click 'AI suggests reply'. The model analyses the request content, communication history and returns a reply suggestion. The agent reviews it, edits if needed, and sends.

  • Tailored to the request context
  • Considers communication history
  • Agent has the final say before sending
  • Speeds up reply by 60–80 %
AI ASISTENT

Hello, thank you for your message. Your request has been received. Our team will reply within 24 hours. For urgent matters, please call us at ...

Credit model for paid services

Ideal for consulting, fortune-telling and services with limited access.

01
Customer buys credits

Customer acquires a credit balance via subscription or one-time payment.

02
Submits a question

Customer submits a request or question via the portal.

03
Credits are deducted

Upon resolution, the defined credit amount is automatically deducted.

All features

The ticket system in Entexia includes everything you need for professional customer support.

AI reply suggestion

With one click, get an AI-generated reply suggestion tailored to the request content.

Categories and priorities

Classify requests by category (technical, billing, general...) and priority (low–urgent).

Internal notes

Agents leave internal notes visible only to the team — the customer doesn't see them.

Email notifications

Customer automatically receives an email on every status change or new reply.

SLA and response times

Set SLA deadlines for each priority and trigger an alert before the deadline.

Credit billing

For paid services, credits are automatically deducted when a request is resolved.

Customer portal

The customer has their own password-protected portal with all their requests.

Audit trail

Every status change, reply, and action is recorded with a timestamp and author.

Frequently asked questions

What is the ticket system in Entexia?

The ticket system is a built-in module for managing customer requests and internal tasks. Every request gets its own tracking, status, responsible agent, and communication history. It works through the customer portal, email, manual entry, or a web form.

Can customers see the status of their requests?

Yes. Every customer gets access to the customer portal, where they can see all their requests, agent replies, and communication history. The portal is private and password-protected.

How does AI assistance work when replying?

When an agent opens a request, they can click 'AI suggests reply' to get an automatic response proposal based on the content of the request and your knowledge base. The agent reviews and confirms or edits before sending.

Does the ticket system support credit billing?

Yes. For fortune-telling, consulting, and similar services, we support a credit model: the customer has a credit balance, and each request deducts a certain number of credits. Agents see the balance in real time.

How many request categories does the system support?

The system supports: general, technical, billing, feature request, fortune-telling, SMS consulting, and other. You define the categories based on your business.

Is the ticket system included in the subscription?

Yes, the ticket system is part of the Entexia platform and does not require additional payment or third-party integration. It is included in every subscription from the Starter plan onwards.

Try the ticket system for free

7 days free, no credit card required. The ticket system is built into every subscription.

Start for free