Answer subscriber, audience and customer messages for information businesses
Spaces connects the messaging accounts that your readers, viewers, subscribers, customers and partners already write to, so an AI agent can read those messages and reply in the same chat using information you give it.
In the information sector, people write to ask about access, subscriptions, accounts, outages, rights and corrections, and the answers are usually already written somewhere.

- Information businesses receive repeated questions about subscriptions, access, billing, accounts, technical status, rights and submissions, and an agent can answer these from your own help text.
- The people writing range from readers and listeners to enterprise customers and licensing partners, so the agent should be told who it is talking to.
- Outages with business impact, billing disputes, legal and rights questions, corrections, complaints about content, privacy and security issues must go to a person.
- Spaces carries the messages only, so account, billing and status systems are reached by the agent through its own tools or not at all.
- Spaces is for people who write to you or who know you and expect to hear from you, and its Terms rule out cold outreach, bulk unsolicited messages and bought lists.
The sector covers film, video and sound recording, publishing of newspapers, periodicals, books and software, broadcasting, streaming and content networks, telecommunications, data processing, web hosting and computing infrastructure, and web portals, libraries and archives.
The audiences differ sharply, from the public to business customers, so the agent must be briefed for each. Spaces suits conversations people start and people who already know you.
- Sector
- NAICS 51
- Inside it
- 6 subsectors
- Last updated
Here is one conversation, start to finish.
An example of how an AI agent handles a message in information. The names and details are made up.
Who writes to an information business
A newspaper, magazine or book publisher hears from subscribers about deliveries and access, from readers about corrections, from authors and freelancers about submissions, and from advertisers and rights buyers. A radio or television station hears from listeners and viewers about schedules, reception and competitions.
A streaming service or content network hears from users about accounts, playback and billing.
A film, video or sound recording business hears from bookers, venues, distributors and artists about screenings, licences and releases. A software publisher hears from customers about licences, installs, bugs and renewals.
A telecommunications company hears about connections, coverage, bills and faults, in large volume from the public. A hosting or data processing firm hears from business customers about outages and capacity, often with urgency.
Libraries, archives and portals hear from members of the public with research and access queries. As with every sector, the key step is to write down who actually sends you chat messages and about what.
A software firm whose customers use a ticketing system may want the agent only for sales and licence questions, while a local radio station may want it for listener messages.
Questions an agent can answer, by kind of business
For publishers and broadcasters, the agent can explain how to subscribe, pause or cancel, how to reach the newsroom, where to send a story tip or a submission, how a delivery problem is reported, and what the schedule is.
It can also state your published corrections process. It should not decide whether a correction is needed or comment on editorial judgement.
For software, hosting and data businesses, the agent can answer how to install or renew, what is included in a product, where documentation lives, how to reset access, and what a status message means in your words.
Troubleshooting that needs a person looking at the customer's account or logs should go to support. If your agent can read a status page through its own tools, it can say whether an incident is known.
For telecommunications, the agent can explain how to set up a service, read a bill, move home, report a fault and understand coverage notes you publish. It can collect fault details and pass them to engineers.
It should not promise repair times or discuss contract exits and charges beyond the wording you provide.
- Subscription, access, delivery and renewal questions
- Where to find documentation, schedules and help pages
- How to send a submission, tip, correction or licence request
- How to report a fault, outage or account problem
Rights, licensing and creative work
Many messages to publishers, studios and labels concern rights: may I use this clip, can I quote this chapter, how do I license this track. These look simple and are not.
The agent can explain how to submit a request and what details you need, such as the work, the use, the territory and the time, and then pass the request to the person who handles licensing.
Submissions from authors, freelancers, musicians and filmmakers are a second stream. The agent can state your submission guidelines and what happens next, and acknowledge receipt. It should not comment on quality, make promises about acceptance or discuss fees and contracts.
That is a conversation for editors and managers.
Piracy, takedown notices, defamation concerns and anything that sounds legal must go to a person. The agent can confirm receipt and tell the sender who will reply, but it should not argue the case.
What you give your agent
Give it your product and service descriptions, your plans in the words you use for them, your help pages and policies on renewal, cancellation and refunds, and the steps customers take to fix common issues.
Add your schedules, your contact routes for newsroom, support, sales, licensing and billing, and your hours. If you run a status page or incident log, tell it where its information comes from and how it should describe an incident.
Describe who it is talking to. A reader, a business customer and a rights buyer need different replies. Give examples of your tone: a newspaper may be direct and plain, a software firm may be technical, a station may be warm.
Include a few lines it should never say, such as guesses about causes, promises about timing or comments on competitors.
Describe account safety. For any request involving account access, personal data or payment details, spell out what the agent can do and what it must pass to a person.
It should never ask for passwords or full payment details in a chat, and it should send security concerns to staff.
What should always go to a person
Outages or incidents with business impact need a person at once, as do reports of a security breach, a data leak, a hacked account or a privacy request. The agent should acknowledge, gather what the customer can say and promise nothing about cause or timing.
Billing disputes, refund requests outside policy, contract questions, enterprise terms and renewals with negotiation belong to staff. So do legal matters, rights and licensing decisions, takedown requests, complaints about content, corrections, and anything touching harassment, abuse or a person at risk.
Press enquiries and statements about your organisation are another category. The agent can direct people to your press contact, but should not comment on stories, plans or performance.
A week in the life of the inbox
At the start of a week, subscribers and customers write about access problems and weekend outages, and the agent works through the standard fixes and passes the rest to support. Midweek is quieter and a good time for rights and submission queries to be handled.
Billing cycles create their own spikes, which you can predict from your calendar.
Events drive the rest: a major news story, a big release, a promotion, a software update, a network fault or a broadcast schedule change. Each one produces a burst of similar questions.
Prepare a short note for the agent whenever you plan an event, and keep one place where staff update the facts during an incident.
After each spike, read the handed-over chats. They show which questions your help pages do not answer and are a quick way to improve both the agent and the pages.
Setting it up, measuring it, and its limits
Connect the account people already write to and begin with replies held as drafts. Spaces enforces per-account limits, pacing and warm-up, and every send is safe to retry, so a burst of messages in an incident does not produce duplicate replies.
Judge the result by time to first reply, how often customers repeat themselves and how often chats are handed over, and whether the handed-over ones needed a person.
Spaces is not a ticketing system, a status page, a newsletter tool or an audience-building channel. It does not hold subscriber data and should not be used for promotions or for contacting people who have not asked to hear from you.
It carries the conversation, and the agent reaches your accounts, billing and status systems through its own tools.
What does an agent actually see?
Examples of first messages to businesses in information. They are illustrations, not real conversations.
- Maya R.Hi, I subscribed last week but I still cannot read the articles on the app. Can you help?
- Tom B.Can I use a thirty second clip from your documentary in a school project? Who do I ask?
- Priya S.My licence key says it has expired but I renewed yesterday.
- Daniel K.I want to pitch a feature to your magazine. Who should I send it to and what do you need?
- Amara O.The broadband has been down since this morning. Is there a problem in my area?
- Maya R.What time is the evening news on Saturday, and is there a repeat?
- Tom B.Our hosted site has been very slow since ten o clock. Is something going on?
- Priya S.There is a mistake in your article about our company. Who do I speak to about a correction?
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.
Any outage, security breach, data leak, hacked account or privacy request.
Billing disputes, refund requests outside policy, contract negotiation and enterprise terms.
Rights, licensing, takedown, defamation and other legal matters.
Requests for corrections, complaints about content and anything about harassment or a person at risk.
Press enquiries and requests for comment on stories, plans or performance.
A customer who asks for a person, is angry, or whose request the agent does not understand.
Explore the subsectors.
Thirty free tools for publishers, broadcasters and media and telecom companies.
Checklists, ready-to-send messages, scorecards and calculators. They run in your browser and send nothing anywhere.
- First-reply checklist for publishers, broadcasters and media and telecom companies
- Hand-over rules checklist for publishers, broadcasters and media and telecom companies
- First-week checklist for publishers, broadcasters and media and telecom companies
- Weekly chat review checklist for publishers, broadcasters and media and telecom companies
- Busy-season checklist for publishers, broadcasters and media and telecom companies
- Customer privacy checklist for publishers, broadcasters and media and telecom companies
- Do and don't guide for your agent: publishers, broadcasters and media and telecom companies
- Greeting messages for publishers, broadcasters and media and telecom companies
- All 30 tools
Questions, answered.
01Can the agent reset passwords or change an account?
Not through Spaces, which carries the messages only. If your agent has its own tools for that, set strict rules for confirming identity, and never let it ask for passwords or full payment details in a chat. Security concerns should go to a person.
02Can it tell customers whether there is an outage?
Only from a status note you keep current or a source it can read through its own tools. It should not guess at causes or fix times, and any incident with business impact should alert a person.
03Can it handle licensing and rights requests?
It can explain how to submit one and collect the details you need, then pass it to the person who decides. It should not agree to a use or quote a fee.
04Is this useful for a small local newspaper or station?
Yes. Small outlets often have no one to answer delivery, subscription and schedule questions promptly, and an agent can take those while editors handle stories and corrections.
05How should corrections and complaints about content be handled?
Hand them to a person, with the details the sender gave. The agent can state your corrections process and confirm receipt, but it should not judge whether a correction is needed.
06Can we use it to send our newsletter or promotions?
No. Spaces is for conversations people start and for people who know you and expect to hear from you. Its Terms rule out bulk unsolicited messages, cold outreach and bought lists.
07Does it work for telecom or hosting providers?
It can answer how-to, billing and fault-reporting questions and collect details for engineers. Outages and anything with business impact should go to a person quickly.
08How do we stop it making things up about our products?
Tell it to answer only from the information you have given it, and to say that a person will confirm when it does not know. Reviewing a sample of its replies each week finds gaps before customers do.
Closer guides for specific businesses.

Telecom and utilities
Let an AI agent answer outage and service questions customers send your telecom or utility business, and pass billing issues to a person. Customer-started conversations only.

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.