Member Relationship History for Coworking Teams
Calls, meetings, complaints and requests are kept as one running history for each member. A renewal discussion or a handover between managers then starts from the record.
Why history stays with the member
When a community manager leaves, the contract and invoices stay behind but the history of calls and promises does not. A replacement may not know about a waived overage or a near exit. That history stays on the member record and does not leave with the person. A good history also protects the member. They should not have to repeat a complaint to a third person or be quoted a rate that was promised otherwise last spring.
What the history holds
Reading it before a conversation
What a useful note looks like
Two lines beat two paragraphs. The next reader wants the fact, the date and what happens next.
Warning signs a manager can read
Operator guides on retention point to the first months of a membership as the risky stretch, and to quiet behaviour as the clue. A record cannot predict who will leave, but it makes these signs easy to find.
- Bookings falling over several weeks
- A complaint closed without the member agreeing
- Fewer people from the company turning up
- A payment contact who changes without notice
Related screens
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.
Reading it before a conversation
What becomes available when a booking is moved or cancelled?
Use “Reading it before a conversation” to move a booking, then cancel a second example. Check the released slot, the person or resource still assigned, and any amount left to settle before accepting the revised schedule.
Background reading: ERPNext: appointment records
Frequently asked questions
Does it record calls?
No. Nothing is recorded as audio. A team member writes two lines about what was said, which is what a colleague can use later.
Can the member see these notes?
No. Their app shows the plan, bookings, bills and whatever they raised themselves. Internal notes stay internal.
Why not keep all this with the member’s details?
Member details hold the state of things today, such as plan, seats and dues. The history holds what led there, and a renewal discussion draws on it.
Does it tell us who is about to leave?
It shows signs, such as bookings tailing off or a complaint that was never settled. Reading them is a judgement for your manager, and no score does it for them.
How much should staff write after each call?
Two lines are enough when something was decided or promised. Routine calls need no entry, and a sparse record that people trust beats a long one they skip.
Who should be allowed to read the history?
Community managers and the owner, as a rule. Front desk staff may need only recent items. Decide the list at set-up, since notes sometimes carry commercial detail.
Does the history carry over if a member moves centres?
Yes. The member keeps one record across buildings, so the new manager sees what the old one knew.
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