CONNECTED SELF-SERVICE EXPERIENCE
Customer Portal
The Ticketix customer portal is a support homepage where customers sign up, submit tickets with or without an account, track and answer their tickets, rate the support they received, search knowledge articles and join a moderated community. Accepted solutions in the community stay visible for future visitors.
Support Homepage
Give customers one starting point for every kind of help.
The portal homepage presents "How can we help?" with a search field, cards that open the sign-in, sign-up, ticket and tracking windows on the same page, links to the knowledge base and the community, product cards, popular articles and common questions. A customer can look for an answer first and open a ticket only when needed.
Customer-facing homepage. A page for customers, separate from the agent workspace and its own staff sign-in.
Search everywhere. The homepage search suggests articles while the visitor types, and Ctrl K or / opens a search window on every page that also offers actions such as submitting a ticket.
Homepage cards. Login, Sign up, Submit Ticket, Track a Ticket, Knowledge Base, Community and Admin by default. The administrator can rename, reorder, hide, remove or add cards. Login, Sign up, Submit Ticket and Track a Ticket keep their address and icon and cannot be removed, but they can be hidden and given their own label and description for each portal language; a hidden card's window still opens from its direct link.
Customer accounts. Sign-up with email verification and sign-in; invited customers activate their account from the invitation link.
Password reset and account security. Forgot password? emails a one-time reset link that is valid for 60 minutes, and customers can turn on two-factor authentication with an authenticator app under Account security.
Announcements. Information, known issue and maintenance messages appear as a band on every portal page for the time the administrator sets and, for a product, on its ticket form; a visitor can hide the band until its text changes.
Product pages and release notes. Each product has a page with its guides, common questions, community topics and, when release notes are kept, the current and latest versions.
Page images, cards and footer are configured in administration; see Portal Content.
Customer Ticket Area
Let customers follow and continue their own requests.
Signed-in customers see their own tickets, the status and priority of each and the public conversation. They reply and attach files from the same view, so a request continues where it started.
- My tickets with the lists All, Open, Waiting for you and Closed, and the conversation of a ticket in a window.
- The ticket window with product, priority, subject, message and several attachments; the product's form fields appear without reloading the page.
- While the customer types the subject, up to three knowledge articles are suggested; This solved my problem closes the form without a ticket, and the question counts as solved without a ticket in the reports.
- Ticket page with conversation, ticket summary, submitted form details, attachments and the technical details that one of your applications sent.
- A reply to a closed ticket reopens it.
- When the ticket closes, the customer receives one Ticket closed email with the ticket link and a rating link, and can rate the support from 1 to 5 stars with a comment, once per ticket.
Customers see only their own tickets and never internal notes. A rating of 1 or 2 notifies the department manager in the app, or the first active administrator when the department has no manager; see Response & Resolution Metrics.
Guest Tickets & Tracking
Accept requests from people who have no account yet.
The ticket window opens a ticket without an account. The confirmation email carries a link that opens the ticket directly for seven days and confirms it on first use; the ticket number and a tracking password stay in the email as a backup.
Guest form. Name, email, product, priority, subject, message, an attachment and the product's form fields.
Email verification. A new guest ticket waits in Pending Verification until the guest opens the link in the confirmation email; the same email carries the ticket number and a tracking password.
Spam checks. A hidden form field, a spam score and submission limits per address catch automated submissions; high scores go to Spam and doubtful tickets to Manual Review.
Tracking. Track a ticket opens the conversation in a window with the ticket number and tracking password, and the guest can reply there; the private ticket link works the same way.
Account from a ticket. A guest can set a password from the ticket link to turn the guest record into a portal account.
Existing accounts stay safe. A guest ticket sent with the email of a registered customer does not change that account or its portal access.
Portal Layout & Language
Serve the portal on any screen in the languages you support.
The portal uses a responsive layout and is available in English, Turkish and Arabic. Arabic switches the interface to right-to-left.
Responsive portal. Pages adapt to phones, tablets and desktops.
Page images. The main page, the knowledge pages, the community pages and the search page can each show their own background image.
Light and dark theme. Visitors choose System, Light or Dark.
Language switch. Visitors choose a language from the header; the administrator sets the default language and which languages the portal shows.
Customer content untouched. Interface translation never changes the words inside customer messages or ticket subjects.
Community Discussions
Let customers ask in public and learn from each other.
The community is a moderated space organized in categories. Visitors open topics with a title and content, others reply, and the support team takes part in the thread.
| Element | Purpose |
|---|---|
| Categories | Group topics by product or subject; a General category is always available. |
| Topics and replies | Formatted posts; visitors without an account post under a name they enter, and with the default setting their posts appear after a moderator approves them. The administrator can also allow posting only after sign-in. |
| Following | Signed-in users follow a topic and are notified of new replies. |
| Reporting | Signed-in users report a topic or reply for moderator review. |
| Views and pinned topics | View counts and pinned topics help visitors find active discussions. |
| Posting limits | Hourly limits, a link limit and duplicate checks slow down spam. |
Community posts are included in the portal search; see Unified Search.
Accepted Solutions
Turn a solved discussion into an answer the next visitor can find.
When a reply resolves a topic, an agent or administrator marks it as the solution. The topic shows a solved signal, and the solution stays public so later visitors find it through browsing or search.
Marked solution. The chosen reply is highlighted, and the topic counts as solved.
Public knowledge preservation. Solved topics remain available instead of disappearing into closed tickets.
Self-service deflection. Customers who find a solved topic may not need to open a ticket.
Search ranking. Solved topics and solution replies rank higher in search; see Ranking Signals.
From topic to article. A solved topic becomes a knowledge base draft with its question and solution, linked to the topic, in one step.
Community Moderation
Keep public discussions useful and on topic.
Agents and administrators moderate the community from the administration area. A moderation queue gathers guest posts waiting for approval, reported posts, topics unanswered for 24 hours and solved topics without an article.
Approval and reports. Approve or reject guest posts; dismiss a report or hide the reported topic or reply.
Topic controls. Edit, pin, lock and unlock topics, hide or delete replies, reply as staff and mark solutions.
Merge duplicates. Merge a duplicate topic into another topic found by its title; its replies move there.
Create a linked ticket. Turn a registered customer's topic into a private ticket when it needs one-to-one support.
Categories. Create and order categories with their own descriptions.
Moderation is available to agents and administrators; see Users, Roles & Security.
A Practical Customer Portal Workflow
- Set the page images, homepage cards and footer, and choose whether guests post after approval or must sign in.
- Create community categories that mirror your products or services.
- Publish a few knowledge articles so the search field returns results on day one.
- Submit a guest ticket, confirm it by email and open it with the ticket number and tracking password.
- Post a community question, answer it from a support account and mark the reply as the solution.
Questions About the Customer Portal
Can a customer see tickets opened by other customers?
No. The ticket area shows only the signed-in customer's own tickets, and a guest sees only the ticket opened with its number and password or private link.
Do customers need an account to use the community?
No. Anyone can read. By default, guests post under a name they enter and their posts appear after a moderator approves them; the administrator can also allow posting only after sign-in. Following topics and reporting posts require a signed-in account.
Who can mark a reply as the accepted solution?
Agents and administrators. The topic author cannot mark a solution.
Is the portal usable on a phone?
Yes. The customer portal is responsive; see Mobile & Responsive Experience.
Continue Your Ticketix Workflow
Reviewed against Ticketix 2.2.1 source code · Last updated 9 November 2026