Requests as conversations
Each request is a conversation with a subject and a threaded message history.
Customer messages and support requests as tracked conversations, not lost emails.
Farexa Support Tickets turns requests into conversations with a subject, status, priority, and a threaded message history — and guests can raise and follow one without an account — so nothing drops between an inbox and a memory.
Support falls apart in shared inboxes: a request read and forgotten, a reply nobody knew was sent, a customer chasing an update no one can find. Farexa Support Tickets makes a request a conversation on the record. Each carries a subject, a status, a priority, and where it came from, with the full thread of messages attached — so the state of a request is something you can see rather than reconstruct from an email chain.
Guests don't need an account to be helped. Someone can raise a request and follow the conversation through a secure guest link, so a customer who isn't a user still gets a tracked thread instead of a black hole. Internally, the conversation keeps its history, so whoever picks it up sees what's already been said rather than starting the reply from scratch.
It's an honest service-desk: a clear queue of conversations with status and priority, built for teams that need requests tracked and answered. It's the place customer questions, service requests, and internal issues live as records — so "did anyone deal with this" has an answer.
Key features
What a request carries.
Status and priority
Conversations carry a status and priority, so the state of a request is visible.
Source on the request
Each conversation records where it came from, so channels are on the record.
Guest access without an account
Guests raise and follow a request through a secure link, no account required.
Full message history
The whole thread stays attached, so whoever picks it up sees what's been said.
A clear queue
Conversations sit in a queue you can read by status and priority.
Customer and internal requests
Handle customer questions, service requests, and internal issues in one place.
Part of the platform
Support lives alongside the customers and website the rest of the business uses.
How it works
From request to resolution.
01
A request arrives. A customer, guest, or team member raises a request; it becomes a conversation with a subject.
02
Set status and priority. The conversation carries its status and priority, so its state is visible in the queue.
03
Reply on the thread. Messages attach to the conversation, so the full history travels with it.
04
Keep guests in the loop. Guests follow the conversation through a secure link, without needing an account.
05
Resolve on the record. The conversation moves through its statuses to resolution, with the history intact.
Who it's for
Who runs a desk here.
- Facility and maintenance service desks — Service requests tracked as conversations with status.
- Businesses supporting customers — Customer questions answered on a thread, not lost in an inbox.
- Teams with internal issues to track — Internal requests as records with a clear queue.
- Support staff and managers — Staff answer on the thread; managers read the queue by status and priority.
Works with
Where support connects.
- CRM — Requests sit alongside the customer records they relate to.
- Website — Public inquiries and support requests come from the same front.
- Analytics — Request volume and status reporting.
- Sales — Support context for the customers you sell to.
- Appointments — Service visits that follow a request.
FAQ
What support teams ask.
Is a request tracked or just an email?
Tracked. Each request is a conversation with a subject, a status, a priority, and its source, with the full thread of messages attached — so its state is something you can see in a queue rather than reconstruct from an email chain.
Can customers without an account get support?
Yes. Guests can raise a request and follow the conversation through a secure link, without needing an account — so a customer who isn't a user still gets a tracked thread instead of a black hole.
Does the history stay with the request?
Yes. The full message history stays attached to the conversation, so whoever picks it up sees what's already been said and can continue rather than starting the reply from scratch.
Does it assign tickets or track SLAs?
It's an honest service desk: conversations with subject, status, priority, source, and threaded history in a clear queue. It doesn't currently include formal ticket assignment or SLA timers — so the page won't claim them. What it does, it does on the record.
What kinds of requests can it handle?
Customer questions, service requests, and internal issues all live here as conversations, and because support is part of the platform, requests sit alongside the customers and website the rest of the business uses.
Stop losing requests in an inbox.
Book a walkthrough and see requests become tracked conversations, with guests able to follow along without an account.