Line of business application support helps your team use the software it relies on every day. The Support Desk assists with technical problems and routine administration. Your application expert or software vendor joins when specialized knowledge is needed. Clear documentation connects everyone so requests can move forward safely and become easier to handle together.

60-Second Summary #

• Start with the Support Desk. Tell us what is happening and how it affects your work. You do not need to diagnose the problem first.
• Routine administration is supported. Within your agreed services, we can follow documented, authorized, repeatable procedures. Appropriate access, active vendor support, and the necessary technical ability are also required.
• Choose an Application Champion and a backup. These are people who understand how your organization uses the software. They help explain the workflow and confirm that the result meets business needs.
• Build missing documentation together. We review existing records and work with your team or vendor to verify suitable procedures. We document what we learn rather than rely on memory or guesswork.
• Vendor support is a coordinated effort. We participate as your IT provider alongside an authorized client representative. Vendor charges remain separate unless included in your written scope.
• Plan broader changes. Company-wide updates, core application changes, and specialist work need scope review, appropriate approvals, and testing. Planning does not automatically make the work non-covered.

What Is Line of Business Application (LOB) Support? #

A Line of Business (LOB) application is software your organization relies on for daily operations. Organizations using these applications include manufacturers, healthcare providers, local governments, municipalities, police departments, and fire departments. They may support one function, such as point-of-sale (POS) transactions, or connect several departments through a shared platform. LOB support combines technical troubleshooting, appropriate routine administration, and coordination with application experts. Common software categories and examples include the following. Some platforms span more than one category.

Your software does not need to appear in this list for us to review a request. Industry-specific and custom-built applications also fit this broader support approach. The examples identify software types, not a guarantee that every feature or configuration is included in your services. These applications may run on a workstation, your organization’s server, or a vendor’s cloud platform. The support path depends on the specific task, hosting environment, and whether the issue involves standard functionality or a customized component. The product name alone does not determine how a request is handled.

What About SCADA and Industrial Control Systems? #

Public works, utilities, and manufacturers may also use supervisory control and data acquisition (SCADA) systems to monitor or control physical equipment. These systems are operational technology (OT), with specialized safety and reliability requirements. We can assist with agreed IT components and coordinate the system vendor or controls specialist. Changes to control logic, safety settings, or equipment behavior require the appropriate specialist and approved procedures. Supporting the connected computer does not automatically include programming or operating the equipment.

How Does Support Differ for Standard and Customized Applications? #

Standard functionality: The application’s standard, vendor-supported features and configurations follow our normal support process within your agreed services. The IT Department helps with supported infrastructure, access, and appropriate routine administration. We involve the software vendor when application-specific expertise is needed. Routine administration must be documented, authorized, repeatable, and within our technical abilities. Active vendor support and appropriate access are also required.

Customized functionality: Custom scripts, custom integrations, modified application code, and specially developed workflows can behave differently from the standard “out-of-the-box” application. Troubleshooting these components may fall under Best Effort support. Their complexity or uncertain behavior may require assistance from the software vendor, original developer, or implementation partner before changes can be made safely. We confirm who supports the customization rather than assume the application’s vendor covers every modification.

Customization does not automatically make the entire application unsupported. For example, applying an approved user role can remain a routine documented task even when repairing a custom integration requires a specialist. The specific request determines the support path. We are happy to help where we can and when a safe, useful action is available. Your Application Champion helps explain the intended workflow. We review the available documentation, assist with the supported IT components, and coordinate the appropriate vendor or specialist. Together, we can document verified procedures to make future requests more consistent and easier to resolve.

What Can the Support Desk Help With? #

Routine application administration is supported within your agreed services. It is not automatically excluded because a request involves a LOB application. The work must be documented, authorized, repeatable, and within the Support Desk’s technical abilities. Active vendor support and appropriate access are also required. We can follow approved procedures to manage users, reset access, assign licenses, and apply authorized roles. We can also install application clients or perform suitable documented settings changes and maintenance.

The word “administration” describes many different tasks. Applying an approved permission is different from deciding what that permission should allow. Following an existing workflow is different from designing how the business should operate. The examples below show how those differences affect who participates.

Our infrastructure work includes the supported servers, operating systems, storage, networks, and workstations around the application. Troubleshooting may involve authentication, shared drives, Windows services, printers, or scanners. It may also involve single sign-on, multifactor authentication, or approved network and firewall settings. Our cybersecurity work includes reviewing access and security controls within the managed environment. For vendor-hosted applications, the vendor manages its platform. We help with the supported IT components that connect to it and coordinate product-specific troubleshooting when needed. Investigating an existing connection is different from developing a new custom integration.

