Operations
Help desk software for a few dozen tickets a week, built by your AI agent in your CRM
A light help desk gives every customer message a ticket with an owner, a priority and a time by which you owe a reply. This template sets up tickets, known issues that link many tickets to one cause, and a satisfaction score. Paste it into your AI agent and it builds the desk in Customermates, and you approve the plan before anything is built. It is made for a business or agency of one to eight people, not for a large support team.
No credit card required. First 14 days free.
How it works
Get a workspace
Create a free Customermates workspace with this template preselected, or use your own self-hosted instance.
Paste the prompt into your AI agent
Copy the prompt below into Claude, ChatGPT or Codex, connected to your workspace. It reads your workspace first and proposes the setup in plain words.
Approve the plan
Nothing is written until you say yes. The agent creates no sample records, sends nothing and tells you what exists when it is done.
The prompt
One self-contained prompt. Choose where your workspace runs, then copy it.
What the agent creates
Lists, fields, stages, views and dashboard widgets, as the plan your agent proposes. You can rename or drop any part.
- 5 lists
- 21 fields
- 7 views
- 9 dashboard widgets
- 8 follow-up rules
Customers
The people who write to you for help.
- Preferred channel
- Language
Accounts
The companies behind your customers, with their support plan.
- Support plan
- Contract ends
Tickets
One request for help, from first message to solved.
- Status
- Priority
- Type
- Channel
- Assigned to
- First reply due
- Solution due
- Solved on
- Satisfaction rating
Known issues
One cause behind many tickets, with its workaround and fix date.
- Status
- Workaround
- Fixed on
Actions
One dated next step per open item.
- Kind
- Status
- Due date
- Owner
- Outcome
Status
- New
- Open
- Waiting for the customer
- Waiting for a third party
- Solved
- Closed
- Spam or duplicate
Status
- Investigating
- Workaround available
- Fixed
- Will not fix
Views
- All tickets
- Ticket board
- Waiting on us
- All known issues
- All customers
- All accounts
- All actions
Dashboard
- Tickets by status
- Open tickets by priority
- Tickets waiting on us
- First replies due
- Average satisfaction rating
- Tickets by type
- Upcoming actions
- Overdue actions
- Recent activity
The weekly support review
The template builds the routine this work already has, so it keeps running after the setup.
Start with the tickets whose first reply or solution is overdue, then those that have been waiting on you for more than two days.
Nudge customers who have not answered for 3 days, and set tickets that stayed silent for 7 days to solved with a note that no reply came.
Look at reopened tickets and solved tickets without a rating, and follow up on every rating of 1 or 2.
Check the open known issues: when one is fixed, tell each customer with a linked ticket, and note the top categories of the week.
Follow-up rules
Create a reply task when a ticket is created
Automation ruleDue the same day
Notify the lead when the first reply is overdue
Automation ruleDue the same day
Nudge the customer after 3 days of waiting
Automation ruleDue the same day
Send the satisfaction survey the day after a ticket is solved
Automation ruleDue after 1 day
Close a ticket that stayed solved for 4 days
Automation ruleDue the same day
Set the solution date to 30 days out when a ticket becomes a data request
Automation ruleDue the same day
Tell the customers when a known issue is fixed
Automation ruleDue after 1 day
Create a ticket when another system sends an alert
Automation ruleDue the same day
Knowledge pages it seeds
Outlines for your own Knowledge Base, filled in with your facts. They are starting points, not finished policies.
How we run support
- Statuses and priorities
- Reply and solution targets
- Who is on duty
Triage and standard replies
- Type, priority and owner
- First reply, need more information, fixed, no response
Data requests
- Verify identity, log, answer within the statutory deadline (one month under the GDPR, 15 days under the LGPD)
- Who decides
What it does not do
Know the limits before you start.
- It is not a phone or SMS system and not a live-chat widget. Tickets come from email, WhatsApp, LinkedIn, Instagram and Telegram messages in the inbox, or from your agent.
- There is no customer portal and no public ticket form in Customermates today. Customers cannot sign in to follow a ticket.
- It does not compute business hours or holidays. Due times come from the support plan table in your knowledge base, set by a rule or by your agent.
- It is not an ITIL change or asset manager, a status page or a bulk messaging tool, and it has no SSO. Zendesk, Freshdesk or Zammad suit high-volume and enterprise support better.
- Replies are drafts you review and send. Reminders come from automation rules and notifications, or from a routine your agent runs on a schedule; the template proposes them and you decide which ones to switch on.
- Keep card numbers, passwords, ID scans and health data out of tickets. A data request keeps its identity check as a yes or no with a date, not as copies of documents.
- Connecting email or WhatsApp to the CRM needs a plan with the inbox, and a mailbox shared by the whole team needs a plan with shared accounts. The pricing page shows which plan has what.
Frequently asked questions
What is the simplest help desk for a small business?
What statuses should a support ticket have?
What response times should I promise?
How do I handle a data request that arrives as a ticket?
Can it replace Zendesk or Freshdesk?
Does the agent answer my customers?
Sources
The practice behind this template comes from these pages.
Customermates
Start your Client support desk today
Start a free trial, paste the prompt and approve the plan.
No credit card required. First 14 days free.