Member Complaint Tickets With an Owner
Complaints about a printer, a cold cabin or a stopped lift are raised once and assigned to one person. They are closed with a note on what was done.
One complaint, one owner
One member tells the front desk, another messages the community manager and a third posts in the members’ group. Without a shared record, each assumes someone else is handling it. A ticket gives the complaint one place and one named owner. Tickets also give the owner an honest view of the building. Patterns across floors and months show where money should go before the next fit-out.
How a complaint runs
Which complaints deserve a short clock
Not every fault is equal. A member with a client due at ten cannot wait for a chair. Most centres sort into three bands when the queue is set up.
What the queue shows
Questions for your own team before launch
- Who receives complaints raised outside office hours
- Which vendors are called for which faults, and who authorises the spend
- What the member is told when a fix needs a part that will take days
Screens around this one
Agree the evidence before signing off this part.
Use a representative scenario to decide what this part of the system must show and where review is still needed.
Maintenance jobs
What proves that a planned task was actually completed?
Select an overdue entry in “Maintenance jobs”. Ask which work record closes it and what remains visible when the visit is postponed or only part of the job is done.
Background reading: ERPNext: maintenance plans
Frequently asked questions
Can members raise a complaint on WhatsApp?
They can message you there, and somebody logs it in moments. The app is more direct, because the member sees the ticket move without asking.
How do we set what is urgent?
By type. Air conditioning and internet carry a short due time, and a broken chair a longer one. You choose the times during set-up.
Does it escalate on its own?
An overdue complaint rises in the queue and can raise a reminder to the manager. There is no automatic chain of alerts to people higher up.
Can we see complaints for one centre only?
Yes. A manager reads their own building, and the owner reads centres side by side.
Is this a full helpdesk?
No. It is a ticket queue for the physical running of a centre. Phone systems, shared inboxes and chat widgets belong to dedicated helpdesk tools.
What should a ticket say when it closes?
What broke, what was done, who did it and whether a vendor came. Those four facts let the next person judge whether a repeat fault needs a bigger fix.
Can a member reopen a ticket?
Ask for this during scoping, since the answer depends on how your team wants to treat a fix the member disputes. A new ticket linked to the old one keeps the history clear.
Tell us what you need.
Share your requirements and one of our engineers will come back to you within one business day.
What happens after you share your requirements
- A senior engineer reads your answers. Nobody phones first.
- Within one business day you get a written note: what we understood, what we would start with, and the questions we still have.
- If it fits, a proposal follows with the order of work, what we need from you and what you receive at each step.
- No call is booked and nothing is paid until you have read the note. Your details stay with us.
Start with your requirements
Seven short steps that tell us what you need. A senior engineer reads them before anyone gets in touch.
Share your requirements