How Does Direct Application Access Help the IT Department? #

Direct application access can help the IT Department complete approved work with fewer interruptions to your organization. Providing it is optional. Our primary focus is infrastructure and end-user support. We do not need access to every application your organization uses.

Routine administration is supported. Within your agreed services, we can follow documented, authorized, repeatable procedures. Appropriate access, active vendor support, and the necessary technical ability are also required.

A login provides technical access. The agreed services, approved procedures, and assigned responsibilities determine how that access is used. It is not unlimited authority or an automatic expansion of services.

What Access Should Be Arranged? #

Application access, server access, and vendor authorization serve different purposes. An application login allows permitted actions inside the software. Server access concerns the supporting infrastructure. Authorization to work with the vendor allows us to communicate as your IT provider. Having one does not automatically provide the others.

• A dedicated IT-support login. Where the application and applicable requirements permit, we use a dedicated shared account identified for EasyITGuys support. Authorized technicians access its stored credentials through their individual IT Documentation platform accounts. Credential access is logged, and work is recorded in tickets for change tracking. These records support accountability but do not establish a complete history of every action inside the application.
• Permissions that match the task. Direct access does not automatically mean full administrator access. A diagnostic role may be sufficient for investigation. A user-management role may be needed for adding or removing users. This follows least privilege: providing only the permissions needed for approved work.
• Protected sign-in. Use multifactor authentication (MFA) where supported and prefer phishing-resistant methods. Approved one-time codes can be managed through the secure IT Documentation platform. Vendor-provided email verification must also meet applicable security requirements. Neither one-time codes nor email verification is phishing-resistant. Share credentials through the approved secure process, not ordinary email or unprotected ticket notes.
• Ownership and recovery. Your organization retains account ownership and an appropriate recovery path. Your Application Champion keeps the application contacts and access instructions current. We control our team’s access to stored credentials. Coordinate changes or removal of the support account when access is no longer needed.

Vendor, agency, or regulatory requirements may restrict shared accounts or limit which support personnel can access an application. A different access arrangement may be needed. Authorization, appropriate permissions, and documentation still matter for every organization, including those without industry-specific requirements.

Who Provides Instructions, and What Happens Next? #

Your authorized organizational contact approves what IT may do. Your Application Champion supplies the relevant procedures, operational requirements, and vendor information, and communicates changes. We can add approved instructions to the IT Documentation platform and help clarify straightforward support procedures. We document the work we perform, but do not independently define your application’s operating rules or assume responsibility for its entire documentation set.

1. Prepare and confirm access. Have the Application Champion or vendor confirm the intended account and permissions before sharing them when practical. IT can validate access in advance through an agreed request or when it is needed for support. Receiving credentials is not the same as testing that they work for the intended task.
2. Perform the approved routine task. Examples include adding or removing application users and applying documented, approved role changes. Where the procedure allows, we can work without your employee remaining connected. Undocumented, higher-risk, or specialized changes need additional review or vendor assistance before proceeding.
3. Record and validate the result. We record actions, findings, and any next steps in the ticket. Your affected employee or Application Champion confirms the operational result when needed. Verified repeatable instructions can then be updated for future requests.

Providing credentials alone does not initiate an application audit, recurring monitoring, extensive documentation, ongoing application-wide access reviews, or additional backup services. The login is available for agreed support tasks when needed. Responsibilities already included in your services remain unchanged.

What Happens Without Direct Application Access? #

Your organization can keep application access with its own team or vendor. We can still assist with covered infrastructure and end-user issues. Application work may require an assisted session, your Application Champion, or vendor participation. Limited Best Effort support may be appropriate for tasks outside normal support when a safe attempt is useful. Missing access does not automatically reclassify otherwise covered work as best effort. We explain what can proceed and what requires another participant.

EasyITGuys Will Not Impersonate Your Organization #

We will not impersonate a client, employee, or account owner. We identify ourselves as EasyITGuys and use an authorized IT-support identity rather than presenting ourselves as another person. We do not answer identity-verification questions or approve actions in someone else’s name.

A support login does not replace vendor-account authorization or your organization’s participation. An authorized organizational representative must join three-way vendor troubleshooting calls. The account owner completes any steps that require their identity or authority. Your Application Champion helps explain the workflow and verify the result. We contribute technical assistance and coordination within the agreed scope.

How Does an Application Request Move Forward? #

You do not need to diagnose the problem or finish documentation before contacting Support. We can begin with safe troubleshooting and review what is already known. When more information or expertise is needed, the next step should be clear.

