Notes from the technical session and next steps

Hi both, Thanks for today. Hannah has asked me to pass on a short summary so it's in writing. - The brain runs inside your own Snowflake account, so your repairs and arrears data stays where it is. - Hannah showed how repairs tickets, tenant calls and complaints get joined, and where a duplicate job can be caught before it reaches a dashboard. - She'll put the diagram and her answers to Paul's questions in writing, and she'll flag anything she needs to check before she commits to it. On our side the deal is still the Growth tier at £56,000 total value, with the target of 16 Aug 2024 for signing. Nothing has changed there, and I'll confirm the detail in the proposal. Paul, if you can share how the housing system marks a re-raised job, that would help Hannah most. Cheers, Tom

Tom, Thanks for the summary. Re-raised jobs carry the original job ref in a notes field, but not always. Roughly half the time someone types it, the rest they don't. That's why the report double-counts. So catching them in the brain only works if Hannah can match on more than the ref. Date, address and trade, probably. Can she confirm that before Helen signs anything off? Helen, shout if I've missed anything. Paul