G2

Marnie D.

HR Systems Implementation & Workforce Compliance Lead

Retail

Mid-Market (51-1000 emp.)

10/6/2026

Business partner of the seller or seller's competitor, not included in G2 scores.

"Intuitive User Management and Segmentation for Streamlined HR Communications"

5/5

What do you like best about Cakemail?

I’m Marnie Duncan, HR Systems Implementation & Workforce Compliance Lead at Charlotte Piedmont Retail Collective LLC. We manage HR communications for our multi-location retail workforce across North Carolina. I use Cakemail to distribute mandatory policy updates, open enrollment benefits reminders, FLSA overtime notices, and store manager training announcements, while controlling internal team access to employee contact data and maintaining CCPA compliance for employee PII.

My favorite feature is the built-in user access and activity dashboard within the organization settings, which cuts roughly 6 hours of manual access auditing work every month. The Users panel seen in my screenshot displays every platform user’s email, last seen timestamp, account creation date, owner status, and active/inactive status all in one table. This visibility is critical for our retail HR team, since we have multiple store managers and junior HR staff who need limited access to employee email lists for internal communications. When I onboard a new HR coordinator to send open enrollment reminders, I can quickly add their account using the plus button, track their login activity, and deactivate their account instantly if they leave our organization. This simple control reduces the risk of unauthorized access to employee personal data and simplifies our CCPA record reviews.

The left sidebar navigation neatly organizes all core tools, separating Campaigns, Automations, Audience Building, and Settings. I use Audience Building heavily to segment our retail workforce by store location, full-time or part-time status, and salaried/hourly classification. For example, I can build a dedicated audience segment only for hourly retail staff to send FLSA overtime and time-clock policy updates, so salaried managers don’t receive irrelevant notices. The automation builder lets me schedule reminder sequences for ACA benefits open enrollment, automatically sending follow-up emails to employees who haven’t completed their benefits selection by the deadline.

I leverage the Email API and native Zapier connection to sync employee data from our Namely HCM system into Cakemail. When a new retail associate completes digital onboarding in Namely, the Zap automatically adds their work email to the correct audience group in Cakemail, removing manual list imports that used to take hours every onboarding cycle. The Senders and Domains configuration under organization profile makes domain authentication straightforward, so our critical HR policy emails reliably land in employee inboxes instead of spam folders, which is essential for our geographically spread retail teams.

An unexpected benefit I uncovered is the “Last Seen” tracking column on the Users page. During our quarterly labor compliance audits, I can quickly validate which HR team members have accessed the platform and reviewed employee contact lists, instead of manually logging every team member’s activity in separate spreadsheets. Last quarter, I spotted an inactive HR account that had not been accessed in months and deactivated it right away, lowering our employee data exposure risk before our external audit.

Suggestions for the product team: Add finer permission tiers so I can grant view-only audience access without allowing team members to export employee PII contact lists. Create pre-built email templates for HR use cases such as ACA open enrollment, FLSA notices and policy updates. Expand audit log exports to capture contact export and deletion events for CCPA and labor compliance reporting. Overall, Cakemail’s intuitive user management and audience segmentation streamline our multi-store retail HR communications and help us keep employee contact data protected. Review collected by and hosted on G2.com.

What do you dislike about Cakemail?

I’m Marnie Duncan, HR Systems Implementation & Workforce Compliance Lead at Charlotte Piedmont Retail Collective LLC. We use Cakemail to send multi-location retail workforce communications, including benefits open enrollment reminders, FLSA overtime notices, and policy updates. We need strict access controls and audit trails to satisfy CCPA, ACA, and EEOC compliance requirements for our employee PII.

The biggest pain point is the limited role-based permission structure, which creates unnecessary data privacy risk for our retail employee contact lists. The Users dashboard only offers broad admin or full-editor access tiers, there is no dedicated view-only or campaign-only permission for our store managers. When I need a regional retail manager to preview a benefits reminder email or check send stats for their store’s staff, I have to grant them full editor privileges. This lets them export the entire employee audience list containing personal emails and contact details. Last open enrollment cycle, a store manager accidentally downloaded the full contact roster and saved it locally, forcing us to complete an internal data review for CCPA compliance. There is no way to lock down audience export capability independently, so I’m forced to choose between zero access or full data export rights for every team member, which creates ongoing privacy exposure.

The second major shortfall is the lack of detailed, exportable audit logs for audience and contact actions. The Users page only shows last login timestamps, but it does not log when a user exports contact lists, deletes employee records, or modifies audience segments. When our external labor auditors request proof of who accessed employee PII for our annual CCPA review, I cannot pull a pre-built audit report from Cakemail. I must manually document every team member’s activity on a separate spreadsheet, adding roughly 7 hours of manual compliance work during each audit cycle. If my manual log has gaps, our retail group risks failing privacy record-keeping requirements.