1. Review the existing process. We check available documentation, prior tickets, approvals, and access. A suitable documented procedure can be followed once its requirements are confirmed.
2. Involve a knowledgeable client resource. When the procedure is missing or unclear, your Application Champion or IT point of contact helps explain the intended outcome. Onsite participation may be needed for local equipment or operational testing.
3. Coordinate with the vendor. When client knowledge is unavailable or specialist expertise is needed, we help arrange the appropriate vendor engagement. Three-way troubleshooting includes the Support Desk, the vendor, and an authorized client representative.
4. Validate and document. The affected user or Application Champion tests the intended operational task with IT assistance. We record the outcome and capture suitable repeatable steps for next time.

A known vendor issue or high-risk request can go directly to the appropriate specialist. The process should help the request move forward, not create unnecessary steps. When a change needs to pause, we explain what is missing and who can help provide it. Testing should match the reported issue. Opening the application is not always the same as resolving the original problem. For example, an invoice problem needs an appropriate invoice-workflow check, not only a successful login.

Who Participates in Successful Application Support? #

An Application Champion understands how your organization uses the software. Your IT point of contact, or IT POC, coordinates IT requests and organizational decisions. One person may fill both roles, but they serve different purposes. A champion does not need to be an IT expert or have authority to approve every change.

Why Is Documentation So Important? #

Good documentation lets another qualified team member follow the same process. It reduces repeated discovery and makes support less dependent on individual memory. It also helps identify when an instruction no longer matches the application. As we learn more about your operations together, useful procedures become part of a shared record rather than knowledge held by one person.

The IT Documentation platform is the shared working reference for approved procedures. Tickets record the request, approvals, actions, and outcome. Linking the two helps the next person understand both the instructions and the history. We record the technical work we perform and help capture validated steps. Your organization supplies operational knowledge and communicates changes. Shared responsibility does not mean the client must write every technical instruction. Outdated instructions need review before use. Vendor documentation can provide a starting point but organization-specific settings and approvals still matter. Store credentials through the approved secure process, not in general notes or email.

Can EasyITGuys Help Create Missing Procedures? #

Yes. We can work with you to document a reasonable, streamlined process through the IT Documentation workflow. This is different from researching an entire application or designing organizational processes. Work expected to exceed roughly one to three hours of documentation effort needs a separate scope discussion. Extensive research, process design, or consulting may need that discussion sooner. We coordinate that discussion with your IT POC, Account Management, the IT Coordinator, and the Project team. Executive participation may also be appropriate. Larger efforts are reviewed as documentation or consulting projects rather than continuing as standard Support Desk or Operations work. The time guideline concerns documentation effort. It is not a cutoff for incident troubleshooting or an automatic allowance of included consulting.

How Does This Apply to Employee Onboarding? #

We can follow the documented application setup process for supported employees. The same approach applies to new hardware, role changes, and departures. Keep application requirements and approved employee-specific setup details in the IT Documentation platform. Link them to the relevant onboarding or access-change ticket. Identify the required applications, roles, licenses, approver, and effective date. “Set them up like another employee” is a useful starting point but the intended permissions still need confirmation. Copying access without review may provide permissions the new role does not need.

How Do We Improve Recurring Requests? #

When the same issue or unanswered question returns, we can review the pattern together. IT can compare the tickets and procedures. Your Application Champion can explain the operational impact, and the vendor can help assess product-specific causes. The next improvement might be a clearer instruction, an approved configuration change, training, or planned specialist work. Agree on the next action, who will handle it, and how the result will be checked. The goal is to reduce repeated effort, not simply repeat a workaround.

How Does Three-Way Vendor Coordination Work? #

Vendor coordination brings together your organization, the Support Desk, and the software vendor. We help explain the technical findings and coordinate the appropriate next actions. Sharing existing tickets, errors, logs, and vendor instructions can reduce repeated investigation. This is a working partnership, not simply a direction to call someone else. An authorized client representative must participate in vendor troubleshooting calls. The Application Champion is usually the best person to explain the workflow and test the result. An account contact may also be needed to verify ownership or approve vendor services. Even without a champion, a client representative still needs to join. EasyITGuys participates as your IT provider, not as the account owner. Let us know when the appropriate client participant is available so we can coordinate the call.

We participate where technical coordination is useful. This can include sharing diagnostics, arranging approved vendor access, or implementing authorized infrastructure changes. Vendor recommendations still need appropriate security and change review. After sharing the technical findings, we may leave the call while your representative continues with the vendor and rejoin when further IT assistance is needed. The vendor provides its product expertise and controls its own support availability. We cannot guarantee its response or resolution timeline. For work we coordinate, the ticket should identify the vendor case, next action, responsible person or team, and follow-up plan. It should also identify anything needed from the client. Our teams coordinate their internal handoffs. You should not have to manage our support queue or repeatedly explain the same issue to move between teams.

