How to Request Support

Purpose

The purpose of this answer is to help clients submit clear support requests so PrismTechTx LLC can review the issue efficiently and determine the right next step.

A good support request helps identify:

• Who needs help

• What issue is happening

• What device, account, software, or service is involved

• When the issue started

• Whether the issue affects one person or multiple people

• Whether the issue may involve a scam, suspicious message, or security concern

• Whether remote support, onsite service, vendor coordination, billing review, or project work may be needed

How to Request Support

Information to Include

When requesting support, include the following information when available:

• 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 anything changed recently

• Whether there is a deadline or time sensitivity

• Whether the issue may involve a suspicious message, scam, malware, or account compromise

Good Support Request Example

Hello,

I need help with my laptop. Outlook keeps asking for my password and will not finish loading my email.

This started yesterday afternoon. I restarted the laptop, but the issue came back.

Device: Dell laptop
Account/service: Microsoft 365 email
Best contact: Phone or email
Availability: Today after 2:00 PM

Less Helpful Support Request Example

My computer is not working.

This may be enough to start a ticket, but additional information will be needed before the issue can be reviewed properly.

For Business Support Requests

Business support requests should include business impact when possible.

Helpful details include:

• Business or organization name

• Affected user or department

• Number of people affected

• Whether work is blocked

• Whether email, phones, payment systems, files, website, or internet access are affected

• Whether the issue affects clients, customers, or public access

• Any deadline or operational impact

For Residential Support Requests

Residential support requests should include the device, account, or service involved.

Helpful details include:

• Type of device

• Whether the issue affects one device or several devices

• Whether the issue affects internet, email, printer, computer, phone, tablet, or software

• Whether the issue started after an update, installation, outage, or suspicious message

• Whether remote support may be possible

For Suspicious Emails, Scams, or Security Concerns

If the request involves a suspicious email, text, call, popup, attachment, website, invoice, or account alert, do not interact with it further until it is reviewed.

Do not:

• Click suspicious links

• Open unexpected attachments

• Call numbers listed in suspicious messages

• Approve unexpected sign-in prompts

• Provide passwords

• Provide payment information

• Allow unknown people to remotely access the device

When requesting review, include:

• Screenshot of the message, when safe

• Sender email address or phone number

• Date and time received

• Whether any links were clicked

• Whether any attachments were opened

• Whether any username, password, payment, or account information was entered

• Whether anyone remotely accessed the device

For Remote Support Requests

Remote support may be possible for many software, account, email, and configuration issues.

Before requesting remote support, clients should be prepared to:

• Be available during the session

• Confirm the device being accessed

• Approve the remote session

• Close unrelated sensitive information

• Avoid sending passwords through email or ticket replies

• Follow the remote support instructions provided

Some issues may still require onsite service, vendor support, or project handling.

For Website or Online Presence Requests

Website development and online presence requests are handled as consultation-based requests and may require a quote or estimate before work begins.

If requesting help with a website, include:

• Existing website address, if any

• Platform, if known

• Goal of the request

• Whether this is a new website, redesign, update, form issue, domain issue, hosting issue, or publishing request

• Desired timeline

• Whether domain, DNS, hosting, email, SSL, or forms are involved

• Any examples or content already available

Website requests may need to be reviewed before PrismTechTx LLC confirms whether the work can be accepted.

What Happens After a Request Is Submitted

After a request is submitted, PrismTechTx LLC will review the information provided and determine the appropriate next step. Submitting a request does not guarantee immediate service, same-day availability, or immediate resolution.

Possible next steps may include:

• Asking clarifying questions

• Scheduling remote support

• Scheduling onsite service

• Providing guidance

• Preparing an estimate or quote

• Coordinating with a vendor

• Treating the request as a project

• Reviewing a security concern

• Closing the request if no further action is needed

Requests That May Require an Estimate or Quote

Some requests may require an estimate or quote before work begins. Hardware, software, licensing, subscriptions, vendor charges, materials, travel, rush service, after-hours work, holiday service, or multi-step project work may be itemized separately when applicable.

Examples include:

• Multi-step work

• Website work

• Hardware or software setup

• Network or WiFi improvements

• Backup and recovery planning

• Security hardening

• Projects

• Work requiring hardware, software, licensing, subscriptions, or vendor costs

• Work where the scope is not yet clear

Vendor-Dependent Requests

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 response, access requirements, support process, or timeline.

Response Expectations

• Request type
  
  
• Complexity
  
  
• Urgency
  
  
• Client availability
  
  
• Existing workload
  
  
• Vendor response
  
  
• Required approvals
  
  
• Whether remote or onsite work is needed
  
  
• Whether the issue involves security review
  
  
• Whether the request requires project handling or third-party coordination

Important Safety Note

If the request involves a possible scam, suspicious message, malware concern, account compromise, or payment redirection concern, stop interacting with the suspicious item and request review before continuing.

It is better to pause and ask than to click, approve, pay, or provide information in a risky situation.

Related Answers

Use these related answers when needed:

• Preparing for a Remote Support Session

• Service Expectations

• Rush Service Explanation

• Basic Scam Safety Guidance

• Business Hours and Response Expectations