The platform also lacks native pre-built HR email templates tailored for workforce compliance use cases. Every time I build communications for ACA open enrollment, FLSA overtime alerts, or EEOC policy updates, I start from a blank template. The generic marketing-focused templates do not include the required legal disclaimers for employee HR notices. I have to copy and paste our compliance language into every email manually, which creates risk of typos or missing required text when rushing during tight open enrollment deadlines.

Another frustrating limitation is the Zapier sync does not support real-time error alerts. We sync Namely HCM employee data into Cakemail audiences, but if the automation fails when a new retail associate is onboarded, there is no notification inside Cakemail. I only catch missing contacts when I manually check audience counts, which delayed sending mandatory new-hire policy emails to three hourly store employees earlier this year.

Suggestions for the product team: Add granular custom permission roles with toggle controls to block audience exports for non-admin users. Build comprehensive audit logs that track contact export, deletion and audience edits, with CSV exports optimized for CCPA and labor compliance audits. Create pre-built HR email templates with preloaded legal disclaimers for open enrollment, FLSA notices and policy communications. Add webhook alerts to notify admins when API or Zapier syncs fail. These fixes would resolve our biggest privacy risks and reduce the manual compliance overhead we face as a multi-store retail HR team. Review collected by and hosted on G2.com.

What problems is Cakemail solving and how is that benefiting you?

I’m Marnie Duncan, HR Systems Implementation & Workforce Compliance Lead at Charlotte Piedmont Retail Collective LLC. We manage multi-store retail locations across North Carolina, and I use Cakemail to distribute workforce communications including ACA open enrollment reminders, FLSA overtime policy updates, and new hire onboarding notices, syncing employee data from our Namely HCM platform and managing employee PII to meet CCPA, EEOC and labor audit requirements.

We struggled with scattered manual email outreach and a lack of segmented employee lists for our geographically dispersed retail workforce, but now we can build targeted audience groups and automate HR reminder sequences, which has resulted in a 32% drop in missed benefits deadlines and saves roughly 7 hours of manual list building and email follow-up work each week.

Before adopting Cakemail, our HR team relied on basic Outlook distribution lists and manual spreadsheet mail merges to send HR communications to retail staff. Our retail employees are spread across multiple store locations, mixing hourly part-time associates, full-time staff and salaried store managers. There was no simple way to separate audiences; every HR email went out to the entire workforce, so hourly associates would receive manager-only policy updates, and salaried leaders got irrelevant overtime notices. I manually copied new hire email contacts from Namely HCM into Excel spreadsheets for every onboarding cohort, which was prone to typos and missing entries. When open enrollment season rolled around, I had to manually send individual reminder emails to employees who hadn’t completed their benefit selections, and tracking who received each notice was extremely difficult. We also had no simple way to manage team access to employee contact data, and every time we prepared for external labor audits, I spent days compiling proof of who received mandatory HR notices.

Once we implemented Cakemail, our workflow changed dramatically. I build segmented audience groups by store location, employment type, and work status. For example, I create a dedicated audience for all hourly retail staff to send FLSA overtime and timekeeping policy updates, while a separate group only for store managers receives performance review training materials. The platform’s automation builder lets me schedule multi-step reminder sequences for ACA open enrollment; it automatically sends follow-up emails to employees who haven’t submitted their benefit elections by the deadline. Using Zapier and Cakemail’s Email API, new hire data from Namely HCM automatically feeds into our new-hire audience segment. When a retail associate completes digital onboarding in Namely, their email is added to the correct list automatically, eliminating manual data entry entirely.

The Users management dashboard, as shown in our screenshot, gives me a single place to add or deactivate HR team accounts and check login activity. This helps me control who can access employee contact lists, reducing the risk of unauthorized access to employee PII. When we run quarterly compliance checks, I can quickly review active platform users and lock accounts for staff who have left the retail group.

An unexpected benefit I discovered is built-in unsubscribe and deliverability management. The platform automatically adds compliant unsubscribe links to every HR email, helping us avoid spam folder placement for our workforce notices. Our mandatory policy updates now reliably reach employee inboxes instead of getting caught in email filters, which was a recurring issue with our old mail merge workflow.

Suggestions for the product team: Add granular permission controls to block audience exports for non-admin users, build full exportable audit logs for contact access and edits, create HR-focused pre-built templates for benefits and labor notices, and add alerts for failed Zapier syncs. Overall, Cakemail replaced our error-prone spreadsheet mail merge system, letting us send the right compliance communications to the correct retail employee groups, cutting down manual admin work and making our HR communications easier to track for labor audits. Review collected by and hosted on G2.com.