Answer software customer messages before they become tickets
Customers write to a software publisher with an error, a licence key and a question: it will not install, where is my download, does this work with my version.
Spaces connects the messaging account those customers already use, so an AI agent can read each message and reply in the same chat, using the product knowledge you give it.

- Software messages are mostly install problems, licence and account issues, compatibility questions and how-to requests.
- An agent can walk through documented steps, explain editions and requirements and look up a licence you give it access to.
- Security reports, data loss, refunds, billing disputes and enterprise deals should go to a person.
- The agent is only as good as your docs, release notes and known-issue list.
- Spaces is for customers who write to you or expect to hear from you, never for cold outreach.
This page is for businesses that publish packaged and subscription software, from games and utilities to business and creative tools. Spaces handles the messages only.
Your agent reaches your licence system, docs and account data through its own tools, and a person handles billing disputes, security reports and anything about someone's data.
- Industry group
- NAICS 5132
- Part of
- Information / Publishing Industries
- Last updated
Here is one conversation, start to finish.
An example of how an AI agent handles a message in software publishers. The names and details are made up.
What lands in a software publisher's chat
Customers rarely write when things work. They write after a failed update, a lost licence email or a feature that is not where it was. A buyer of a business tool asks whether a new version supports their operating system.
A hobbyist asks how to move a licence to a new laptop.
A second group is evaluators: people who have not bought yet and want to know which edition fits, what the trial includes and how licences are counted. They are also people who know you, because they came to your site and started the conversation.
Answers an agent can give from your docs
Most repeat questions have documented answers. Where to download, how to activate, how to move a licence, what the system requirements are and which version fixed a known bug.
Give the agent your docs, your release notes and your known-issue list, and it replies in plain steps without sending the customer to a search page.
With a lookup into your licence system, it can also confirm which edition an email holds, how many seats are used and when a subscription renews. It reports; it does not change entitlements unless you give it that power.
- Install, update and activation steps by platform
- System requirements and edition comparisons
- Licence lookup and seat counts for the account that is writing
- Known issues and workarounds from your release notes
How to brief the agent
Write down the order of troubleshooting your best support person follows. Ask for version and platform first, then the exact error text, then the steps that usually fix it. Tell the agent when to stop and hand over, such as after two failed steps.
Add the words you want to avoid. Customers do not want to hear it is a user error, and an agent that never says so earns trust.
The line the agent never crosses
Security and data are for people. A report of a vulnerability, suspected misuse of an account, lost work or a privacy request needs a named person and a record. The agent confirms receipt, gathers the details and hands the thread across.
Money questions also go human: refunds, charge disputes, invoices for a company, volume pricing and custom contracts. The agent says who will reply and by when you tell it.
Release days and quiet weeks
A release produces a spike of messages about the new version within hours. An agent that knows the release notes can handle the first wave while your engineers read the real bug reports.
Start with install and licence questions. Add trial and edition guidance next, and keep a short list of new known issues updated on release day.
What does an agent actually see?
Examples of first messages to businesses in software publishers. They are illustrations, not real conversations.
- Maya R.I updated this morning and now the app will not open. What should I do?
- Tom B.I lost the email with my licence key. Can you resend it?
- Priya S.Does version 5 work on my older laptop with Windows 10?
- Daniel K.How do I move my licence to a new computer?
- Amara O.What is the difference between the standard and pro edition?
- Maya R.Is there a trial for the team plan, and how many seats does it include?
- Tom B.I think I found a way to read another user's files. Who should I tell?
- Priya S.I was charged twice for my subscription this month.
What always goes to a person.
Your agent answers what it can and hands the rest to someone on your team. These are the conversations to hand over every time.
Security reports and suspected account compromise
Lost or corrupted user data and privacy requests
Refunds, double charges and billing disputes
Company contracts, volume pricing and custom terms
Bug reports that need engineering and are not in the known-issue list
Press, partner and reseller enquiries
- Software Publishers
Thirty free tools for software publishers and app makers.
Checklists, ready-to-send messages, scorecards and calculators. They run in your browser and send nothing anywhere.
- First-reply checklist for software publishers and app makers
- Hand-over rules checklist for software publishers and app makers
- First-week checklist for software publishers and app makers
- Weekly chat review checklist for software publishers and app makers
- Busy-season checklist for software publishers and app makers
- Customer privacy checklist for software publishers and app makers
- Do and don't guide for your agent: software publishers and app makers
- Greeting messages for software publishers and app makers
- All 30 tools
Questions, answered.
01Can the agent resend a licence key?
If you give it a tool for your licence system and rules about verifying the owner. Otherwise it passes the request to your support team.
02Will it solve a bug it has never seen?
No. It follows your documented steps and known issues, then hands the thread over with the details your engineers need.
03Does it replace our help centre?
It works alongside it. The agent can pull answers from the same articles and reply in the chat the customer started.
04Can it announce a new release to users?
Only to users who know you and expect to hear from you. Bulk or cold messaging is outside what Spaces allows.
05How does it handle different platforms?
Give it your docs split by platform, and tell it to ask which one the customer uses before answering.
06Can it see a customer's account?
Only through the tools you give it, and only for the person writing. Spaces carries the message; your own system holds the data.
Closer guides for specific businesses.

Supermarkets
Let an AI agent answer the messages shoppers send your store about stock, hours and order pickup. Customer-started conversations only.

Restaurants
Let an AI agent answer guests' messages about bookings, menus, hours and takeaway, in the chat they started.

Retail stores
Let an AI agent answer customers' messages about sizes, stock, store hours and reserve-and-collect, in the chat they started.

Online stores
Let an AI agent answer order, delivery, return and sizing questions from your customers in the chat they started.

Salons
Let an AI agent answer clients' booking, rescheduling and price questions in the chat they started, while you're with a client.

Real estate
Let an AI agent reply to people who message about your listings: availability, viewings and details, in the chat they started.