Who Maintains Vendor Support and Pays Vendor Fees? #

Your organization maintains active licensing, subscriptions, maintenance, and vendor support for software outside the EasyITGuys-provided managed solution. Keep account contacts and support information current. We are happy to advise and assist with coordination. For software supplied within our managed solution, responsibilities follow the services identified in your agreement. Purchasing a license does not by itself include every application service. Vendor support, consulting, upgrade, and licensing fees remain the client’s responsibility unless expressly included in the written scope. Vendor coordination does not absorb those third-party charges. When additional work or charges are identified, the next step is to review the scope and obtain the applicable authorization. The vendor determines its own services and fees.

What Should You Include in a Support Request? #

Start with the application name, what you were trying to do, and what happened instead. Report the problem even when you do not have every detail. The following information helps the right people begin without unnecessary back-and-forth.

• Impact: Who is affected? Is work stopped, slowed, or still possible through a workaround?
• Evidence: Share the exact error, when it started, and a relevant screenshot without unnecessary sensitive information.
• Context: Include recent changes, previous ticket numbers, vendor case numbers, and available instructions.
• Participation: Identify the affected user, Application Champion, and when they can help with troubleshooting.

For example: “Our accounting application stopped opening at 9:15 a.m. Three users are affected. We cannot process invoices. The error screenshot is attached. Our Application Champion is available now.”

Call the Support Desk when you need help now, especially during an outage. Email or the IT Support Panel works well when immediate assistance is not needed. Keep updates in the existing ticket so the history stays together. The IT Support Ticket Process explains communication, follow-up, and escalation.

When Do Updates Need Planning or a Project? #

A workstation patch and a core application update can have very different effects. Core changes may affect the database, integrations, and every user. Even a short procedure can interrupt Organization-wide operations. A suitable client patch used during troubleshooting may fit routine support. Application-server updates, major version changes, migrations, and mass deployments need planning and scope review. Vendor participation or specialist services may be necessary. Before a broader change, confirm compatibility and vendor requirements. Identify affected systems, approvals, the installation sequence, and the maintenance window. Include recovery preparation and a way to return to the prior state when supported. Assign someone to test important operational workflows afterward. Involve IT before scheduling vendor changes to the managed environment.

Planning and billing are separate decisions. A coordinated change is not automatically a non-covered project. However, major version upgrades, server-side application updates, and mass application installations are separate from standard routine LOB assistance. These services need scope and fee review unless already expressly included in your written services. Review IT Change Management: Why Scoping and Planning Matter and Covered and Non-Covered Projects for the planning and coverage distinctions.

What About Custom Software, Database Work, and Training? #

Specialist work can include database engineering, direct data changes, custom reports, and software development. New integrations, custom scripts, data migrations, and major accounting or manufacturing configuration also need the appropriate expertise. This includes custom connections that use application programming interfaces (APIs). For customized software, we can investigate the supporting IT environment and follow suitable approved procedures. Custom or nonstandard functions may receive limited best-effort assistance when a safe attempt is appropriate. Code defects require the developer or a qualified specialist. Neither a technician’s familiarity nor a written procedure automatically makes specialist work part of routine support.

A managed server does not automatically include every database responsibility. Database integrity, performance tuning, and database-specific backup design need the appropriate specialist and documented ownership. IT can coordinate that work without assuming every database function. See Database Administration vs Managed IT. We can help coordinate a specialist from your network or the EasyITGuys Trust Network. Specialist work needs appropriate planning and may carry additional costs. For day-to-day questions, the Support Desk can assist with suitable documented procedures. Application training and decisions about how to run accounting, production, or other business processes belong with the appropriate client expert or vendor.

Does Application Support Include Backup and Recovery? #

Application support does not automatically establish backup protection for all application data. Backup coverage and recovery responsibilities need to be identified separately. A server image can protect the operating system, installed applications, and data on the included volumes. It does not automatically protect information stored elsewhere or in a vendor’s cloud service.

An application-aware image coordinates with supported software during backup when properly configured. It is not automatically the same as a native database backup strategy, such as backups created through SQL Server’s database backup functions. For critical applications, we recommend reviewing infrastructure recovery alongside application and database recovery. Additional application-specific backups may support more precise data recovery or meet vendor requirements. Start with existing backup capabilities and vendor-supported methods. Add protection where the recovery requirements justify it, rather than assuming every system needs another product.

