Hires, moves and milestones in PayCaptain start the right journey for UK employers, with no lists to export and proof of who read it.
.svg)
.svg)
PayCaptain is a UK payroll platform with an employee-facing app.
See every integration →Employee, job title, department, location, manager, start date, employment type, work email, mobile number and your custom fields.
You pick the fields that sync and whether the connection is read-only or also writes approved fields back to PayCaptain. 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.
A new employee in PayCaptain starts preboarding with a welcome, first-week details and a nudge to their manager.
A promotion or new job in PayCaptain triggers congratulations and moves them into the right audiences.
Moving sites sends the new location's contacts, key links and local updates.
The new manager gets a handoff and a prompt to say hello.
Open enrollment reminders go only to eligible employees, with follow-ups to people who have not opened them.
Offboarding steps go out on schedule, and leavers drop out of every audience after their last day.
Use PayCaptain departments, locations and pay groups to send updates that feel personal, from pay-day reminders to benefits season.
Every department, location and manager in PayCaptain becomes a live audience. New hires are in on day one, and leavers drop out on their last.
A start date in PayCaptain kicks off preboarding, day one and the first 90 days, with manager nudges built in.
Work anniversaries and promotions recorded in PayCaptain 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 PayCaptain fields you already track, ready for leadership without a spreadsheet.
Every person in PayCaptain becomes one ChangeEngine profile. Departments, locations, managers and custom fields turn into audiences you can combine, like every people manager in two locations, and they update on every sync.
UK teams spread across offices, sites and remote workers get updates by site and role, in British or US English, with follow-ups to the people who did not open them.
Most teams start read-only. If you want ChangeEngine to send data back to PayCaptain, 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 PayCaptain 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 PayCaptain fields you want to use: department, location, manager and start date. You choose what comes across and what stays in PayCaptain.
Audiences fill themselves from PayCaptain, 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.
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 PayCaptain stays your system of record.
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 PayCaptain.
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. Connect your assistant to the ChangeEngine MCP and ask it to build an audience from your PayCaptain fields or pull read rates by team. It acts with your permissions, and a person publishes every send.
ChangeEngine flags people the last sync could not place, for example because of a duplicate record. Fix it in PayCaptain and they are picked up on the next sync.
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.
