Skip to content

Tech support

Start with what stopped.

You do not need to diagnose the fault before you call. Tell us what happened, who it affects, and which part of the day has stopped.

  1. What changedThe message, outage, or behavior you noticed.
  2. Who feels itThe people, rooms, devices, or customers affected.
  3. What cannot waitWhat needs to work first so you can carry on.
Little Fight journal artwork with a Wi-Fi symbol
A connection problem is easier to solve when the pattern is visible.

A small map beats a big guess

Find the break before changing anything.

We check what still works and where the trouble begins. For Wi-Fi, that might mean testing the connection near the router, then in the rooms where you actually use it. That helps us tell an internet-provider issue from a problem inside the space.

What should stay private?

Do not send passwords, recovery codes, payment data, or private customer records in a support request. Share the symptom first and agree on a safe access method.

Read the Wi-Fi guide +

The first useful record

Know what we fixed.

You should be able to explain the fix without learning a new vocabulary. We leave a plain account of what changed, who controls it, and what to check next.

Symptom
What staff or customers saw.
Scope
Which work, devices, rooms, or accounts were affected.
Change
What we changed and which account controls it.
Next check
What to check if the problem returns.

Everyday systems

Get help with the tools you use.

Wi-Fi, printers, and payment devices

Map where the connection fails and what still works before moving equipment or changing settings. A guest network, a card reader, and a staff laptop may need different checks.

Outlook, Microsoft 365, and business email

Look at the message path, mailbox rules, and account owner. In Microsoft 365, check shared-mailbox access, licenses, and who can administer the account. Preserve the mail and files the business needs before a staff handover.

Check business email +
Mac, iPhone, iPad, and Windows setup

List the tasks that must work on day one. Test email, files, printing, calls, and the connection where you will use the device. Check the work account and recovery route, and keep the old device until the handover works.

Plan a device handover +

When a visit makes sense

Plan around the work that must stay on.

Tell us your New York neighborhood and what needs attention. We confirm visit availability, access and the work involved before you make plans. Website projects are our current priority; a visit is booked only when we confirm it with you.

Your accounts stay yours. If a provider or equipment vendor needs to act, we explain who to contact and what they need to know.

Tech support questions

How do I make sure I own my domain, website, and website accounts?

Your domain, hosting, site platform, and connected tools should live in accounts the business can renew and recover.

We map who holds each account, move ownership where it belongs, and leave usable handoff notes so one person is never the only key.

Bring the account names and renewal notices you can find; keep passwords private.

How can a business avoid losing control of its domain name?

Your domain needs a business-controlled login, renewal email, payment method, and recovery contact before the next notice arrives.

We identify the registrar and authorized account owner, then record the details that keep a later renewal or provider change manageable.

Send the domain name and the email that receives its renewal notices.

What should I check after a website update goes live?

After an update, use a phone to test every page, link, or button that you changed. Follow each link or button you changed and check that any form, booking, or payment still reaches the right place.

We test the pages, forms, links, booking, or checkout involved, then leave a short record of what changed for the next update.

Send the update you made and the customer action it was meant to improve.

What should a business know about website hosting before changing providers?

Before moving a site, find out who controls its hosting, domain, and email and how they connect. Check how email is connected, keep a backup, and agree on how to restore the old setup if needed.

We map what the site depends on, keep the business as the account owner, and plan the move around the pages customers rely on.

Send the hosting provider and domain details before you end any service.

Why does the Wi-Fi work in one room but not another?

A strong signal in one room can turn weak in another because walls, distance, or nearby devices get in the way.

Test near the router, then in the room where work stops. Note which devices fail. We can check whether the cause is the placement, the equipment, or your internet service.

Tell us where the connection drops.

Why are my business emails going to spam?

Email can be flagged because of its content, how it was sent, or settings on either account. Check whether it affects everyone or only some people.

Check Junk or Spam and note any error. We can review sender checks, mailbox rules, account access, and Microsoft 365 shared-mailbox permissions. Leave domain settings alone until the cause is clear.

