When Rippling provisions a laptop and accounts, ChangeEngine handles the human part: the welcome, the first-week plan and the manager nudges.

Rippling brings HR, payroll, IT and device management into one platform, and is popular with fast-growing companies that hire across countries and want one employee record behind everything.
See every integration →Employee, title, department, team, work location, manager, start date, employment type, country, work email and your custom fields.
You pick the fields that sync and whether the connection is read-only or also writes approved fields back to Rippling. Sensitive fields report coverage only, never values, when your team asks an AI assistant about them.
Editors only see what their role allows, and every change is logged.
When something changes in your system of record, the right people hear about it on the right channel. Nobody on the People team presses send.
Preboarding starts as soon as the start date is in Rippling, with a welcome email and what to expect on day one.
Promotions trigger congratulations and an announcement your team approves first.
Moving teams sends the new team's channels, rituals and key links.
The new manager gets a handoff note and a prompt to set up a first one-on-one.
Work anniversaries trigger a message from their manager and an optional e-gift.
Leavers get clear last-week steps, and they drop out of every audience after their last day.
Use Rippling country and work location to send time-zone aware updates and local policy news to the people they apply to.
Every department, location and manager in Rippling becomes a live audience. New hires are in on day one, and leavers drop out on their last.
A start date in Rippling kicks off preboarding, day one and the first 90 days, with manager nudges built in.
Work anniversaries and promotions recorded in Rippling trigger a message, a manager prompt or an e-gift on the day.
Merge first name, manager, location and role into every email, Slack/Teams post and text, so a company-wide update reads like it was written for one person.
Every read and click rolls up by the Rippling fields you already track, ready for leadership without a spreadsheet.
Every person in Rippling becomes one ChangeEngine profile. Departments, locations, managers and custom fields turn into audiences you can combine, and they update on every sync.
People hired across many countries get updates in their language and local time, and contractors and employees can each get the version that applies to them.
Most teams start read-only. If you want ChangeEngine to send data back to Rippling, you approve write access for specific fields, every change is logged, and you can switch it off at any time.
Your services team runs the setup with IT. When you need something that is not in the box, your forward deployed engineer builds it.
Meet the forward deployed engineer →Your Rippling admin approves access for ChangeEngine, read-only or read and write. We send the exact permission checklist ahead of the call, so IT knows what it is signing off on.
On a working call, we map the Rippling fields you want to use: department, team, work location, manager and start date. You choose what comes across and what stays in Rippling.
Audiences fill themselves from Rippling, your first journeys switch on, and you see every person who could not be placed so you can fix the record at the source.
Your People team moves fast. Your IT team keeps control of every connection.
SOC 2 and ISO 27001. GDPR compliant, with data residency in the US, EU or Canada.
Single sign-on over SAML or OAuth, with optional two-factor authentication for editors.
SCIM provisioning, and content shown by HRIS attributes like role, location and employment type.
Employee data is encrypted in transit and at rest, and editors only see what their role allows.
Word-level audit logs, role-based editors, and AI providers contractually barred from training on your data.
Run your hub on your own subdomain, like central.yourcompany.com, with a couple of DNS records.



No. Rippling keeps provisioning apps and devices. ChangeEngine adds the communication journey around it, from the first welcome to the 90-day check-in.
Yes. Custom fields map the same way as standard ones, so you can target, personalize or trigger a program on anything your team already keeps up to date in Rippling.
Yes. Schedule a send once and it goes out in each recipient's local time.
Most teams are live with HRIS and SSO in about two weeks. IT approves the connection, we map fields with you on a call, and your audiences fill themselves.
Yes. ChangeEngine is SOC 2 and ISO 27001 certified and GDPR compliant. Data is encrypted in transit and at rest, you choose US, EU or Canadian data residency, and AI providers are contractually barred from training on your data.
Yes, if you want it to. Most teams start read-only. You can turn on write access for the specific fields you approve, every change is logged, and Rippling stays your system of record.
The ChangeEngine MCP connects the assistant your company already approved. Build audiences from this integration's data, draft a send or pull last week's read rates in plain words. A person on your team publishes every send.
Explore the ChangeEngine MCP →
Instant, policy-grounded answers in the hub and Slack/Teams.

One message, every channel, timed to each person.

Onboarding to offboarding, triggered by your HRIS.

Proof for leadership, by team, channel and program.
Bring your HRIS and your channels. We will show you your first program, built in front of you.