Wrenfield Property Management / BB-Demo – Onboarding
Callcompleted
Wrenfield Property Management: documents · 2026-03-18 12:15
Onboarding call with Wrenfield's Head of Data and Data Analyst. Ticket and invoice data looked fine. Laura will add a fallback for older tickets missing a resident ID, then connect the call recorder export, with a walkthrough booked for the following Wednesday.
What was said
What this says
Current to 11 Oct 26Onboarding call with Wrenfield's Head of Data and Data Analyst. Ticket and invoice data looked fine. Laura will add a fallback for older tickets missing a resident ID, then connect the call recorder export, with a walkthrough booked for the following Wednesday.
What happened: Toby Cowell reviewed the ticket sample and said it looked clean, apart from older tickets with no resident ID. Laura Penhaligon will link those by block reference and date, then sign off the ticket connector.
Customer view: Hugh Fenton called the invoicing data fine and straightforward. Both customer contacts engaged and asked practical questions about effort and timing.
Commercial: This is delivery progress with no commercial signal. The customer asked how much work the next connector is for them, which suggests limited capacity to validate.
Watch: Roughly ten per cent of older tickets lack a resident ID, so the fallback link is less exact for them. The call recorder data is more structured and needs more validation.
Themes
Current to 9 Oct 26Who was there
BB-Demo
Them
Follow-up
Next steps
Current to 9 Oct 26- Laura builds the ticket fallback and signs off the ticket connector.
- Laura sends the call recorder sample with a guide by the end of the week.
Risks
Current to 9 Oct 26- Older tickets without a resident ID rely on a less exact fallback link.
- The call recorder data is more structured and needs more validation from a small customer team.
Opportunities
Transcript
Laura Penhaligon NoneToby, Hugh, how are we? Did you get a chance to look at the ticket data sample I sent?
Toby Cowell NoneYeah, we had a look. Looks pretty clean to me. One thing, some of the older tickets don't have a resident ID, just a block reference. Is that going to be a problem?- Laura Penhaligon NoneThat's helpful to know. I'll build a fallback: if resident ID is missing, we'll link by block reference and date. It's not ideal but it'll work. How many records are we talking?
- Toby Cowell NoneMaybe ten per cent of the older ones, nothing recent.
- Laura Penhaligon NoneNo drama. That's a quick fix. Once I've done that, the ticket connector is good to sign off. What about the invoicing data?
Hugh Fenton NoneThat looked fine to me. Pretty straightforward.- Laura Penhaligon NoneGreat. So this week I'm going to connect up the calls as well, your call recorder export. Similar process. I'll pull samples, you validate them, we sign off.
- Toby Cowell NoneHow much work is that on our side?
- Laura Penhaligon NoneSame as before, really. Review call, half an hour or so. The longer answer is the call recorder data is a bit more structured: timestamps, metadata, transcripts: so there's more to validate, but you know your system, you'll spot if something looks odd.
- Hugh Fenton NoneWhen will you have that ready?
- Laura Penhaligon NoneBy end of this week. I'll send it with a quick guide. Let's schedule a call for next Wednesday to walk through it.
- Toby Cowell NoneWednesday works.
- Laura Penhaligon NoneBrilliant. After that we're onto the CRM connector, that's the last one, and then we'll be straight into testing. Put it in the diary, Wednesday, same time next week. Cheers, you two.