Tell us what happened and the sending address. Never include passwords, sign-in codes, or private customer messages.

What should happen before a new work computer replaces the old one?

Set up the new Mac or Windows computer before the old one is retired, then test the work that cannot pause.

List the approved apps, accounts, files, printers, and shared folders. For a Mac, iPhone, iPad, or Windows device, record its work account and recovery route. Test the real work, then keep the old device until important tasks are checked.

List the programs and files the new computer must have on day one.

What happens during an on-site tech visit?

An on-site visit starts with the symptom, the people affected, and the work that must keep moving.

We confirm New York availability after the issue and location are known. The visit focuses on what can be checked safely, what needs a follow-up, and a plain note of the changes made.

Share the location, the problem, and what work is blocked.

Why will one computer print but another cannot?

If one computer can print but another cannot, compare their connections and settings before replacing the printer. Check their Wi-Fi networks, selected printer, and error messages first.

Choose the same printer on both devices and check whether a stuck job is holding the queue. Note which computer works before changing settings. We can help check the printer software and connection if the difference is unclear.

Tell us which computer prints and which one does not.

How do I know our files are really backed up?

Keep a separate copy of important files and check that you can recover a sample. Seeing a backup icon is not the same as knowing your files can be restored.

Check which files are copied, where the copy lives, and who can recover it. Restore a harmless sample into a new location, protecting the working file. Ask us if the settings are unclear.

Bring the backup service name and one file you would need back.

What should I include when I ask for tech help?

A useful tech request names what changed, who is affected, which device or service is involved, and what work is blocked.

A screenshot, exact error message, and the time the problem started can help. Do not send passwords by text or email; agree on a safe access method first.

Call, text, or email the symptom in your own words.

What should a small office plan before moving?

Plan the internet connection, equipment locations, and the critical work that must continue before the move day arrives.

Confirm the provider’s installation plan, map where network equipment and printers will live, and list the systems that staff need on the first day. Test the essentials once the space is ready.

Share the move date, new address, and the systems that must work first.

Do we need ongoing tech support?

The right amount of tech support depends on what keeps breaking, what changes often, and who handles the fixes now.

Start with the work your team needs each day. Check who owns the accounts, runs updates, and tests backups. A regular check may help; a new monthly bill should have a clear purpose.

Tell us which problems keep coming back.

Should guest Wi-Fi be separate from business equipment?

Give guests their own Wi-Fi network so their phones do not share access with your work devices and private files.

The name alone is not enough: the router must keep the two networks apart. We can check its settings and how your staff devices and card readers connect before making a change.

Tell us what guests use and what the staff uses.

Is the internet down, or is our Wi-Fi the problem?

A wired test can help separate a provider connection problem from a problem inside the Wi-Fi network.

If a computer works through a cable but not through Wi-Fi, focus on the local network. If both fail, check the provider status and the internet equipment before changing settings.

Tell us what works on a cable and what fails on Wi-Fi.

Why are customer replies missing from a shared inbox?

Replies can go missing when a shared inbox has unclear forwarding rules, access settings, or no one assigned to check it.

Test it from an outside email account. Check which address the customer sees, where the reply lands, and who can read it. Give each public address a person who checks it.

Share the address customers use and where replies should arrive.

What should we do when someone leaves the team?

Before someone leaves, make sure the business can still reach the mail, files, and tools that person used for work.

List their work accounts, including Microsoft 365 where used. An approved account manager should keep needed records, transfer control, and then remove access. Do not wipe a device until the business has its files.

Start with the accounts and files the person controls.

What security basics should a small business check first?

Start with a separate login for each person, a second sign-in step, current software, and a backup you have tested.

Give staff a clear way to report a strange message. These steps lower risk; they cannot remove it. Check who can change the key accounts and how the business would get back in.

Bring the accounts and devices you most need to protect.

Who should own our business passwords and recovery methods?

The business should control its work accounts and have a safe way to regain access if someone leaves the team.

Keep a record of who can manage email, domains, payments, and cloud files. Check recovery details before you need them. For Apple devices, record the work Apple Account or device manager; do not copy passwords into the notes.

