Automated Sendible Client Onboarding Checklist
When a new client is added, WebRun opens Sendible, works through connecting their social profiles and priority inbox settings, adds their first week of scheduled posts to Google Calendar, and notifies the account team in Microsoft Teams once setup is complete.
How do I onboard a new client in Sendible quickly and consistently?
WebRun sets up a new client's Sendible workspace as soon as they're added, connecting their social profiles and approval settings, blocking out their first week on Google Calendar, and notifying the account team in Microsoft Teams once it's done. It never publishes a client's posts itself, keeping that decision with your team.
- Every new client gets the same consistent setup, nothing skipped
- The first week's calendar is blocked out before the client's first post
- The account team knows setup is done without asking
Built for Social media agencies · account managers · marketing consultants · PR firms
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.sendible.comin a real browser with your saved login - no setup, no API keys. -
1
Sendible - connect the new client's profiles
WebRun opens Sendible to connect the new client's profiles. - Open Sendible and create a new client workspace
- Connect each of the client's social profiles
- Set up their priority inbox and approval settings
Done when Every profile for the new client is connected with approval settings in place.
-
2
Google Calendar - schedule their first week
WebRun opens Google Calendar to schedule their first week. - Open the client's content calendar
- Add placeholders for the first week of scheduled posts
- Flag any day that still needs content confirmed
Done when The first week has a placeholder scheduled for every planned post.
-
3
Microsoft Teams - notify the account team
WebRun opens Microsoft Teams to notify the account team. - Post a checklist confirming which setup steps are complete
- Notify the account manager assigned to the client
- Flag any step that still needs manual follow-up
Done when The account team has confirmation that setup is complete or knows what's outstanding.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does WebRun post content for the new client right away?
No. It only sets up the connections and blocks out a first-week calendar. Writing and approving the actual posts is still done by your team.
What if a client profile fails to connect?
That step gets flagged in the Teams checklist as outstanding, so the account manager knows exactly what still needs manual attention.
Does this replace talking to the client about their content plan?
No. It handles the technical setup so your team can spend that first conversation on strategy instead of connecting accounts.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.