What was said
What this says
Current to 11 Oct 26Connection now passes after a key format fix. The first CRM load ran and the customer chose the underwriting system code as the broker key. A notes field access rule remains open, and organisation counts match but coded ones are a few short.
What happened: With the allow list added and the key format fixed, Laura Penhaligon ran the first CRM load. Organisations and contacts finished, while activities were still running.
Customer view: Siobhán Dunne worries about brokers entered three ways and said she would lose faith loudly if one broker split into three. She decided the underwriting system code is the key and asked for it to be written down.
Commercial: Trust in broker answers is the early value test for the brain. The unresolved notes field rule is a data governance point that could hold back wider use.
Watch: Coded records are a handful short in the brain against Aoife Tuohy's export, and some brokers show no last contact. Laura owes a timestamp check.
Themes
Current to 9 Oct 26Who was there
B-Brain
Them
Follow-up
Next steps
Current to 9 Oct 26- Laura to check timestamps on the missing coded records and report back.
- Laura to bring options for a notes field access model next time.
- Aoife to join the next call as helpdesk admin for the claims tickets connector.
Risks
Current to 9 Oct 26- Broker names are entered inconsistently, so a split broker could erode confidence early.
- The CRM notes field holds personal remarks and has no access rule yet.
- Coded broker counts differ slightly from the customer's export and are unexplained.
Opportunities
Current to 9 Oct 26- Joining CRM records to the underwriting code and flagging mismatches gives a visible early win on data quality.