Spaces

Ready answers for software and IT firms

This library gives software and IT firms ready answers to common questions about support hours, project types, hosting and how to report a fault. Fill in your details and copy the ones you need.

Runs in your browser. Nothing you enter is sent anywhere or saved.

Before you start

Every software firm gets the same questions again and again. What are your support hours? Do you work with small businesses? How do I report a fault? Do you host the site as well? Writing the answers once, carefully, saves your team hundreds of repeated replies and gives your agent solid material.

Fill in the boxes below and the answers update with your details. Copy the ones that apply, and delete any that do not suit you. Read each aloud before you use it, and change anything that does not sound like your firm. Your own voice matters.

What are your support hours?

[business] support is open [hours]. Outside those hours, you can still write here. Urgent faults that stop your business are passed to our on-call engineer.

How do I report a problem?

The quickest way is [route]. A screenshot helps a lot. Please do not send passwords in the chat. We will confirm receipt and tell you when to expect an update.

What do you do?

[business] provides [services]. If you tell us a little about your situation, we can say whether it is a fit and suggest the next step.

Do you take on small projects?

Yes, [business] works on projects of different sizes. Tell us what you need, and who will use it, and a person will let you know how we could help, with [services] in mind.

Who owns the code or the site you build?

That is set out in your agreement with [business], so I will not guess. A person will confirm what applies to your project and send you the exact wording from the contract.

Write answers that sound like you

Ready answers should be short, warm and specific. Cut anything that sounds like a policy document. A client reading "our team will be delighted to assist" does not feel looked after. A client reading "write here and we will reply today" does.

Keep the library small and honest, ten to fifteen answers. Check it every few months so it still matches your hours, services and contracts.

Answers that should always go to a person

Some questions look routine but are not.

  • Who owns the code, the data or the domain.
  • Prices, discounts and contract changes.
  • Anything about security, breaches or access.
  • Questions about legal terms, data protection or liability.

FAQ

How many ready answers do we need?

Start with ten. Choose the questions you hear most, such as hours, how to report a fault and what you build. Add more as real chats show you what clients ask.

Can the agent change the wording of a ready answer?

Yes, lightly, to fit the question. You can tell it which facts must stay exactly as written, such as hours, so it never invents details.

What if a ready answer becomes out of date?

Put a reminder in your calendar to check the library every quarter, and whenever your hours, services or contract terms change. An old answer is worse than none.

More free tools for software and tech support firms

Read the guide: Answer client messages at your software and IT firm, from outages to scoping.