Spaces
Subsector / NAICS 518

Answer hosting and data processing customers in the chat they already use

Companies that provide computing infrastructure, data processing and web hosting hear from customers at all hours: a site is down, a certificate has expired, an invoice looks wrong, a migration is due.

Spaces connects the messaging account those customers already write to, so an AI agent can read each message and reply in the same chat, using the facts you give it.

A friendly clay robot agent beside a phone with chat bubbles, with WhatsApp, Instagram and LinkedIn icons
Key takeaways
  • Customers of hosting and data processing firms usually message when something is wrong or about to change, so speed and clarity of the first reply matter most.
  • An agent can answer routine questions about plans, domains, backups, renewals and setup steps from information you provide.
  • Spaces handles the messages only, so any look-up of server status, tickets or accounts happens through your agent's own tools.
  • Outages, suspected security problems, data loss, legal requests and contract changes should always go to a person.
  • Spaces is for customers who write to you and people who expect to hear from you, never for cold outreach or bought lists.

This is a good fit for the routine, repeatable questions and a poor fit for anything that needs an engineer's judgment.

The agent can explain how your plans are organised, point to the right setup steps, collect the details a technician will need and tell people what happens next.

It hands the conversation to a person whenever an incident, a security concern or a contract decision is involved.

Subsector
NAICS 518
Part of
Information
Inside it
1 industry groups
Last updated
See it in your world

Here is one conversation, start to finish.

An example of how an AI agent handles a message in computing infrastructure providers, data processing, web hosting, and related services. The names and details are made up.

DevComputing Infrastructure Providers, Data Processing, Web Hosting, and Related ServicesAI agent
In this guide
01 / Subsector

Who messages a hosting or data processing business

The code 518 covers a wide span of providers: companies that rent out computing capacity and storage, firms that process data on behalf of others, and businesses that host websites and applications.

Their customers range from a bakery owner with a single website to a small software team running several servers and a finance department outsourcing payroll data handling. Each group writes differently, and the first thing to settle is which of them reach you through chat.

Small site owners tend to write in plain language and often have no technical vocabulary. They say the site is slow, the page shows an error, or the shop will not load.

Technical customers write shorter and more precisely: a service name, a region, a time something started. Partners such as web agencies and resellers message on behalf of their own clients and expect quick, accurate answers they can pass on.

Suppliers and contractors write too, for example a data centre technician confirming a visit window or a domain registrar contact asking about a transfer.

Be honest about this in your set-up: the agent should be told which kinds of senders it may answer and which it should simply pass to the right person.

02 / Subsector

What an agent can answer

Go through your sub-services one at a time.

For web hosting, the usual questions are how to point a domain at the service, where to find the control panel, how backups work, how to restore a file, and how to add another website to an existing plan.

For data processing work, customers ask when a batch will be delivered, what format a file should arrive in, who to contact about a rejected record and how long a job normally takes.

For infrastructure rental, they ask how to add storage, resize a server or move to another region.

An agent can answer all of these from a short knowledge document that you write once and keep current. It is not guessing: it is repeating your published process in a friendly voice, in the language the customer used.

When it reaches the edge of what you wrote, it says so and brings in a person rather than inventing an answer.

  • Domain and DNS set-up steps in plain language
  • Where backups live and how restores are requested
  • How to upgrade, downgrade or add a service
  • Expected turnaround for a processing job once it is submitted
  • What a customer should send when reporting a fault
03 / Subsector

Fault reports and the first reply

A customer who writes that their site is down is anxious, and a fast, calm first reply changes the whole tone of the exchange.

The agent can acknowledge the message straight away, ask for the domain name, what the visitor sees, when it began and whether anything was changed just before, and tell the customer a person is looking at it.

That means the engineer opens the case with the information already gathered instead of starting with questions.

What the agent should not do is diagnose. It should not tell a customer that nothing is wrong, promise a fix time or guess at a cause.

If your agent has a tool that reads your status page or monitoring system, it can pass on what that tool reports, worded as a fact from your system, and still bring in a person for anything unresolved.

04 / Subsector

What you must give your agent

The quality of the replies depends on the quality of the brief.

Write down your plans and what each includes, your renewal and billing rules, your support hours and how out-of-hours faults are handled, the steps for common tasks, the formats and cut-off times for processing work, and the exact wording you use for things you cannot promise.

Keep it in one place so you can update it when a plan changes.

Also tell the agent who to hand over to, by role, and what a good handover note looks like: customer name, service, what was asked, what has already been said.

Make clear which topics it must never discuss, such as another customer's account, and that it should ask for identity checks to be done by a person.

Remember that Spaces connects the chat only. If you want the agent to look up an invoice or a server's state, it needs its own tool to do that, set up in the agent and not in Spaces.

05 / Subsector

What always stays with a person

Some conversations in this field carry real consequences.

Anything about an active outage that affects a customer's business, a suspected breach, lost or exposed data, a request from a lawyer or authority, a contract dispute, a refund or a service credit belongs to a named member of staff.

So does any change that cannot be undone, such as deleting a server or wiping a backup.

