
Telecom
Your network never sleeps. Neither does your support.
AI agents for activations, tech support and billing.
Critical workflows.
New lines and services activated with every document in place
The agent guides customers through plan requirements, receives IDs and signed contracts, checks what is missing and prepares the activation for your team to approve.
- Requirements explained by plan
- ID and contract intake
- Missing-document follow-up
- Activation ready for approval

First-line support that follows your troubleshooting guide
Slow internet, no signal, a decoder that won’t start. The agent walks the customer through your approved steps, checks known outages and schedules a technician when the steps run out.
- Guided troubleshooting from your playbook
- Checks against known outages
- Technician visit requests
- Handoff with the steps already tried

Billing questions explained line by line
The agent explains charges from the account data, sends copies, shares payment options and opens a review when the customer disputes a charge. Credits and adjustments wait for approval.
- Bill explanations from account data
- Bill copies and payment options
- Dispute requests opened
- Approval for credits and adjustments

Plan changes and portability requests prepared complete
The agent explains the options your rules allow, collects what each change requires and prepares the request. Changes to the contract or the customer’s data need a person’s approval.
- Plan options within your rules
- Portability document intake
- Request prepared for your team
- Approval for contract changes


An internet provider whose support line stops repeating itself
A regional internet and pay TV provider answers thousands of support contacts a month. Most follow the same troubleshooting guide, and many end in a technician visit that a restart would have avoided.
- A workshop with customer service and field operations picks the first workflow: first-line internet support.
- The team shares its troubleshooting guide and the outage list the network team already maintains.
- The agent answers on WhatsApp and web chat, checks for known outages, walks the customer through the guide and schedules a visit when the steps run out.
- Billing questions are added next, answered from the account export with any credit sent for approval.
What changes
Customers get help at any hour, technicians are sent when they are actually needed and support agents receive cases with the steps already tried. Every conversation is on the record for the managers to review.
Example scenario with Chucao Telecom, a fictional company. It shows how an agent would work, not a customer result.
Why Baguals.
Your troubleshooting guide, applied every time
The agent follows the steps your team approved, in order, and never improvises a fix. When the guide runs out, a person takes over with full context.
Contract changes need a human yes
Changing a plan, a contract or customer data is a sensitive action. By default a person approves it, and every step lands in a log that can’t be edited.
Documents processed, not retyped
IDs, contracts and portability forms are read and checked by the agent, with every field traceable to the original and anything doubtful sent to a person.
A future-ready operation
Your teams keep their systems and routines. We prepare the operation underneath so agents can take the repeated contacts without forcing anyone to change.
Solutions for this industry
Questions, answered.
Can the agent fix technical problems on its own?
It guides the customer through the steps your team has approved, such as restarting equipment or checking connections, and checks whether there is a known outage. It doesn’t make changes to your network. When the steps don’t solve the problem, it schedules a visit or hands the case to a person with everything already tried.
Can it change a customer’s plan?
It can explain the options your rules allow and prepare the request with everything required. Changing a plan or contract touches the customer’s data and billing, so it is a sensitive action and, by default, a person on your team approves it before it is applied.
How does it handle identity documents?
The agent reads IDs and contracts to check that a request is complete, and shows how sure it is about each field. Passwords, keys and card numbers are filtered out and never stored. Each company runs isolated from the others, with data in São Paulo.
Which channels does it support?
WhatsApp, web chat and email are the usual starting point. Voice can be added when your operation needs it, and if a call is recorded the customer is told first. Slack and Teams are available for internal workflows. Every channel follows the same rules and lands in the same record.
How do we start?
With a workshop with your leadership to pick one workflow, often first-line technical support or activations. We build it on your troubleshooting guide and exports, agree on a metric upfront and get it running in weeks. Then we add the next workflow.

