Use case: payroll and HR software

Help for the screens people open once a month, on deadline

Payroll runs, declarations, year-end and leave rollover: rare, high-stakes tasks done by a business owner or an office manager, not a payroll expert. Nuri shows up in the closing window, explains the error that blocks the save, and keeps admin steps away from employees.

Deadlines

Nudges that open with the closing window

Support tickets in payroll come in waves: the days before a monthly declaration, the end of the leave year, the first payslips of January.

  • Give a nudge or a checklist a schedule: a date window, a monthly window that wraps over the month end (the 25th to the 5th), or a yearly one, in the visitor’s time zone or one you pick.
  • Show it only to admins, a plan, or users in their first weeks, with the attributes your page passes.
  • A checklist can start fresh each period, for a month-end or year-end routine people redo every time.
  • Show me starts the goal, or replays a flow you recorded once.
a nudge in Engage > Nudges
Nudge: "Payroll closes on the 5th. Want me to walk you through it?"
Goal:     Run this month's payroll
Repeat:   every month, from day 25 to day 5
Time zone: Europe/Paris
Who:      role is admin
How often: at most every 7 days
Errors

“Why can’t I save this?” answered on the spot

A refused declaration or an invalid employee record is where users give up and write to support.

  • When a form shows an error, Nuri reads the error message next to the field, points at the first field in error and says what the message means, from your help center.
  • It works with how your app already marks errors: aria-invalid, the browser’s own validation, common framework error classes, alert banners and toasts.
  • Field values are never read. When an error message repeats what the user typed, the widget sends a generic reason instead.
  • In English, French, Spanish, German and Arabic, right to left included.
Roles

Admins and employees, one app, the right help

The same product serves the person who runs payroll and the employees who request leave or download a payslip.

  • Mark help-center sources, snippets, suggested goals and recorded flows as for some roles or plans only. Nuri uses them only for those visitors.
  • List restricted areas, such as /settings/payroll: for other visitors Nuri leaves them out, never points into them, and says an administrator of their organization usually handles that.
  • Test a question as a role in the dashboard to see what that visitor would get.
  • The role comes from your page, so this keeps help relevant; it is not access control. Your app’s own permissions still decide who can do what.

When it still needs your payroll expert

The Contact support button opens your chat or help desk (Intercom, Zendesk, Crisp, HubSpot chat, Freshchat, Freshdesk, Help Scout), WhatsApp, email or your support page. In most of them the user’s goal and a summary of what Nuri tried come along, so your expert doesn’t start from zero. Your help center stays the source: Zendesk, Intercom, Freshdesk and Help Scout articles are synced every day. See integrations.

Customer success teams can turn on account tracking to see which client companies struggle during the closing window, with Slack alerts and a weekly digest: see customer success.

Not built yet

  • Resuming a long procedure on another day. A guided goal lasts for the browser tab; a user who stops halfway asks again next time.
  • A “what goes in this field?” button. Users can ask Nuri about a field in words; it answers from your help center.
  • Native mobile apps (often the employee side). Nuri works in web pages, including the web version of a staff app.
  • Dutch, Italian and Portuguese. The widget speaks English, French, Spanish, German and Arabic.

What to know before you start

  • Nuri never reads form fields or what users type into your app. The question a user asks Nuri is sent to the model, with emails and long numbers masked.
  • Mark payslip amounts, names and bank details with data-guide-private or data-guide-ignore, and they never leave the page. See security.
  • We don’t publish a deflection rate: we have no customer numbers yet, so we measure yours with you.

Ready for your next closing window?

Free for 3 months for design partners. We set it up with you; you paste one script tag.