Skip to main content
Rise is your own HR, payroll and time-off system. Connect it once with an OAuth application in Rise, and Neo reads who is away before it routes a ticket.

​
What Neo can do with Rise People

  • Dispatch around booked leave. AI dispatch reads the confirmed time off in Rise for the days it plans, and treats a technician on leave as away on those dates, part days included. The Dispatch Ticket action reads it with no setting to turn on. An agent that uses Get Technician Context reads it when you give the agent Rise People Time Off at Read Only or more. Round Robin does not read Rise.
  • Answer who is off. Who is away today, this week or on a date, and under which policy.
  • Work time-off approvals. List the requests waiting on a manager, approve or reject them, read balances and policies, and file a request when your instructions say so.
  • Answer HR questions. Who reports to whom, which team and department someone is in, and who is onboarding.
  • Read and run Rise reports, and read payroll, when you give the agent those permission groups.

​
How dispatch finds a technician in Rise

Neo matches each person on leave to a technician by their work email in Rise, against the technician’s email in your PSA or their Microsoft 365 sign-in. With no email match, Neo uses the full name, when exactly one technician has it. Someone who matches no technician, such as office staff, is left out. Rise lists only confirmed absences: a request still waiting for approval does not block anyone. If Rise cannot be reached, the run output says that booked leave was unknown, and dispatch uses your PSA calendar alone. Your custom instructions still decide: for example, “A technician on a half day off can take remote tickets in the morning.” See Rise People API for the permission groups.

​
Next steps

Connect Rise People

Create an OAuth application in Rise and save it in Neo.