Admin WalkthroughScreen by screen
Every screen you’ll touch as a Lollipop admin — what it does, where to find it, and what to watch for. Coral rings in the screenshots mark the control to act on.
Your Customer Success contact handles most of the initial setup with you. This guide is for afterwards: changing a send time, adding someone who joined, fixing a bounced email, checking how the month is going.
Setup (steps 1–7) is what gets configured before launch. Running it (steps 8–13) is what you’ll come back to month after month. Skip to whichever you need.
| To do this | Go here |
|---|---|
| Upload your roster | Employees › Imports |
| Add one person | Employees › Add Employee |
| Change when check-ins send | Teams › Delivery Schedules |
| Change who gets alerts | Settings › Configuration |
| Email, SMS or Slack | Settings › Check Ins |
| Fix a bounced address | Super Admin › Invalid Users |
| See who opted out | Super Admin › Unsubscribed Users |
Keep the company Inactive until your launch date. Switching to Active immediately emails every admin and supervisor a "set up your password" notice — so do all your setup first, then flip the switch.
Admin WalkthroughSetup · before launch
Confirm your name, address, and Time Zone. The time zone defaults to Pacific and is the master clock for every send, so set it before anything else. The red banner and the Inactive / Active toggle at the bottom confirm automations are off while you build.

Choose how check-ins reach people — Email, SMS, and Offer Follow-Up. Leave Follow-Up on so someone having a hard day can ask for a manager conversation. These are company-wide settings, not per team.

Admin WalkthroughDownload the sample template, match it exactly, then attach your file before clicking Upload — the button won’t prompt you for one. A CSV Import Report emails back from noreply@lollipopco.co listing any rows that failed and why.

| Column | Required | What to put in it |
|---|---|---|
| Team | Required | Drives grouping and who gets the alerts. |
| First / Last name | Required | Real names — the program is not anonymous. |
| Company Admin | Required | Yes or No. Yes grants full admin access. |
| Team Role | Required | Must read employee or supervisor — lowercase. |
| Email and/or Phone | At least one | Either will do. Phone enables SMS check-ins. |
| ID · Title · Location · Dept | Optional | Improves your reporting and segmentation. |
Admin WalkthroughSetup · before launch
Seven things cause nearly every failed row. The import report names the row and the reason, so work down this list against what it tells you.
| What went wrong | How to fix it |
|---|---|
| Phone format | Must match the template exactly — (555) 123-4567, parentheses and dashes. The most common failure by a distance. Excel reformats numbers on its own, so check after saving. |
| Team Role says "user" | It must read employee or supervisor, lowercase. Rows with "user" fail silently. |
| Instruction rows left in | The template’s first two rows are instructions, not data. Delete them so the headers read correctly. |
| Blank rows | Any empty row breaks the import. Check the bottom of the sheet, where Excel leaves phantom rows after you delete people. |
| Supervisor on several teams | They need one row per team. That’s how the supervisor structure works. |
| Duplicate emails | Each person appears once. A supervisor doesn’t need a second row to also be an employee. |
| Upload clicked too early | Attach the file first — the button doesn’t prompt you for one. |
If you’re on Slack, delete the phone columns entirely before uploading — delivery goes through the bot, and it removes the biggest source of failures at a stroke. And re-uploading is safe: it adds and updates without deleting anyone, so fix the flagged rows and run it again as many times as you need.
Admin WalkthroughAfter the upload, confirm every team has its supervisors and that the employee counts match your roster. A red ✗ in the Supervisor or Employee column flags a team with no coverage. Use Add Team for anything the sheet didn’t create.

For one or two people joining, add them here rather than re-uploading the whole roster. Set their System Role and Company Role, then Save.

Admin WalkthroughSet send days and times per team — there’s no bulk option, so repeat for each one. Toggle the days on, pick the time, Save. Three to four times a week is the recommended cadence.

Decide what HR, Admin, and Supervisor each see and receive — responses, trigger words, follow-ups, and notifications. Then Save Configuration.

Admin WalkthroughRunning it · month to month
Totals for the whole account: Employees, Admins, Supervisors, Unsubscribed, Invalid, Inactive, and Teams. Right after an upload, use it to check the numbers reconcile to your roster.

Once you’re live, the Engagement and Average Mood gauges headline the dashboard. Set the date filter to the current month first — it’s the single most common source of confusing numbers.

Admin WalkthroughOptionally reward participation. A common approach is three $25 gift cards a month, drawn at random from everyone who checked in. Lollipop doesn’t fulfill prizes — you run and fund the incentive in-house.

Add words that escalate a check-in immediately — self-harm language, harassment, safety concerns — so the right people are alerted the moment they appear. Use + New Word to manage the list.

Admin WalkthroughInactive and unsubscribed people are excluded from the engagement rate. It’s measured against those who can actually receive and answer a check-in, so opt-outs don’t drag your number down.
Addresses and numbers that bounced land here with an Invalid at timestamp. Correct the contact detail and click Re-Activate. Worth checking in the first 48 hours after launch, when most bounces surface.

People who opted out, usually by replying STOP to an SMS. They stop receiving check-ins and leave the engagement denominator. Around 5% is normal; a sudden spike is worth a conversation.

Admin WalkthroughIf you deliver by Slack
Check-ins arrive as a Slack message from the Lollipop bot instead of by email or text. Your Slack admin authorizes the app once, the same as any other Slack integration.
Your Slack workspace admin installs and authorizes the Lollipop app. Once connected, check-ins route through the bot.

No phone numbers to collect or format, which removes the largest source of import errors. Accounts set to Spanish get Spanish bot messages automatically. We still upload the roster manually rather than pulling in every Slack user, so you keep control of who’s in scope.
Slack delivery is company-wide, like the other channel settings — it isn’t set per team.
Admin WalkthroughKeep this page
| Question | Answer |
|---|---|
| Someone joined. Do I re-upload? | No — use Employees › Add Employee for one or two. Re-upload for five or more. |
| Will re-uploading delete people? | No. It adds and updates. Nobody is removed by an upload. |
| Someone left. | Delete them — which deactivates rather than erases. They move to the Inactive list and leave the engagement count. |
| Making someone an admin | Edit their existing row and set Company Admin to Yes. Never add a second record — it fails on duplicate email. |
| Do supervisors still check in? | Yes. One row, role supervisor. They don’t need a second row as an employee. |
| Changing a send time | Teams › Delivery Schedules, per team. There’s no bulk edit. |
| Teams in other time zones | The zone is company-wide, so offset each team’s clock time to hit its local window. |
| Where’s my import report? | Emailed from noreply@lollipopco.co after every upload, listing failed rows and why. |
| Engagement looks wrong | Check the date filter first. Then remember inactive and unsubscribed people are excluded from the calculation. |
| Someone isn’t getting check-ins | Look in Super Admin › Invalid Users — a bounced address or number lands there with a timestamp. |
The Admin Help Center in your portal answers these and about thirty more, searchable. Anything it doesn’t cover, email your Lollipop contact — we’d rather hear from you early than have you work around something.