FeaturesWhat's nextQuestions
In development

Email support.
A shared place
to get it done.

Give every request an owner, every reply its context, and your team a clear way forward. XpressHelp brings email and ticket work together.

Ticketing and email are deployed. The broader product is still being built.

A conversation, with the whole story Illustrative example
SUP-24Open

Help with an export

Priority: NormalAssigned to: Alex
Customer

My export stops halfway through. Can you help me find out why?

Internal note

Reproduced with the same filter. Checking the date range before we reply.

Visible to your team
Alex · Public reply

Thanks for the details. Could you send the date range you're exporting?

Conversation and team context, togetherEmail ticket

For the people
behind the inbox.

When support lives in a shared mailbox, it's easy to lose track of who is handling what. XpressHelp gives your team a shared ticket workspace, with the customer conversation and internal discussion in the same place.

Built today

A practical help desk.
Room for the whole team.

The ticketing and email foundation is deployed. These are the capabilities already implemented, rather than promises from the roadmap.

A clear home for every request

Turn incoming email into tickets. Keep threaded replies, attachments, status, priority, tags and ownership together.

Teamwork with the context intact

Use internal notes, mentions, followers and CCs. Live updates and teammate presence help your team stay in step.

Less repetition, more attention

Find tickets with search and saved views. Apply manual macros, make bulk changes and move quickly with keyboard shortcuts.

Keep an eye on email

See delivery status, review suspended messages and manage blocked senders. Choose the notifications you receive in the app and by email.

Clear roles, shared context.

Owners, admins, agents, light agents and knowledge editors have distinct permissions. Private attachments and workspace access checks keep support data within its workspace.

The direction

Good answers should
outlast the ticket.

The goal is to turn resolved conversations into useful knowledge, with a person reviewing every AI draft. That pipeline is planned; it isn't available today.

In development

A knowledge base your team can maintain

An article editor and builder, with drafts, review, publishing and version history, are implemented in an unmerged change awaiting deployment approval.

Planned

Help customers find their next step

A public help center, customer portal, search and support widget are part of the next knowledge base milestone. Live chat follows later.

Planned

AI assistance with human judgment

Ticket summaries, reply drafts and article suggestions come before a pipeline that drafts knowledge from resolved tickets for human review.

Automation, SLAs, reporting, billing and XpressFlux integration are also planned. The roadmap sets a direction, with no published release dates.

A few useful answers.

Is XpressHelp finished?

No. The ticketing and email foundation is deployed, while the knowledge base, portal and AI work are still in development or planned. Contact XpressBase to discuss the current scope before relying on it for your team.

Can I see a demo or discuss access?

Contact XpressBase to discuss XpressHelp and arrange next steps. You can join the waitlist to request access. Joining does not create an account or guarantee access; approved requests receive an invitation. Existing users can sign in to the application.

What does it cost?

Commercial pricing hasn't been finalized. Pricing ideas in the product plan are hypotheses, not current offers. Talk to XpressBase about your team's needs.

Does the AI publish articles or send replies on its own?

The AI features are planned. The intended knowledge workflow requires a person to approve each draft before publication.

Let's talk about
your support workflow.

See whether the current help desk fits your team, and discuss what's coming next.

Join waitlist