SMARTTILE · CARRIERAUTOMATE™ · CARRIER PORTAL AUTOMATIONBETA

Carrier web portals — the rung between API and phone

For carriers with no ticket API, CarrierAutomate has a web-portal step: a headless browser that logs in to the carrier's portal, fills the trouble form and reads back the ticket number. It is BETA: built, reachable and switchable, but no carrier login is stored yet and the scripts have never run against the real portals — those carriers are called by Joey today.

SmartTile integrates with
Carrier customer web portals — navigation scripts for GTT and Windstream (Puppeteer headless Chrome, with a one-time code when the portal asks for MFA) — using portal logins SmartChoice stores encrypted, one per carrier.
How SmartTile automates it
Tier 1.5 of the CarrierAutomate ladder (API → portal → voice): log in, open the trouble-ticket form, fill it from the pre-call data package, submit, capture the ticket number — or fall through to Joey. BETA: off by default, no portal login stored, no portal ticket opened yet. Joey handles these carriers by phone.
Category
CarrierCarrierAutomate™

Some carriers never publish a repair API, but they all have a customer portal. CarrierAutomate's portal step uses it the way a technician would — sign in, find Report Trouble, type in the circuit, account and site details SmartTile has already gathered, submit, and bring back the ticket number. This page describes what is built and what it is waiting on. Until it is switched on and proven, Joey Circuits, our voice agent, opens and chases tickets with these carriers by phone — the live path.

What is built

Portal scripts

GTT and Windstream: login (entering a one-time MFA code when a seed is saved), open ticket creation, fill the form, submit, read the ticket number, and a read-only form check. Frontier's help-centre chat bot is not a portal and is left to Joey.

Ticket creator

Runs only when the switch is on and the carrier has a login that passed its test. Launches headless Chrome, runs the script with the pre-call data package, writes the ticket number to the carrier ticket, and journals every attempt. On failure it saves a screenshot.

Carrier portal logins

SuperAdmin panel on CarrierAutomate settings: add or replace a login, Test login (sign-in only), Check ticket form (reaches the form, submits nothing), use / don't use, last result — and the tier switch.

What it is waiting on — plainly

ItemState today
Portal loginsNone stored yet. The encrypted store and the SuperAdmin panel are live.
Proof against the real portalsThe GTT and Windstream selectors have never run against the live portals. Test login proves sign-in; the first real ticket proves the rest.
The tier switchacta.portal_tier.enabled — off by default, and it cannot be turned on until a saved login passes Test login.
Browser and hand-offBuilt: Puppeteer ships with SmartTile, and the ladder now reaches the portal step between API and phone.
Scheduled health checksOn demand per portal (Check ticket form); no daily schedule yet.
Sell the outcome that is live: for GTT, Windstream, Frontier and every other carrier without an API, Joey opens the ticket by phone, relays the circuit and site details, and captures the ticket number. Portal automation is the next rung, not today's promise.
SmartChoice · SmartTile CarrierAutomate™ — Carrier Portal AutomationPage 1 of 2
SMARTTILE · CARRIERAUTOMATE™ · CARRIER PORTAL AUTOMATION — HOW THE PORTAL STEP WORKS, AND HOW IT IS KEPT SAFE

The portal step, as built

  1. A circuit is confirmed down and the carrier has no working API path.
  2. SmartTile checks the tier switch and for an ACTIVE portal login for that carrier whose last test passed, then runs the pre-call data gate — nothing is typed into a portal with required data missing.
  3. Headless Chrome opens the carrier's portal and the carrier's script signs in, entering a one-time code if the portal asks and a seed is saved.
  4. The script opens the trouble form, fills circuit ID, account number and PIN, site and contact from the data package, and submits.
  5. The ticket number is read from the confirmation page and written to the SmartTile carrier ticket; the attempt is journalled either way. No number means no success — the ticket continues to Joey.

Security and control

Encrypted logins

Username, password and MFA seed are AES-256-GCM encrypted, each bound to its field. The API returns only set / not set — never a value — and error text is scrubbed of secrets.

SuperAdmin only, off by default

Only SmartChoice superadmins see or change portal logins and the switch. The switch refuses to turn on until a login passes, and the platform kill switch overrides it.

Fails toward a person

A failed login or changed portal marks that portal and stops the step; no ticket number means no success, and the ticket carries on to Joey.

Common questions

QuestionAnswer
Can SmartTile open a GTT or Windstream ticket on the portal today?Not yet — beta. The step is built and reachable, but no login is stored and it is switched off. Joey opens those tickets by phone today.
Whose portal login is used?One SmartChoice portal login per carrier. Per-customer portal logins are not supported.
What happens when a carrier redesigns its portal?The next Test login, form check or ticket attempt records LOGIN FAILED or PORTAL CHANGED with a screenshot, and the ticket goes to Joey.
No API? The portal step is built and waiting on its first login — and Joey already opens the ticket by phone.
SmartChoice · smarttile.smartchoiceus.com · (800) 217-3096, 24×7 · verified 2026-09-28Page 2 of 2