How onboarding works
What week one looks like
Onboarding is deliberately small. You are not migrating anything, and nothing changes inside your CMS. You issue read-only credentials, we build the picture of your estate, and outreach stays switched off until you say otherwise. Most of the effort is contact data, and that is the part only you can do.
Stage 1
day 1
Connect
We take read-only API credentials for your CMS and connect. Nodark discovers your players and starts checking them on a roughly 15-minute cycle.
From you
read-only API credentials, and a technical contact for an hour if something needs clarifying.
Stage 2
days 1–3
Build the picture
Venues get matched to addresses and opening hours. Nodark seeds hours automatically, then flags the ones that look wrong. Screens with missing addresses, missing hours or duplicate records show up on a data-quality list.
From you
a review of the flagged list. Nobody knows your odd sites better than you — the pub that opens at 4pm, the pharmacy that shuts Sundays.
Stage 3
days 3–7
Watch, silently
Monitoring runs with all outreach off. You see which screens are dark, which flap daily, and which have been off for a month. For most operators this week is the uncomfortable one. It is also the most useful.
From you
nothing. Just look at it.
Stage 4
end of week one, or later
Turn on outreach
Outreach is enabled client by client, not estate-wide. Pick one client to start with. Supply venue contact names and mobiles for those sites, agree the response windows, and confirm who on your team approves callouts.
From you
venue contacts for the first client, agreed response times, and named approvers. Then you decide when to add the next client.