Web app example · a small customer support team
This helpdesk lets a customer describe a problem without first signing up, then gives them a private link for following the conversation. Agents see requests in an inbox and can sort them by whether they are open, waiting or closed.
The design lowers friction for customers while giving a small support team a shared queue. Decide what information is necessary to investigate an issue, which messages need a response first, and how a requester can recover a lost thread link.
Cleo is opening to founders in small batches. Join the waitlist and we'll save your spot.
Updated
A support inbox accepts tickets without an account, gives requesters private thread links and helps agents triage open work. Use the sample to name the audience, the main action, and the smallest useful first version. Cleo HQ then helps turn your own brief into a product plan and a working build.
Ask for a way to reply, a short description of the problem, and any details that help reproduce it, such as the page or action involved. Avoid making a customer repeat information the team can already see. The example accepts requests without an account; explain what information is private and never ask for passwords or payment details in a support message.
Choose definitions the whole team can apply consistently. “Waiting” might mean the team needs information from the customer, while “closed” should mean no further action is expected; do not use either label as a vague sign of age. The sample offers three triage states, so document when a ticket moves between them and what reopens a resolved conversation.
A private thread link lets the requester read replies without creating a password-based account. Tell them to keep the link somewhere safe and provide a support route if it is lost. The example uses private links for follow-up; avoid putting ticket content in a public address or forwarding the link to anyone who should not see the conversation.