Find the right tickets
Create and search requests, then filter by status, priority or type. Lists and a board help organise open, resolved and overdue requests.
SolveITUsed internally · introduction by agreement
Service desk & shared ticket workflows
Resolve requests together.
Understand the history.
SolveIT brings service requests, ownership and replies into a shared workspace. Support teams and connected agents work on the same ticket, with internal notes kept separate from replies to requesters.
- 01Capture the request
- 02Assign responsibility
- 03Record the answer & resolution
An example of shared ticket work. Intake channels, roles and connected applications are configured around your team.
For internal IT teams, service departments and companies handling recurring support requests. Especially useful when requests move between inboxes, chats and individual people.
What you can build on.
Make ownership visible
Manage responsibility, priority and due dates on the record. The activity history keeps changes and next steps traceable.
Replies and internal notes
Keep requester communication separate from internal coordination. Team members can continue from the existing history without collecting the context again.
Roles for each task
Administrators, support staff and requesters have different responsibilities and access. We review the customer groups and organisational boundaries required before use.
Connect agents through the API
Individual, revocable access preserves attribution. Agents can work on tickets; competing changes are checked against the current record version.
Requests from applications
An embedded support widget and application reports can attach page context to a request. Each connection and its permitted data are configured and tested separately.
Implemented scope. Your introduction.
Already implemented
- Tickets, lists, board, replies, internal notes and an activity history.
- Roles, a documented REST API and separate agent and application access.
- Internal use at NeuroFunken; customer operations and specific integrations are introduced separately.
Agreed before introduction
- Intake channels, required roles and organisational boundaries.
- Email connections, notifications, deadlines and other required workflows.
- Migration, infrastructure, backups, retention and support scope.
We agree installation, access design, migration and support for your use case. Internal use at NeuroFunken does not mean a customer instance is already configured. The individual offer defines licence, operating arrangements and service scope.
Start with a defined scope.
- 01
Understand the task
Walk through a real workflow, your users and current systems. Identify the needed functions, permissions and data.
- 02
Agree and test a pilot
Agree scope, costs, responsibilities and acceptance criteria. Test migration and integrations using suitable sample data before regular operation.
- 03
Handover and operations
Introduce the team to the agreed workflow. Document access, responsibilities and operating arrangements; commission ongoing support as needed.
SUPPORT FOR YOUR PROJECT
Plan the right introduction.
No blanket subscription or fixed implementation price is promised here. We quote the product introduction, integrations and operations against the agreed scope.
Request an introduction- Plan integrations
Data flows and responsibilities between your systems.
- Choose operating arrangements
Infrastructure, backups and ongoing support with a defined scope.
Questions about SolveIT
Can I book SolveIT immediately through public self-service?
Introduction currently starts with a discussion. We review your support workflow and agree deployment, operations and costs. A contact request or product discussion does not create a paid instance.
Do agents resolve tickets automatically?
SolveIT provides ticket workflows and API access. Access alone does not start an agent runtime. Allowed tasks, required questions and human decisions are explicitly defined for the connected agent.
Is every customer organisation automatically isolated?
Roles and application assignments alone do not demonstrate complete tenant separation. Before serving several customers, we review visibility, data storage and permissions for the intended operating model.
Are email, remote support and all integrations included?
Required channels and integrations belong in the agreed scope. An existing API or widget does not replace a configured connection. Remote support also needs the approved workflow of the application concerned.