Start with the account that controls your business email.

How do we find duplicate subscriptions and surprise renewals?

Make one list of the tools you pay for, what each one does, and when the next bill is due.

Ask who uses each tool and which records it holds. Two apps may do the same job, but one might hold files the business still needs. Check that before you cancel.

Bring a recent list of software charges.

How do we make a meeting room ready for a client call?

Test the camera, microphone, display, and connection from the room where the meeting will happen.

Use the same laptop, conferencing account, and display path the team expects to use. Little Fight can check the working inputs and a fallback contact method before an important meeting.

Tell us which room, devices, and call platform you use.

What should we do when a work computer is out of storage?

Check what is taking up space before you delete files, especially folders that sync with other people or devices.

Start with the storage screen. Old downloads or installers may be easy to clear, but a shared file may disappear for everyone. Confirm you have a safe copy of any business records before removing them.

Share the storage summary without showing private files.

How should a small team organize shared files?

Use folder names that describe the work, give each person the right access, and put someone in charge of keeping things tidy.

Try a normal task. Can the right person find a recent invoice or an approved template without asking around? Fix the part that makes them stop and ask.

Show us one folder that the team struggles to use.

What should we test before using a new business phone number?

Call the new business number from another phone before you publish it, and check what happens when no one answers.

Listen to the voicemail, leave a test message, and confirm who gets it. Check the after-hours path too. We can help test the number and make sure customers have a clear way to reach you.

Tell us where calls should go.

How should we handle software updates without disrupting work?

List the devices and apps the team needs, then choose a time to update them when work can safely pause.

Check what a change could affect: payments, booking, files, or shared access. Keep a way to recover if it fails. After the update, test a normal task before the team relies on it.

Tell us which tasks cannot stop during the workday.

How do we make sure a former contractor no longer has access?

Turning off an email account may still leave a former contractor able to open shared files or sign into other tools.

List the systems they used. Have each account owner check and remove that access, including shared links. Keep the records the business needs and transfer control of files before closing an account.

Start with the services and folders the contractor used.

Why does the card reader disconnect during service?

A card reader may drop out because of a weak signal, a power problem, its settings, or the payment service itself.

Note the time and exact message on the screen. Check whether it happens in one place or across the shop. Plan tests around service, and keep customer card details out of support messages.

Tell us the reader model and when it fails.

What access should a new teammate receive?

Give a new teammate the accounts, devices, files, and instructions their role needs, then test a real first task with the manager.

Use role-based access rather than copying another person’s entire setup. Keep the owner of each account clear so later changes do not depend on memory.

Describe the role and the first task the person must complete.

How do we avoid a domain or email renewal problem?

Keep a clear record of where you bought the domain, who runs your email, and who gets each renewal notice.

Check the payment method and recovery details before a bill is due. Make sure the business can reach the person allowed to renew or change the account. We can help untangle who controls what.

Start with the domain name and latest renewal notice.

Why should a tech fix be written down?

A clear support note makes the next problem easier to understand because it records what changed, who owns it, and what to check first.

Keep the note plain enough for the business owner to use. Include the symptom, action, affected account or device, and any follow-up the owner needs to schedule.

Ask for a plain-language record after the next important fix.

What should we gather before changing IT providers?

Before changing tech providers, list the accounts they manage, who owns them, and which parts of the work must keep running.

Keep passwords out of email and text. Agree on a safe way to grant access. Set a time for the change, test the work afterward, and keep a record of who now handles each account.

Bring the service list and key work hours.

What makes a home office ready for real work?

A useful home office starts with the work you need to do, then matches the devices, connection, and account access to that job.

Test the laptop, monitor, printer, call platform, and work account together. Keep a simple record of cables, Wi-Fi details, and settings the owner may need later.

List the programs, devices, and calls you need to handle from home.

Talk to Little Fight.

Send a website link, an error message, or a few lines about the work. We’ll take a free first look and explain what we can help with.

9am–9pm Eastern. After hours, leave a message.