Purpose
The purpose of this answer is to help clients understand how support, consultation, project work, billing, vendor coordination, and follow up are generally handled.
Technology issues can vary widely, so service expectations should be clear without promising immediate resolution or guaranteed outcomes.
General Service Standard
PrismTechTx LLC reviews each request based on the information provided, the type of issue, urgency, complexity, client availability, vendor involvement, service availability, and whether the request requires support, consultation, billing review, remote support, onsite service, or project handling.
Not every request can be resolved immediately.
Some requests may require:
Additional information
Remote support
Onsite service
Vendor support
Estimate or quote approval
Payment or billing review
Project planning
Security review
Follow up after testing or confirmation
Support Requests
Support requests are used for troubleshooting, technical assistance, device issues, software issues, account issues, network issues, printer issues, and general technology problems.
A support request may involve:
Reviewing the issue
Asking clarifying questions
Troubleshooting remotely
Scheduling service
Coordinating with a vendor
Providing guidance
Leaving the ticket pending while waiting for confirmation
Some support issues may turn into project work if the request becomes larger than a single troubleshooting action.
Consultation Requests
Consultation requests are used when the client needs guidance, service review, pricing, planning, or help deciding the right next step.
A consultation may be needed for:
New client inquiries
Website or online presence requests
Network improvements
Device replacement planning
Backup and recovery planning
Security hardening
Project scoping
Vendor or product guidance
A consultation does not always mean work can begin immediately.
Some consultations may lead to an estimate, quote, project, support ticket, or referral to a vendor.
Project Work
Project work is used when a request involves planning, multiple steps, scheduling, procurement, vendor coordination, implementation, documentation, testing, or handoff.
Examples may include:
Website development or redesign
Network or WiFi improvement
Multi-device setup
Backup planning and implementation
Security hardening
Device migration
Business system setup
Domain, DNS, hosting, or email changes
Project work may require a quote, estimate, deposit, payment, approval, timeline review, or scheduled implementation.
Remote Support
Remote support may be used when the issue can reasonably be reviewed without an onsite visit.
Remote support may be appropriate for:
Software troubleshooting
Email setup
Account settings
Browser issues
Remote diagnostics
Website or platform review
Suspicious email review
User guidance
Remote support may not be appropriate for:
Cabling
Hardware replacement
Physical installation
WiFi coverage testing
Network equipment placement
Device issues where internet access is not working
Situations where remote access is unsafe
Remote support requires client permission and may require the client to be present during the session.
Onsite Service
Onsite service may be needed when work requires physical access, inspection, installation, cabling, equipment placement, or hands-on troubleshooting.
Onsite service may be appropriate for:
Printer or scanner physical setup
Network equipment installation
WiFi coverage review
Hardware replacement
Cabling or device placement
Multiple device setup
Physical inspection
Onsite work may require scheduling, availability confirmation, travel consideration, estimate review, or project handling.
Vendor-Dependent Issues
Some issues depend on third-party providers.
Examples include:
Internet service provider
Domain registrar
DNS provider
Hosting provider
Email provider
Software vendor
Licensing provider
Hardware manufacturer
Warranty provider
Payment processor
When a vendor is involved, resolution may depend on that vendor’s access, response time, support process, approval requirements, or service limitations.
PrismTechTx LLC may assist with vendor coordination when appropriate, but vendor response times and outcomes are not fully controlled by PrismTechTx LLC.
Billing and Estimates
Some requests may require an estimate, quote, invoice, approval, deposit, or payment before work begins.
Billing or estimate review may apply when:
The request is larger than routine support
Project work is involved
Website work is requested
Hardware, software, licensing, subscription, or vendor cost is involved
Onsite service is needed
Procurement is required
Work requires approval before proceeding
The scope is not yet clear
Hardware, software, subscriptions, licensing, hosting, domain, vendor, shipping, travel, rush service, after-hours service, holiday service, or other third-party costs may be separate from service labor.
Rush Service
Rush service means a client is requesting faster than normal handling or service outside standard availability.
Rush service does not automatically guarantee immediate service, same-day service, after-hours service, or emergency response.
Rush requests are reviewed based on:
Availability
Request type
Urgency
Existing workload
Client impact
Vendor dependencies
Whether the request can be safely handled quickly
Rush, priority, evening, weekend, holiday, or after-hours service may involve additional cost if accepted.
Business Hours and Availability
Security Concerns
Security-related issues may require careful review before normal support continues.
Examples include:
Suspicious email
Possible phishing
Possible scam
Malware concern
Account compromise
Unknown remote access tool
Suspicious invoice
Payment redirection
Unauthorized login
Business email compromise concern
When a security concern exists, the safest first step may be to stop interacting with the suspicious item and request review before clicking, replying, paying, approving, or entering information.
Information Needed From Clients
Clients can help move requests forward by providing clear information.
Helpful details include:
What happened
When it started
What device, account, software, or service is involved
Any error message
Screenshots, when safe
Whether the issue affects one person or multiple people
Whether anything changed recently
Whether the issue is urgent
Whether a vendor is involved
Whether a suspicious message, link, attachment, or caller was involved
Incomplete information may delay review or require follow-up questions.
Client Availability
Some requests require the client to be available.
Client availability may be needed for:
Remote support
Onsite service
Account sign-in
MFA approval
Vendor authorization
Testing
Scheduling
Project review
Final confirmation
If the client is unavailable, the ticket may remain pending until the next action can be completed.
Follow Up
Some tickets are placed in a pending status while waiting for a response, confirmation, vendor update, payment, approval, scheduled time, or future review.
Follow up may be needed when:
More information is required
Client testing is needed
Vendor response is pending
Payment or approval is pending
A fix needs confirmation
Another appointment is needed
Security review requires monitoring
If no response is received after reasonable follow up, the request may be closed or marked as no longer needing action.
Resolution Expectations
PrismTechTx LLC works to provide practical, reliable support, but technology issues may depend on factors outside direct control.
Resolution may be affected by:
Device condition
Vendor limitations
Account access
Internet service
Hardware failure
Software bugs
Security compromise
Licensing restrictions
Missing information
Unsupported systems
Client availability
Third-party response
No service response, support session, review, or recommendation should be understood as a guarantee that every issue can be fully resolved.
Client Communication
Client communication should remain clear and direct.
Depending on the request, clients may receive:
Clarifying questions
Scheduling options
Remote support instructions
Status updates
Vendor dependency updates
Estimate or quote information
Follow-up requests
Closeout summaries
Clients should avoid sending passwords, recovery codes, payment card numbers, or unnecessary sensitive information through email, text, or ticket replies.
Service Completion
A request may be considered complete when:
The issue is resolved
Requested guidance was provided
The client confirms no further help is needed
The request was moved to another service path, such as consultation, billing review, vendor coordination, security review, or project handling
The request was declined or canceled
The request is out of scope
The client does not respond after reasonable follow up
No further action is available or appropriate
Related Answers
Use these related answers when needed:
How to Request Support
Preparing for a Remote Support Session
Rush Service Explanation
Basic Scam Safety Guidance
Business Hours and Response Expectations