Yes. Map tier breakpoints (600 kWh, 2,000 kWh) and summer and winter demand charges as postmeta. Ratepayers describing a high bill get real math: 1,840 kWh at tiered rates plus a 4.2 kW demand peak at 9.4 cents equals $234 in energy plus $39.48 demand plus the basic charge, not 'usage went up'.

Yes. If your outage map publishes a JSON feed, SleekAI ingests it on a short cache (30 to 120 seconds) and the bot quotes the affected area, customer count, cause if posted, and the current estimated restoration time. During storm events that cuts dispatcher call volume by half and keeps the line free for actual downed-line reports.

Each rebate is a custom post with eligibility rules (residential, low-income, electric heat only, HOA approval needed) and amounts. The bot asks the ratepayer's situation, surfaces the programs that match, and links to the application form. It will not promise approval, only eligibility based on published criteria.

Yes. Net metering rules, interconnection thresholds (under 25 kW expedited, over 25 kW Schedule 8 study), avoided-cost versus full retail credit rules, and annual true-up dates each live as posts or meta. Solar customers get accurate answers about credit carryover and the bot routes installer questions to your interconnection email.

Yes. The bot walks ratepayers through the move-in or move-out flow: address verification against the service area boundary, deposit amount based on credit class, autopay enrollment, ID upload, and expected connect-by date from your service crew schedule. It hands off to the secure form for any step requiring PII.

Each commission meeting is a post with agenda items, packet PDF, public comment sign-up link, and recording URL. The bot quotes the next meeting date, lists agenda items by topic (rate case, capital plan, IRP), and points ratepayers to the docket and the sign-up form for live public comment.

By policy, the bot only quotes published material. It does not access individual account data unless you separately integrate with your CIS through an authenticated endpoint. Conversation logs are retained per your records retention schedule and exportable in response to public records requests. PHI and PII are redacted by default.

Yes. Each territory or member utility is a taxonomy term. The bot asks the ratepayer's address or account number, maps it to the right rate schedule, outage feed, and rebate catalog, and quotes the rules that apply to that territory. Joint-action members can share one bot with territory-aware routing.