Onboarding session and source access

Hi Ashok, Nice to speak after the kickoff. Here is the plan for your onboarding session, so you can see what I'm asking for before we get on a call. The aim is to get your first refresh to land cleanly, before we switch on the refresh across everything. I'd like to do it in this order: - branch orders and deliveries first - trade credit second - call recordings last What I need from your side is: - written access for each system, with a named owner, before I connect anything - the field that identifies a trade account in each system, so I can check that it maps cleanly across all of them - confirmation of who will be an admin besides you, so you aren't running this alone once I've handed over The licence covers 160 users, so we will plan the rollout in waves rather than switching everyone on at once. Only a handful of people are using it so far, which is what I'd expect at this stage. Could you reply with a couple of slots next week that suit you? I'll write up a setup note after each session so nothing lives only in my head. Thanks, Callie

Callie, Thanks, the order works for me. Access: I can have the branch orders and deliveries credentials with you by Monday. Credit needs sign-off from Gillian's team, so that may take a little longer. I'd rather not hand over anything half-approved. I'll send the call recording access last, as you suggest. One question on the account identifier: which account number is that? Our branch system and the credit system don't always carry the same one for a trade account. I know of a few cases where a builder has a different number at different branches. I'll pull a list of those so you can see them before we map anything. I'll test it on one branch first and send you a screenshot of what I see, then we can decide whether to widen it. Wednesday morning suits me for the session, or Thursday if that's better for you. Second admin: I'll check with my team and come back to you. Ashok