Agents should also hand over when a customer is upset, when they ask for a person, or when the same problem has come back several times. Set these rules clearly, and test them with practice messages before the agent talks to a real customer.

06 / Subsector

A typical week

Monday brings weekend leftovers: renewals that lapsed, a site a customer changed on Friday and cannot now open. Mid-week, planned maintenance notes prompt questions about timing and whether a customer's service is affected.

Month end brings invoice questions, and processing firms see rushes around reporting deadlines when clients want a file turned around quickly.

Across all of this the agent takes the repeat questions and the information-gathering, and your engineers and account managers pick up the conversations that need judgment.

Because the agent can pace its replies and Spaces enforces limits per account, a burst of messages after a disruption does not cause the account to behave erratically.

07 / Subsector

Setting it up step by step

Start small. Connect the messaging account customers already use, point your agent at it, and begin with read-only access or with replies held as drafts so a person reviews each one.

Write the knowledge document, add your hand-over rules, and run twenty or so realistic messages through it yourself, including awkward ones.

When the drafts look right, let the agent send the simplest kind of reply on its own, such as opening hours and how-to steps, and keep everything else in review.

Widen its remit slowly, and read a sample of real conversations each week to catch drift.

08 / Subsector

Common mistakes

The most frequent error is giving the agent too little detail about what is and is not included in each plan, so it answers confidently and wrongly. The second is letting it speculate during an incident.

The third is forgetting that customers may write on behalf of a company they do not own, so an agent should not disclose account details to anyone who has not been verified by a person.

Another is treating the account as a broadcast tool. Telling every customer about a new product is not what Spaces is for. Updates about a fault that a customer has reported, sent to the people who reported it, are fine.

09 / Subsector

How to tell it is working, and where Spaces does not fit

Look at qualitative signs. Do customers get a first reply quickly, even at night? Do engineers receive handovers that already contain the domain, the symptom and the time?

How often do conversations go to a person, and are they the right ones? Are customers asking the same question twice because the first answer was unclear? Reading real conversations each week tells you more than any single number.

Spaces is not a status page, a ticketing system, a monitoring tool or a way to broadcast maintenance notices to everyone. It does not log in to servers or change configuration.

It is also unsuitable if your customers do not use a messaging account to reach you, because there is nothing to connect. In that case keep your existing support channels and consider Spaces only if that changes.

Messages people send

What does an agent actually see?

Examples of first messages to businesses in computing infrastructure providers, data processing, web hosting, and related services. They are illustrations, not real conversations.

  • Maya R.My website has been showing an error since this morning, can someone look at it?now
  • Tom B.How do I point my domain to the new server you set up for us?2 min
  • Priya S.We need to move our database to a different region. What do we have to do?9 min
  • Daniel K.Can you restore yesterday's backup of our shop?24 min
  • Amara O.Our batch file for the monthly payroll run was rejected. What format do you need?1 h
  • Maya R.My invoice shows two hosting plans but I only have one. Can you check?now
  • Tom B.I am an agency and need to add three more client sites to our plan.2 min
  • Priya S.Our certificate expires tomorrow, will it renew by itself?9 min
Illustration: the chats your agent reads through the API, with example names.
Hand-over

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.

01

Any active outage or degraded service that affects a customer's business.

02

A suspected security incident, data exposure or lost data.

03

Requests from lawyers, authorities or anyone claiming to act for a customer.

04

Contract changes, disputes, refunds and service credits.

05

Any request to delete servers, wipe data or make changes that cannot be reversed.

06

A customer who asks for a person or is clearly upset.

Inside Computing Infrastructure Providers, Data Processing, Web Hosting, and Related Services

Explore the industry groups.

Free tools

Thirty free tools for hosting and data processing providers.

Checklists, ready-to-send messages, scorecards and calculators. They run in your browser and send nothing anywhere.

FAQ

Questions, answered.

01Can the agent check whether my server is up?

Only if your agent has its own tool that reads your monitoring or status system. Spaces handles the messages. If the agent has such a tool, it should report what the tool says and hand anything unresolved to a person.

02Should it tell customers when an outage will be fixed?

No. Give the agent wording that says a person is working on it and that an update will follow. Fix times should come from your engineers.

03Can it reset a customer's password or access?

That is an identity decision and should go to a person. The agent can explain your reset steps and collect the request.

04Will it understand technical messages?

It can read technical wording, and you can add a glossary of your service names to your brief. For anything that needs real diagnosis, it should hand over with the details it gathered.

05Can we use it to announce maintenance to all customers?

No. Spaces is for conversations people start and for people who expect to hear from you. Bulk announcements to a whole list are ruled out by its Terms, so use your usual notice channels.

06What about customers who write in another language?

The agent can reply in the language the customer used, based on the information you provided. Have a person check anything that carries legal or billing weight.

07Can resellers and agencies use the same chat?

Yes, they are people who know you and write to you. Tell the agent which partner questions it can answer and which need your account team.

08Is every reply safe to retry if something fails?

Yes. Spaces makes every send safe to retry, so a network hiccup will not produce a duplicate message to the customer.

Guides

Closer guides for specific businesses.

Give your agent its first account today.