"Why is my bill so high?" and "please change my bank details" look alike in the inbox and carry very different risk. The first is an explanation every customer should get quickly. The second is an account change that only the verified account holder may make. An AI concierge connected to your billing system, CRM and portal can explain a bill from the customer's own data and make the changes you allow, after your systems have verified who is asking.
Below, stage by stage: what households, business customers and installers need, what we've learned from conversations with utilities, and how Typewise fits the systems you run today, including while some of them are being replaced.
- General questionsTariffs and processes"How do I apply for a new connection?"
- Understand the billHigh bill, consumption"Why is my bill so high this month?"
- Change the accountPayment and contact details"Please update my bank details."
- Professionals and partnersInstallers, inspectors, business customers"What do I need to submit for the meter installation?"
How the concierge works with your billing system, CRM and portal
Typewise doesn't replace your billing system, CRM or customer portal. It connects to them and keeps three things apart.
Information. Public answers come from your website, documents and knowledge articles. Each source has an access level, so internal material can help your team without being shared with customers. Billing, consumption and payment data come through lookups from systems you connect through an MCP server, or through Salesforce or Zendesk where the data already sits. See the integrations for what is available.
Actions. Account changes run only as actions you configure one by one, with approval by a person on by default. Their customer input can be limited to verified values: a customer signed in to your portal, an email address confirmed with a one-time code, or the phone number on WhatsApp. Without a verified value, the action doesn't run.
Handoff. Collections, disputes and technical approvals go to the team that owns them, with the conversation history and a summary, in Typewise or in the helpdesk you already use.
- Reads tariffs and processes for everyone, billing and consumption data for a verified customer
- Acts only for a verified account holder, where a system offers the change and you allow it
- Hands over collections, disputes and technical approvals to the owning team
- Website and process documentspublic informationReads
- Billing systemconfirmed for your product and versionReadsActs
- CRMfor example SalesforceReadsActs
- Customer portalsigns customers inReads
- Service, collections and engineering teamsin Typewise or your helpdeskHands over
Your admins set this up: which Specialist handles which topic, which lookups and actions it may use, and when it hands over. Nova, the AI Operator in Typewise, can draft that configuration with them. Its changes stay drafts until someone publishes them, and Nova never writes to customers. The concierge your customers talk to is the AI Agent.
What utility customers need, and how the concierge handles it
1. Can an AI answer utility customers' general questions?
Yes, from approved public information: tariffs, processes, what a letter or notification means, how to apply for a connection. None of that needs an account.
What we've learned. A new channel isn't an improvement if it adds an unresolved contact. Before you open it, check that the first questions can actually be answered from the sources you connect. A portal full of good information can still go unused, so a conversational answer that points into it can help.
In Typewise. The concierge answers from your website, documents and knowledge articles, in the customer's language. Give every source an owner who keeps it current.
2. Can the AI explain a customer's bill?
For a verified customer, yes: from billing and consumption data, in plain language, before the question turns into a dispute.
What we've learned. Treat a high-bill question as an explanation workflow, not only a payment transaction. And confirm the exact billing product and version behind any integration early: one vendor name can cover several billing products.
In Typewise. Connect a billing lookup and map its customer input to a verified value. Payment reminders follow the same pattern: with payment status connected, the concierge can explain where a payment stands and which options your policy offers. Adjustments, goodwill and payment arrangements follow your policy and your approvers.
3. Can the AI change account details?
Only the changes you configure as actions, and only for a customer your systems have verified.
What we've learned. Decide what happens when one email asks for a supported change and for something else. And test every connector with the parameters production will use: an internal test with the wrong parameters doesn't prove readiness.
In Typewise. Each action has its own approval setting, on by default. The concierge handles the supported part of a request and passes the rest to a person with the conversation attached. Where no integration exists yet, it collects what the change needs and raises a manual action for your team.
4. How does the AI help installers and business customers?
They ask different questions from households: process requirements, documents to submit, the status of a request. The concierge can answer from process information and take the request in, so the responsible engineers receive it complete.
What we've learned. Treat professionals as their own audience, with their own process information and an intake destination the engineers actually work in.
In Typewise. A Specialist per request type collects what the engineers need, and web forms reach the concierge through the Form API. Technical approvals and connection decisions stay with the responsible engineers.
What to check before each stage goes live
Each stage depends on different data and a different owner. Map platform ownership first: who owns the CRM, the billing system and the portal decides what the concierge can reach.
| Stage | What the concierge needs | Who may own it | Check first |
|---|---|---|---|
| General questions | Approved public sources | Communications and service | Who keeps each source current? |
| Understand the bill | Billing and consumption data for a verified customer | IT and billing | Which billing product and version, and how is the customer verified? |
| Change the account | A write path for each change in scope | IT | Which changes, with which parameters, and what happens with mixed requests? |
| Professionals and partners | Process information and an intake destination | Engineering | Where do the engineers work on incoming requests? |
When your team takes over, the case continues
The handover carries the conversation history and a summary, so the colleague who takes a dispute or a payment arrangement doesn't start again. Support from the service department doesn't grant authority over a platform: agree access with whoever owns the CRM, billing system and portal before you plan the first stage.
Our article on AI agent permissions covers how to decide which account changes to allow.
How to start
Split the evaluation: let the business owner judge value and IT judge fit with the technology strategy, with a shared rubric so neither decides alone. Write down who edits what: your service team can change instructions and Specialists, with Nova drafting them, while integrations and data access stay with IT.
If your billing system is being replaced, start with general questions and explanations that don't depend on it, and keep account changes for after the migration. Report only what people can use: a dashboard that shows features staff can't access invites justified challenges, and inferred sentiment isn't surveyed satisfaction.
Common questions
Does Typewise integrate with our billing system?
If your billing system offers an interface, it connects through an MCP server, or through Salesforce or Zendesk where the data already sits. Confirm the exact product and version early: one vendor name can cover several billing products. What the concierge can do then depends on the operations the system offers and the ones you allow.
How does the AI know who it is talking to?
Account lookups and actions take their customer input from verified values only: a customer signed in to your portal, an email address confirmed with a one-time code, or the phone number on WhatsApp. Without one, they don't run, and the concierge answers from public information or hands over.
Our billing system is being replaced. Should we wait?
You can start with general questions and explanations that don't depend on the changing system, and add account changes after the migration. Map platform ownership first, so the first stage isn't blocked by a system in transition.
Can the AI handle late-payment questions?
With payment status connected for a verified customer, it can explain where a payment stands and which options your policy offers. Collection decisions and exceptions stay with your team.