Document what is protected, acceptable downtime and data loss, and who performs each recovery task. A successful backup or server boot does not prove that employees can complete their business tasks. The Application Champion, affected users, and vendor help validate the application with IT assistance. The following guides explain the protection and testing decisions in more detail:

• Server Backups vs Application and Database Backups
• Backup, Disaster Recovery, and Business Continuity Explained
• Backup Security and Retention: 3-2-1-1-0 Explained
• Backup Testing and Recovery Validation Explained

Frequently Asked Questions #

Does line of business application support include administration? #

Yes, routine administration is supported within the agreed scope when documented, authorized, and repeatable. Active vendor support, appropriate access, and the necessary technical ability are also needed. Designing business workflows or performing specialist work follows a different support path.

Why do we need an Application Champion when we already have IT? #

IT understands the supported technology environment. Your champion understands how your organization uses the application. Both perspectives help identify the problem and confirm a useful result. A backup champion provides continuity when the primary person is unavailable.

What if we have no documentation or knowledgeable employee? #

Contact the Support Desk anyway. We can review existing records and begin safe troubleshooting. Application-specific work may need a three-way vendor call. An authorized client representative still participates, even when the vendor supplies the missing expertise.

Why are instructions needed when IT has done this before? #

We should first review existing documentation and prior tickets rather than ask you to start over. Share an earlier ticket number when available. If we previously completed the task but did not capture the process clearly, we should review our notes and improve the documentation. Your Application Champion may still need to confirm current requirements or changes. We should use the information already available rather than ask you to recreate it.

Isn’t this only a couple of clicks? #

Sometimes it is. The important question is what those clicks change. A short action can alter permissions, production settings, or organizational records. The review should match the risk, rather than the number of clicks.

Does the one-to-three-hour guideline limit troubleshooting time? #

No. It helps identify when developing documentation needs separate scoping. It is not a general incident time limit or an automatic allowance of included consulting. Normal support follows the applicable service scope.

Does every application request get only 15 minutes of help? #

No. The up-to-15-minute best-effort guideline concerns applicable unsupported or out-of-scope requests, not routine covered application support. It does not automatically provide free work or require a minimum period of experimentation. A technician may escalate sooner when that is the safer path.

What happens if our vendor support agreement has expired? #

Application-specific assistance may be limited until vendor support is restored. We can still review the supported infrastructure and help identify next steps. Limited best-effort assistance may be appropriate, but it does not replace vendor expertise or guarantee a repair.

Do we need to stay on the vendor call? #

An appropriate client representative needs to participate so the account can be verified and the business workflow can be tested. This does not need to be the head of your organization unless their authority is required. If the right person is unavailable, tell Support so the next working session can be coordinated.

What if the vendor says the problem belongs to IT? #

Share the vendor case and findings with the Support Desk. We can compare the evidence and coordinate a joint discussion about the affected components. You should not need to decide which technical team is correct. The goal is to identify the next test or action and who will perform it.

Does involving the vendor make the entire request billable? #

No. Vendor participation alone does not determine labor coverage. The task and your selected services determine what is included. Vendor charges and separately scoped specialist work remain distinct from routine Support Desk assistance.

Can a documented update still need a project? #

Yes. Documentation does not remove organization-wide impact, downtime, or dependencies. A planned project may still be the appropriate delivery method. Project planning and whether the work is covered are separate questions.

Does a successful server backup prove our application can recover? #

No. Backup completion, server recovery, and application validation are different checks. Confirm which data is protected and which recovery tasks have been tested. Application testing should include the relevant business workflows.

You have administrator access. Why is more information or vendor assistance still needed? #

Administrator access identifies what an account can do, not which actions your organization has approved or how its workflows should operate. Routine administration remains supported when documented, authorized, repeatable, technically appropriate, and backed by active vendor support. A custom integration, missing procedure, or higher-risk change may still require your Application Champion or vendor. We use the available access to complete approved work and identify the next step, not to guess or impersonate someone else.

What should we do if a request is described as “not supported”? #

Ask which part needs a different support path and what the next action is. The gap may involve documentation, approval, access, vendor support, specialist expertise, or project scope. A useful explanation identifies what is needed to move forward, not simply what cannot be done. When expectations differ, ask your IT POC and Account Management to review the specific request, ticket history, and applicable agreement with you. We can clarify responsibilities and document the agreed next steps. For a broader process discussion, schedule time with Account Management or Mission Control / Operations so the right people can participate. Immediate technical issues should continue through the Support Desk.