Support that fits the size of your rollout
Discuss training, migration, rollout and support for Kurasa deployments.
What to include in your first message
Name the school or programme, the number of sites, your intended start date and the first task staff need to complete. Mention any records to migrate and who will coordinate training locally. Ask which support channel, service hours and response arrangements apply to your proposed rollout.
Scope the work around your rollout
Tell us how many schools and users are involved, what information already exists and which workflows need to come first. Include the timeline, local contacts and training needs. These details help define responsibilities for migration, configuration, onboarding and follow-up rather than leaving support expectations unclear until the rollout begins.
Agree what successful adoption looks like
A useful support plan identifies the first tasks staff should complete and how questions will be handled. Set review points to discuss participation, record quality and recurring barriers. For networks or public programmes, clarify the role of each local team and partner. Kurasa will confirm the available services and scope through discussion.