{"id":8050,"date":"2016-08-30T17:01:47","date_gmt":"2016-08-30T17:01:47","guid":{"rendered":"https:\/\/www.process.st\/templates\/the-client-onboarding-checklist\/"},"modified":"2024-02-28T18:07:26","modified_gmt":"2024-02-28T18:07:26","slug":"the-client-onboarding-checklist","status":"publish","type":"post","link":"https:\/\/www.process.st\/templates\/the-client-onboarding-checklist\/","title":{"rendered":"The Client Onboarding Checklist"},"content":{"rendered":"
\n

Foundation Elements: <\/h2>\n
\n

There are a few "first steps" that create the accounts and code you will need for other onboarding tasks.<\/p>\n<\/p><\/div>\n<\/section>\n

\n

Create a Basecamp for the client <\/h2>\n
\n

Everything we do for our clients lives inside of Basecamp.<\/p>\n

The first step is to create a new Basecamp for the client. Name it using our naming format:<\/p>\n

[Client] Client Business Name<\/p>\n<\/p><\/div>\n<\/section>\n

\n

Get the client's technical \/ website contact details <\/h2>\n
\n

Answer this question: who do you contact if you need code placed on the website?<\/p>\n

Who is in charge of changing domain names to use with Unbounce?<\/p>\n

If Gravytrain is responsible for everything, no problem. Who do we contact when we need a username and password for something?<\/p>\n

Do not proceed further until you know who the client's technical contact is. Document this person and their email\/phone in the "Docs & Files" section in the client's Basecamp.<\/h5>\n<\/p><\/div>\n<\/section>\n
\n

Get the client's branding elements <\/h2>\n
\n