A support inbox that looks the same every day
Your support queue at half nine: how do I add a second vendor to a listing, where has my viewing gone, why can't I see the Harrogate branch, the app says error, please call me. Most are from negotiators and lettings staff. Many are one line long, sent from a phone, with no screenshot and no mention of which property they mean.
Your support person replies asking which listing, waits, gets a reply after the negotiator's next viewing, then finds the answer is in a help article that was written months ago. Meanwhile a real problem, a sync failure hitting a whole agency, sits under forty how-do-I questions.
Negotiators are not ignoring you on purpose
Agency staff work on their feet. They switch between calls, viewings, portals and their CRM all day, and your product is one tab among many. A help centre that needs searching is a detour they will not take while a buyer is on hold.
- Help content lives on a separate site, written in your team's terms, not the words a negotiator would search for.
- Tickets arrive with no context, so every one starts with questions.
- Staff turnover in agencies means there are always new users who were never trained.
- Routine questions and genuine faults share one queue, sorted by arrival time.
- Nobody measures which screens generate the most confusion, so the product never changes to prevent it.
What it takes out of a small team
Support at a proptech startup is often a founder, a customer success person and whichever developer is nearest. Routine tickets eat the hours they need for onboarding and product work. Real faults are found late, and agencies on the receiving end of slow answers begin to wonder whether you are big enough to rely on. Negotiators who get stuck and give up simply go back to the old way of doing things, which shows up later as low usage at renewal.
How we build a lighter support load
What we build works on three fronts: fewer questions, better tickets, and faster answers to the routine ones.
- Contextual help on the screens that generate the most tickets: short hints and one-step guides written in agency language, such as adding a joint vendor or reassigning a viewing.
- A help button inside the product that captures the agency, branch, user, current screen, the record they have open and recent errors, and attaches them to the ticket automatically.
- A triage assistant using OpenAI or Anthropic Claude, answering only from your own help content and product documentation, and saying it does not know when the content does not cover the question.
- Routing rules: anything mentioning sync, missing listings, money or several users at once goes straight to a person, flagged as a possible fault.
- Ticket tagging by screen and topic, so each month you can see which parts of the product cause the most questions and fix the design, not just the answer.
| Ticket type | Where it goes |
|---|---|
| How do I do X | Triage assistant, from your help content |
| Cannot see a branch or record | Assistant checks permissions context, then a person |
| Listing missing from a portal | Person, flagged as possible fault |
| Rent, deposit or money question | Person, always |
| Several users reporting the same thing | Grouped and escalated as an incident |
The assistant never makes changes to agency data. It answers, links to the guide and hands over, with the conversation attached so the negotiator does not have to repeat themselves.
The queue after the change
The morning queue is shorter and each item carries its own context. The question about the second vendor was answered in the product with a two-step guide. The negotiator who cannot see the Harrogate branch was told their user is not assigned to it and who at their agency can change that. Three tickets saying listings are missing arrived within ten minutes of each other, were grouped, and your support person saw a possible incident at the top of the queue before the fourth came in.
Is this your support queue?
- Most tickets are how-do-I questions answered somewhere in your help centre.
- Your first reply to most tickets asks which listing or which branch.
- Real faults are found hours after the first report.
- You cannot say which screens cause the most tickets.
- New negotiators at existing agencies keep asking the same questions.