Product
Six capabilities. One ticket. One desk.
DeskForge is the omnichannel platform your agents keep open: ticketing, workspace, messenger, knowledge, automations, and analytics.
DeskForge · Views
Online#1042 · chat · high
Checkout stall — size chart
Priya
The messenger popped on checkout. Does the parka run large? I can still edit the cart.Maya · Agent
True to size — I dropped the chart in the thread. Stay on this chat if you want me to hold the order.Internal note
Tagged checkout. Customer never sees this line.Ticketing
A queue that respects how support actually works
Statuses move from new to open, pending, on-hold, solved, and closed. Priority, type, groups, tags, and assignment are first-class — not fields you bolt on later.
- Views for yours, unassigned, live chat, new, and waiting
- Claim a ticket, assign a teammate, or leave it in the pool
- Email, web, API, and chat share the same ticket record
In this workspace
Ticketing
Sign in and use the real surface — this is not a mock API. The agent workspace, portal, and widget are the product.
Open the deskAgent workspace
Three panes. Public reply or a note they will never see.
The desk is a list, a conversation, and properties. Macros stamp the replies you already know. Internal notes stay on the workspace — the portal and messenger only get public comments.
- Composer for public reply vs internal note
- Properties: status, priority, type, group, tags, assignee
- Live refresh so a chat thread does not go stale mid-shift
In this workspace
Agent workspace
Sign in and use the real surface — this is not a mock API. The agent workspace, portal, and widget are the product.
Open the deskLive chat widget
A storefront messenger that becomes a ticket
One script tag loads the launcher. Visitors identify, chat over SSE with a polling fallback, and land in the live queue. Page-visit rules can greet on the paths that drop carts.
- data-key on the script selects the tenant channel
- Realtime to visitors and agents, plus desktop notifications
- Seeded rules on /pricing and /checkout in the playground
Website messenger
<script src="https://deskforge-axadrev.vercel.app/widget.js" data-key="df_pk_northwind_live" async></script>Knowledge
Publish the answer once. Let the portal take the repeats.
Categories, sections, and articles with draft vs published. Customers search the help center, read, and open a ticket when the article is not enough.
- Help center at /portal — no agent login required to read
- Customers submit and track tickets on the public thread only
- Staff can still jump from the desk into the same articles
In this workspace
Knowledge
Sign in and use the real surface — this is not a mock API. The agent workspace, portal, and widget are the product.
Open the deskAutomations
Triggers, time-based automations, and macros — without another workflow product
Triggers tag, assign, and escalate when a ticket changes. Automations run on a clock: pending follow-ups, stale New tickets, auto-close after solved. Macros keep replies consistent.
- Admin-managed triggers and hourly automations
- Business-hour or calendar clocks from the SLA calendar
- Widget rules with delay, greeting, and ticket side-effects
In this workspace
Automations
Sign in and use the real surface — this is not a mock API. The agent workspace, portal, and widget are the product.
Open the deskAnalytics
Command view for the people who run the floor
The dashboard is queue health, agent load, first-reply time, and a triage table. Reports cover volume, FRT, and resolution — the numbers a lead checks before standup.
- Open count on the desk chrome
- Volume and resolution in reports
- Live chat board for the conversations happening now
In this workspace
Analytics
Sign in and use the real surface — this is not a mock API. The agent workspace, portal, and widget are the product.
Open the deskSee it on a storefront
The playground embeds the same snippet your marketing site would ship.