Skip to content
Start free

Every promise to a customer, kept on time.

Turn a message into a ticket with a number, a type and a deadline. Risti counts your working hours, pauses while you wait on the customer, and shows what's due next.

Dilnoza RahimovaWhatsApp · +998 90 000 12 34
CH-1042Delivery issueHighReply in 12 min
Salom! Divanning oyog‘i yorilib qoldi, rasm yubordim.

Aziz made this ticket CH-1042

Dilnoza was told her ticket number

Uzr so‘raymiz! Ertaga yangi oyoq olib kelamiz, bepul.
Note Warehouse is sending a new leg tomorrow.
Reply on WhatsApp…

Numbers your customers can quote

Each ticket gets your prefix and the next number, like CH-1042. Customers can mention it in any channel, and your team finds it in a second.

  • Types with their own details: order number, product, a photo, a date.
  • Details can be required from the start or only before solving.
  • Four priorities, from low to urgent, each with its own deadlines.
CH-1046Chair arrived with a torn seatOverdue 25 min
CH-1042Lola sofa: cracked oak legReply in 12 min
CH-1039Grey cover instead of beigeReply in 2 h
CH-1030Invoice for the office orderWaiting on customer

A clock that knows your working hours

Deadlines count only while you're open, skip holidays, and stop while you wait on the customer. When time runs short, the ticket turns amber; when it's missed, it turns red.

  • Opening hours and holidays in your organization's time zone.
  • Waiting on the customer pauses the clock; their reply starts it again.
  • First reply, next reply and solved-within targets per priority.
A working weekOpenWaiting on customer
  • Mon
  • TueDue
  • Wed
  • Thu
  • Fri
  • Sat
  • SunClosed
06:0012:0018:0024:00

The finer points

Built for teams where one request can involve a chat, an email, a phone call and the warehouse.

  • Internal tasks

    Ask another team for something, with its own due time, linked to the customer's ticket. The customer never sees it.

  • Merge duplicates

    The same problem arrived by WhatsApp and email? Merge the tickets; the conversations move to one.

  • Solve with an outcome

    Replacement sent, refunded, repaired: choose how it ended, from outcomes your organization sets.

  • Reopens when the customer replies

    A reply within seven days reopens the ticket. After that, it starts a new ticket linked to the old one.

  • The customer knows where things stand

    Risti can tell customers their ticket number on their own channel, and the outcome when it's solved.

  • Your rules

    Owners and admins set the types, details, outcomes and deadlines for the whole organization.

Questions people ask

Does every conversation become a ticket?

No. Conversations stay conversations. Make a ticket when a request needs follow-up: a delivery problem, a refund, a warranty case.

How are deadlines counted at night and on weekends?

Only during your opening hours, in your organization's time zone, skipping the holidays you add. You can also count every hour if you work around the clock.

What happens while we wait for the customer?

Set the ticket to Waiting on customer and its deadlines pause. When the customer writes back, the clock starts again from where it stopped.

Do tickets work with every channel?

Yes. A ticket belongs to the customer's conversation, whichever channel it came from, and several conversations can share one ticket.

Keep every promise on time.

Make your first ticket in a few minutes. Your deadlines start counting right away.