Alpha Now boarding early teams

One queue for every customer message

Slack, Telegram and email, grouped by AI, timed against your SLAs and answered where they started.

Start 14-day trial

Per-seat pricing · no setup fees · cancel anytime

Webhook retries return 410

DKT-1042 · #fernway-support

Resolve
PN

Priya N. 9:41 AM

Since this morning every retry to our endpoint comes back 410. Nothing changed on our side.

Screenshot read: 410 errors spike on /orders and /refunds from 08:52.

TR

Tomás R. 9:47 AM

Found it: the endpoint was disabled after a burst of failures. Re-enabling it now and replaying the missed events.

✅ Resolved from Slack by Priya
Reply in Slack… Send

Running clocks

Counted in business hours, per tier

On track At risk Breached
  • Invoice PDF shows the wrong VAT number

    DKT-1051 · Standard · first response

    2h 10m left

  • SSO login loops back to the sign-in page

    DKT-1048 · Priority · first response

    18m left

  • Export to CSV times out on large workspaces

    DKT-1044 · Priority · resolution

    Breached 1h ago

  • How do we add a second billing contact?

    DKT-1039 · Standard · resolution

    Paused · closed hours

New dockets

412 +8%

Median first response

14 min −22%

SLA attainment

97.2% +1.4 pts

Dockets per day

Last 14 days

Sep 30 Oct 13

Which priority customers are closest to breaching this week?

Two dockets are inside the last 30 minutes of their clock, and one has already breached.

DocketCompanyClock
DKT-1048 Northwind 18m left
DKT-1053 Fernway 27m left
DKT-1044 Halcyon Breached
Ask about your queue…

Where your customers already talk

  • Slack
  • Telegram
  • Email
  • Live chat

The pipeline

How a stray message becomes a solved docket.

No forms. Customers talk where they already do; Deskstar does the filing.

  1. 01

    It arrives

    In a shared Slack channel, your Telegram bot or your inbox.

    • #fernway retries come back 410…
    • tallis export keeps timing out
    • harbour SSO for a second workspace
  2. 02

    It finds its docket

    Matched by meaning, so follow-ups never become duplicates.

    “Also — evt_8f2c41 is one of them”

    posted outside the thread

    DKT-1042 grouped
  3. 03

    The clock starts

    The customer's tier sets the SLA, timed in your business hours.

    First response 18m left

    Enterprise tier · 30m target

  4. 04

    The answer goes home

    Reply from Deskstar; it lands back in the original thread.

    “Fixed — retries are flowing again.”

    sent to the Slack thread

Shared channels

Lives in the thread, not next to it.

Most B2B support happens in Slack. Deskstar follows it as it unfolds.

  1. 1

    React ✅ to resolve. Un-react to reopen.

  2. 2

    Edits stay in sync. Deletes leave a trace.

  3. 3

    Screenshots get read. Described by AI, so they're searchable.

  4. 4

    Stragglers get grouped. Even outside the thread.

Commitments

The clock knows when you're closed.

Targets per tier, in business hours. Weekends and holidays don't count.

DKT-1051 · Invoice PDF shows the wrong VAT number

Standard tier · first response in 4 business hours

Fri 15:10 · created
Mon 11:10 · due
Fri · open
closed · 64h
Mon · open
12:00 17:00
clock pauses
09:00
resumes
14:00
Target
4h
Wall clock
68h
Breached?
No

Wingman

Ask your queue anything.

Wingman is the assistant for your team. It reads dockets, companies and SLAs, and answers with the numbers behind the answer.

  • Read-only. It looks things up, it never changes a docket.
  • Summarises a long thread before you reply.
  • Counts come from your data, not the model's guess.

Which priority customers are closest to breaching this week?

Two dockets are inside the last 30 minutes of their clock, and one has already breached.

DocketCompanyClock
DKT-1048 Northwind 18m left
DKT-1053 Fernway 27m left
DKT-1044 Halcyon Breached
Ask about your queue…

New dockets

412 +8%

Median first response

14 min −22%

SLA attainment

97.2% +1.4 pts

Dockets per day

Last 14 days

Sep 30 Oct 13

Insights

See how the queue is really doing.

Volume, response times and SLA attainment, by day, channel and tier. Built from the events as they happen, so the charts match the queue.

And more

The rest of the toolkit.

  • Workflows

    Branch, wait for days, then act, on a visual canvas.

  • Automation rules

    Assign and notify the moment a docket arrives. Forms, not code.

  • Companies & tiers

    Tiers decide which SLA each customer gets.

  • Broadcasts

    Announce incidents and releases to a segment, by email or Slack.

  • Help center

    Publish articles on your own domain, in your brand.

  • Encrypted at rest

    Encrypted messages, isolated workspaces, role-based access.

Pricing

Pick a flight plan.

Priced per seat. Orbit and above add Slack, Telegram, workflows and broadcasts, plus more AI credits.

Launchpad

$10 USD / seat / mo

AI credits / mo
1,200
Trial
14 days
  • Email and live chat
  • AI grouping and SLAs
  • Insights, companies and tiers

Orbit

$25 USD / seat / mo

AI credits / mo
3,000
Trial
14 days
  • Everything in Launchpad
  • Slack and Telegram
  • Workflows and automation rules
  • Broadcasts

Interstellar

$55 USD / seat / mo

AI credits / mo
5,000
Trial
14 days
  • Everything in Orbit
  • The largest AI credit pool

See what's included and how billing works →

  • → Owners, admins & agents take seats
  • → Viewers, billing & IT free
  • → Prorated seats
  • → Cancel anytime

FAQ

Before you board.

What does “alpha” mean for us?
The core is built and in daily use. Expect fast releases, a few rough edges, and a team that acts on your feedback.
Which channels are supported?
Slack (including shared channels), Telegram and email. More are coming.
Is there a free plan?
No — every plan starts with a 14-day trial. A card is required; cancel before it ends and you won't be charged.
What are AI credits?
The currency for AI your team uses directly, like the assistant. Grouping, summaries and image reading on incoming messages are on us and never use credits. Each plan includes a monthly pool for the workspace; extra credits are $0.02 each.
How is our data protected?
Messages are encrypted at rest, workspaces are isolated, and roles control access.

Stop chasing threads. Start closing dockets.