You have a help desk. Your team still DMs you.
The one you bought points at your customers. IT, HR, finance and facilities file somewhere else - chat, a project board, a shared inbox, usually more than one at once.
Your first $50 is on us.
For teams of 1 to 100,000. Nothing is charged today.
And the firms hunting hardest for a fix are the ones it is working worst for: they rate their request workflow 3.15 out of 5, against 3.91 for firms that already have a tool for it.
Curfew Labs study of 67 firms, 2026.
The tool is not the problem. Getting requests into it is.
We asked 67 firms how they track internal requests. The ones who already run a ticketing tool kept saying the same thing.
People still DM or email requests directly instead of submitting a ticket, so requirements and context get fragmented across different threads before work actually starts.
Requests often get scattered across email and chat instead of staying in the central system, making status tracking and visibility difficult across teams.
It's actually the behavior change of getting people to actually use the tool and produce actionable requests!
There is no centralized place outside of email to track the status of your tickets as a user.
Verbatim, from firms that already use a dedicated ticketing tool.
So the queue goes where the requests already are.
Every queue has its own address. Forward it-help@ to it and the next message is a ticket, with the thread and the attachments. Reply from the ticket and your answer lands in their inbox; their reply comes back to the ticket. Nobody has to learn to file one.
The actual first screen of a new queue. There is no setup wizard behind it.
Your queue already has one waiting. Nothing to configure, nothing to name.
Sender, subject and attachments intact. Replies from Curfew go back out as you, and land on the same ticket.
Each person you add is a seat. You are charged only for people you give access to.
One question: “What is your request?”
Type it and you have a ticket - routed, dated, assigned. Everything else is optional, and it is all right there when you want it.
What it does
Every request in one queue.
Email in, replies out, threaded - and anything you type yourself lands in the same place. Each queue is its own address, so support@ and billing@ stay separate without separate tools.
The right people see it, and only them.
Labels can restrict a ticket to named people, so a confidential HR request never sits in the general queue. The same labels can auto-assign as they are applied.
You see what needs you.
Five statuses, a due date, and a queue that separates what is actually actionable from what is waiting on someone else. The pile becomes a short list.
Keep the help desk you have.
This is the one your own people file into. IT, onboarding, facilities, finance - each its own queue, its own address, its own workers. Tag a ticket “New hire” and a saved checklist stamps itself, every step with its own owner, each owner added automatically. Confidential work is a label rather than a second system.
Press /
One key on every screen, two engines behind it. Type a filter and the board changes, instantly. Type a name and the ticket is right there. Ask an actual question and Alfred - Curfew's AI - takes it from you, in place, beside your work.
Nothing reaches the AI that a filter or a row could have answered exactly. The fast, deterministic path is not a fallback for the model. The model is the fallback for it.
is:overdueA token filters the list you are looking at - instant, exact, no model involved.
Only a question reaches Alfred. The ↵ lights up, and he answers in the rail beside your work.
Alfred runs as you.
He sees exactly what you see and nothing else - every lookup is re-checked against your own permissions, structurally. A restricted ticket you cannot open is one Alfred cannot read to you either.
He never acts on his own.
Anything that would change a ticket comes back as a card you approve. Alfred suggests, a person confirms.
Your first $50 is on us.
$17.00 per user, per month. Add a card to start and nothing is charged today. You pay per person you give access to — and only for the apps you actually use.
We tell you twice before the credit runs out, and again when it does.
Add or remove people any time - you are only charged for the days they have access.
Payments are processed securely by Stripe. We never see or store your card.
Common questions
What is Curfew?
A suite of business apps built on one foundation - one login, one bill. Tickets is one of them, and it works entirely on its own.
How do I sign in?
Passwordless. Enter your email and we send you a sign-in link. There is no password to create, remember or leak.
How much setup is there before we can file a ticket?
None. Type what you need and press enter. Queues, labels, checklists and templates are there when you want them, and never in the way before then.
Can we use this for internal requests, not just customers?
Yes - it is what the app was built for. Onboarding, IT, facilities and internal intake run in the same queue, and a label can stamp a saved checklist onto a ticket, owners and all.
How does this compare to the legacy help desks?
Same job, about a quarter of the price, and running in an afternoon instead of a quarter. You forward an address instead of scheduling an implementation.
Is there AI, and what does it do with our data?
Yes - Alfred answers questions about your queue in plain language. Most of what you type never reaches him: / filters and searches instantly on its own, and only a real question escalates. When it does, Alfred runs with your own permissions, so he can never surface a ticket you could not open yourself, and he never changes anything without your confirmation.
How big does this go?
Teams of 1 to 100,000. The queue, the permissions and the checklists are the same whether one person answers everything or thousands share the work.
Can I bring my existing tickets over?
Yes, with our help - import is not self-serve yet. Write to us after you sign up and we bring your history in with you.
What happens to my data if I leave?
It is yours. Ask and we run a full export of your tickets and send it to you. A self-serve download is on the roadmap, not in the product today.
Do I have to use the other Curfew apps?
No. Tickets stands alone. If you ever add another Curfew app, it shares the same login and the same bill.
When am I charged?
Not at signup. You add a card to activate the workspace, and your first $50 of usage is covered by a welcome credit - we tell you twice before it runs out, and again when it does. After that you are billed monthly in advance for the people you have given access to. Adding or removing someone mid-month is prorated to the day.
What counts as a user?
Only the people you give access to. Adding the app to your workspace is free; assigning somebody is what bills, and unassigning them stops it the same day.
Who handles payment?
Stripe. Card details go directly to Stripe and are never stored by Curfew.
Start today.
One queue, one address, and your first $50 on us.
Rest easy. It’s covered.