Business Hours and Response Expectations

    Purpose

    The purpose of this answer is to help clients understand when requests are normally reviewed, what can affect response time, and why some requests may require scheduling, follow up, vendor coordination, estimate review, or project planning before work can begin.

    General Response Standard

    PrismTechTx LLC reviews requests based on the type of issue, urgency, complexity, client availability, vendor involvement, existing workload, and whether the request requires remote support, onsite service, billing review, security review, or project handling.

    Submitting a request does not guarantee immediate service or immediate resolution.

    Some requests can be handled quickly.

    Other requests may require:

    • Clarifying questions

    • Remote support scheduling

    • Onsite scheduling

    • Vendor coordination

    • Estimate or quote approval

    • Billing review

    • Project planning

    • Security review

    • Follow up after testing or confirmation

    Business Hours

    Standard service is provided during normal business hours.

    Recognized holidays are outside standard service availability unless prior arrangements are made.

    Requests submitted outside normal business hours may not be reviewed until the next available business period unless a separate arrangement has been made.

    Do not assume evening, weekend, holiday, rush, priority, or after-hours support is available unless it has been confirmed.

    After-Hours Requests

    Evening, weekend, holiday, rush, priority, or after-hours requests may be reviewed when available, but response is not guaranteed unless a specific service arrangement exists or the request has been accepted.

    After-hours service may depend on:

    • Availability

    • Request type

    • Urgency

    • Existing workload

    • Client impact

    • Remote support possibility

    • Onsite requirements

    • Vendor dependency

    • Billing or approval requirements

    Evening, weekend, holiday, rush, priority, or after-hours work may require separate approval and may be billed at the applicable expedited or after-hours rate.

    Rush Requests

    Rush service means the client is requesting faster than normal handling.

    Rush service does not automatically guarantee:

    • Immediate response

    • Same-day service

    • Evening, weekend, holiday, or after-hours service

    • Emergency response

    • Guaranteed resolution

    • Faster vendor response

    Rush requests are reviewed case by case based on availability, request type, urgency, impact, safety, client availability, and whether the work can be handled within the requested timeframe.

    Use the Rush Service Explanation answer for more detail.

    Security Concerns

    Security concerns may need 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

    If a security concern is involved, the safest first step is usually to stop interacting with the suspicious item and request review before clicking, replying, paying, approving, or entering information.

    Vendor-Dependent Requests

    Some requests 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, response and resolution may depend on that vendor’s process, access requirements, response time, support availability, and service limitations.

    PrismTechTx LLC may assist with vendor coordination when appropriate, but vendor timelines are not fully controlled by PrismTechTx LLC.

    Remote Support Scheduling

    Remote support may require the client to be available during the session.

    Before a remote session, the client may need to:

    • Confirm the device being accessed

    • Approve the remote support session

    • Stay available during the session

    • Save open work

    • Close unrelated sensitive information

    • Avoid sending passwords through email or ticket replies

    Remote support may need to be scheduled based on client availability and PrismTechTx LLC availability.

    Onsite Service Scheduling

    Onsite service may require scheduling in advance.

    Onsite work may be needed for:

    • Physical installation

    • Cabling

    • Hardware replacement

    • Printer or scanner setup

    • Network equipment placement

    • WiFi coverage review

    • Device setup requiring hands-on work

    Onsite scheduling may depend on location, availability, scope, travel considerations, required equipment, and whether an estimate or approval is needed first.

    Project Scheduling

    Project work may require planning before implementation begins.

    Project work 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 timelines may depend on approval, payment, procurement, vendor response, client content, scheduling, testing, and handoff requirements.

    Billing and Estimate Review

    Some requests may require billing, estimate, quote, approval, deposit, or payment review before work begins.

    This may apply when:

    • The request is larger than routine support

    • Website work is requested

    • Project work is involved

    • Hardware, software, licensing, subscription, vendor, travel, rush, after-hours, holiday, or third-party cost is involved

    • Onsite service is needed

    • Procurement is required

    • Client approval is needed before proceeding

    • Payment is required before work begins

    Requests requiring billing or estimate review may take longer than routine support requests.

    What Can Delay a Response or Resolution

    Response or resolution may be delayed by:

    • Missing information

    • Client availability

    • Vendor response time

    • Hardware or software availability

    • Account access issues

    • Payment or approval requirements

    • Scheduling constraints

    • Security review needs

    • Scope uncertainty

    • Unsupported systems

    • Internet or service outages

    • Required onsite work

    • Existing workload

    Providing complete information at the beginning of the request can help reduce avoidable delays.

    Helpful Information to Include

    When submitting a request, include:

    • Name

    • Business or organization, when applicable

    • Best contact method

    • Brief description of the issue

    • Device, account, software, website, or service involved

    • Error message or screenshot, when available

    • When the issue started

    • Whether the issue is constant or intermittent

    • Whether one person or multiple people are affected

    • Whether there is a deadline

    • Whether a suspicious message, scam, malware, or account compromise may be involved

    • Availability for remote or onsite support

    Response Expectation Language

    Use this expectation for client-facing language:

    Requests are reviewed based on the type of issue, urgency, complexity, availability, business hours, holiday schedules, and whether vendor, billing, security, remote support, onsite service, or project planning is involved.
    


    

    Submitting a request does not guarantee immediate response, immediate service, same-day availability, after-hours availability, or immediate resolution, but complete information helps the request move forward more efficiently.
    Submitting a request does not guarantee immediate response, immediate service, same-day availability, after-hours availability, or immediate resolution, but complete information helps the request move forward more efficiently.

    Public SLA Note

    Public-facing response expectations are general guidance, not a guarantee of a specific service level, response time, or resolution time.
    Internal service targets may be used to help organize work, but those targets do not guarantee immediate service, same-day service, after-hours service, or complete resolution.

    Closing or Pending Requests

    A request may remain pending when waiting for:

    • Client response

    • Client availability

    • Vendor response

    • Payment or approval

    • Estimate review

    • Scheduling confirmation

    • Security review

    • Client testing

    • Follow up after service

    A request may be closed 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, remote support, onsite service, 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

    Important Safety Note

    For possible scams, suspicious messages, malware concerns, account compromise, or payment redirection concerns, stop interacting with the suspicious item and request review before continuing.

    Do not click links, open attachments, approve sign-in prompts, provide payment information, or allow unknown remote access until the concern has been reviewed.

    Related Answers

    Use these related answers when needed:

    • How to Request Support

    • Preparing for a Remote Support Session

    • Service Expectations

    • Rush Service Explanation

    • Basic Scam Safety Guidance

    Tags
    Client_Support Business_Hours
    Published