Thanks for today: demo recap and next steps

Hi Helen, Paul, Thanks for your time this afternoon. Good to see the demo running on your own repairs and arrears data rather than a canned set, and I thought the questions from both of you were spot on. A quick recap so we're all working from the same page: - You want tenant calls, repairs tickets, complaints and rent arrears in one place, so the board pack stops being stitched together by hand. - Helen's main test is whether the figures reconcile to the housing management system and whether you can see the source behind each one. - Paul wants repairs reporting he can trust before the morning stand-up. Hannah is copied in and will write up the connector side properly, including what we'd connect first and how the nightly refresh works. She'll put it in writing so you can pass it to your IT colleagues if that helps. On our side I'm pencilling in a proposal for the Growth tier. I've got the end of the proposal stage in my notes as roughly 16 Aug 2024 for a decision, but that's only a planning date, so tell me if it's wrong for you. No drama either way. One ask: could you each let me know anything from today you'd want covered in the proposal? Better I hear it now than after it's written. Leave the rest with me and let's get something in the diary for next week. Cheers, Tom Tom Ashdown Account Executive, BB-Demo

Tom, Thanks for the demo. Useful. One thing for the proposal. Repairs jobs. We have a known issue where the same job can show up more than once depending on how the job is raised and updated in the housing system. I need to know how the brain handles that. Does it count a job once or does it just take what the source gives it? Also need to know what happens to the repairs numbers if a connector fails overnight. I'd want to see that before the stand-up, not find out at ten. Can Hannah answer both in her write-up? Happy to send her a sample if it helps. Paul