Support

A full support desk, not just a chat fallback

An inbox and board, reply-and-set-status in one click, canned replies your team shares, and two-way email with an audit trail in every ticket. On every plan, including Free.

  1. However it starts, it's a ticket

    Chat escalation, your hosted support page, Slack, or one you log yourself for a phone call or a DM. Every path lands in the same inbox.

  2. Reply and set the status together

    Send as Waiting on customer, or Send as Resolved, in one click. Canned replies fill in the customer's details and can suggest the status for you.

  3. They get an email, you get the trail

    No portal to log into. Their reply threads back onto the ticket, and every change is recorded in the thread.

0

third-party helpdesk required

4

ways a ticket can start

5

states from Open to Closed

How it works

Everything your team needs to answer tickets

Every way in, one inbox

Chat escalation, your hosted support page, a ticket from a Slack message, and tickets you log yourself for a phone call or a DM all create the same record. Nothing to check in a second tool.

Inbox and board

Work the queue as a fast inbox with search, status tabs, date and priority filters, or switch to a board by status. Drag a ticket between columns, or open it in a side drawer without leaving the board.

Reply and set the status in one click

The send button says exactly what will happen: Send as Waiting on customer, Send as Resolved. Your last choice is remembered, and notes leave the status alone unless you choose otherwise.

Canned replies your whole team shares

Type / in the reply box, search, preview the reply with this customer's details filled in, and insert it. Keep shared replies for the team and personal ones for yourself, and let a reply suggest a status and priority. Turn any reply you wrote into a canned reply from the thread.

Two-way email, with delivery status

Your reply lands in the customer's inbox and their answer threads onto the same ticket. Each reply shows whether it was sent, and a reply that did not go out can be resent from the thread.

Internal notes stay internal

Coordinate on a ticket without the customer ever seeing it. Notes are coloured differently and have their own tab so a private note can never be mistaken for a reply.

An audit trail inside every ticket

Status and priority changes, canned replies used and ticket creation appear in the thread with who did it and when, grouped under the reply that caused them. Filter the thread to All, Replies, Notes or Events.

Built for clearing a queue

Send and go to the next ticket in the list you are working. Unsent drafts are kept per ticket, so switching tickets never costs you a half-written reply.

Roles that match a real team

Owner, Admin, Agent and Viewer. Agents answer tickets and keep personal canned replies, Admins and the Owner manage shared ones, and Viewers can read without changing anything.

Log anything that happened off-platform

A phone call, a DM, an email that landed somewhere else: create a ticket for it with the priority set, so it is tracked the same way as everything else.

Refund after 30 days?Open

Maria Santos · via email

Do you offer refunds if I cancel after 30 days?

You

Hi Maria, yes, within 45 days. I have started it for you.

  • Canned reply “Refund request received” applied
  • Status Open → Waiting on customer

Emailed to customer

Type / for canned repliesSend as Waiting on customer

Illustrative example of a ticket thread.

Common questions

Does this replace Zendesk or Intercom?

For the day-to-day work of answering customers, yes: tickets from several channels, an inbox and a board, a status and priority workflow, shared canned replies, threaded email with delivery status, internal notes and an audit trail are all built in, on every plan. It does not include ticket assignment, SLA timers, automations or live chat handoff, so if your process depends on those, a dedicated helpdesk is still the better fit.

Can my team use canned replies?

Yes. Admins and the Owner keep shared replies the whole team can use, and every agent can keep personal ones. Type / in the reply box to search and preview a reply with the customer's name and ticket details filled in. A reply can also suggest a status and priority, and any reply you have written can be saved as a canned reply from the thread.

Do customers reply by email?

Yes. Your reply goes to their inbox as a normal email, and what they send back is added to the same ticket. Each reply shows whether it was sent, and one that did not go out can be resent.

Who can see and change what?

There are four roles. Owner and Admin can do everything, including managing shared canned replies. Agents work tickets and keep their own canned replies. Viewers can read tickets but not reply or change anything.

Do tickets only come from the chatbot failing to answer?

No. Chat escalation is one way in. Tickets also come from the hosted support page, from a button in Slack, and from ones you log yourself for anything that reached you outside those, like a phone call or a DM. All of them end up in the same inbox.

Is support ticketing available on the Free plan?

Yes, on every plan, with no seat limit or ticket cap tied to it. It is not an upsell.

How do I find out when a ticket comes in?

Email, Telegram or a Slack channel, per project. You choose which to use from the dashboard's notification settings (Slack is on the paid plans). Nothing about a new ticket depends on you happening to check the dashboard.

Can a visitor reach support without using the chat widget at all?

Yes. Every project gets its own hosted support page, so someone who came looking for help directly, and never opened the chat, still has somewhere to go.

Curious how visitors reach you the other way? See lead capture →

Run support from here instead of a separate helpdesk

An inbox, a board, canned replies and two-way email, all on the Free plan from day one.

Free to start. No credit card required.