Internal tools template
Replydesk
For a support team of a few agents and a lead. Cool blues and clear numbers, with internal notes tinted apart from replies so nobody sends one to a customer by mistake.
Opens the prompt in Crisp so you can change it before the build starts.
The look: Harbor.
Calm and trustworthy: cool blues, clear numbers, lots of air. Headings in Inter Tight, text in Inter.
- background
- surface
- foreground
- primary
- accent
- Opening
- split: the promise and two actions on the left, a real preview of the product with its data on the right, in a framed window
- Sections
- calm bands that alternate background and card, a row of three numbers that matter, a feature list with the product beside it
- Motion
- reveal on each section, cards that appear one after another on card grids
- Texture
- none
The screens.
- 01Inbox
- 02Ticket
- 03Customers
- 04Customer detail
- 05Saved replies
- 06Reports
- 07Settings
Build a shared support inbox for my team called Replydesk. Customers write in through a contact form or by email, and four agents answer them. A lead assigns tickets and watches response times. Records: tickets (number, subject, customer, channel: form or email, status: new, open, waiting on customer, solved, priority, assignee, tags, created at, first reply at), messages (ticket, from customer or agent, body, internal note or not, sent at), customers (name, email, company, tickets so far) and saved replies (title, body). Screens. Inbox: a page header with a one-line summary, stat cards for open tickets, unassigned, median first reply time today and solved this week, then the ticket list with views for Mine, Unassigned, Waiting and All, oldest first. Then the ticket page: the conversation as a thread, internal notes in a different tint, a reply box with saved replies, and a side panel with the customer, status, priority, assignee and tags. Then customers and a customer page with their past tickets, saved replies, a public contact form, a reports page with tickets per day and replies per agent, and settings. Roles: lead and agent; agents see every ticket, but only the lead changes settings. Reply emails are stored until an email key is added. Seed fifty tickets over two weeks from twenty customers, in every status, with full threads.Use this template
What Crisp builds from it
- Tickets from a public form or email in one inbox
- Threads with internal notes and saved replies
- Views for mine, unassigned and waiting
- Reports of tickets per day and replies per agent
- Lead and agent roles
Change the name, the town and the details to yours before you start. How a build works.
More internal tools templates.
- Signoff Desk
Purchase and travel requests that move through sign-off in steps
- Shelfcount
Stock levels, counts and reorders for one warehouse and three shops
- Firstweek
Every new starter checklist in one place, with the right task for each person