Governance and collaboration

Internal requests and issue reports

ArkanERP Requests and Issue Reports gathers service requests and problem reports between a business's staff and sections in one place. Each request goes to its section's team and is assigned to a member, its response and resolution times are counted in working hours by priority, and a late one is escalated to the team leader and managers.

  • Fields of each request type's own
  • Response and resolution times in working hours
  • Automatic assignment to team members
  • Internal notes the requester doesn't see

What Requests and issue reports does

  • Types and categories

    Each type (a service request or an issue report) has its category, its own fields, required attachments, who may file it, whether it is confidential, and the record it is about.

  • Approval before work

    A type that needs approval goes through its flow first and closes if refused.

  • Assignment

    A request goes to its type's team in the company, then to the least busy member, the next in turn, a named person, a member at the requester's branch, or the team leader to assign.

  • Service times

    A response time and a resolution time per priority, counted in working hours without the weekend and the company's holidays. Putting a request on hold stops the clock and adds the time held.

  • Working and closing

    A request is taken, started, held for information, moved to another team or reprioritised, and isn't done before its type's checklist. The requester confirms and rates it, or refuses the result and sends it back, and may reopen it within the days allowed.

  • The conversation in the request

    Messages, files and @mentions, internal team notes the requester doesn't see, and every movement as its own line.

  • Converting and merging

    A request's type can be changed, it can become a financial request with its data and files, be merged into a duplicate, or have parts split off as requests of their own.

  • Escalation and auto-closing

    A request not answered or done in time is escalated to the team leader and managers, and one done but not confirmed closes after the set days.

  • My Services for everyone

    One page where any employee files a request, an issue or a financial request, follows their own, and sees what waits for their approval, with counts.

  • Ready catalogues

    Ready sections and request types, as businesses already work them, can be imported; you pick what fits and what exists stays as it is.

How the work flows

  1. 1

    Filing

    The employee picks the type, fills its fields and attaches files.

  2. 2

    Approval

    If the type needs approval, it goes through its flow first.

  3. 3

    Assignment

    The request is assigned to a team member and the response clock starts.

  4. 4

    Work

    The member works it and talks with the requester; it is escalated if late.

  5. 5

    Closing

    The requester confirms and rates it, or sends it back.

Questions about Requests and issue reports

Which sections is it for?

Any internal section: IT, maintenance, HR, purchasing and others. Each section has its team, its request types and their fields.

How are response and resolution times counted?

In working hours by the request's priority, leaving out the weekend and the company's holidays when set, and the count stops while the request is on hold.

Does the requester see the team's notes?

No. Internal notes are for the team only; the requester sees the messages meant for them and their request's movements.

Can a request become a financial request?

Yes. It becomes a financial request with its data and files and follows the financial approval flow through to payment.

Are requests assigned automatically?

Yes, by the team's rule: the least busy member, the next in turn, a member at the requester's branch or a named person, or left to the team leader.