CarrierAutomate integration

Granite repair tickets opened by API, not by phone

The SmartTile Granite Telecom integration opens the repair ticket the moment a Granite circuit is confirmed down, then keeps Granite’s status and notes in step until it closes.

SmartTile CarrierAutomate view of active Granite repair tickets opened by API and the API activity log syncing Granite status to Rev.io (sample data)
Seconds
To open the repair ticket by API
0 calls
Placed to Granite when the API works
30 min
Granite status and notes pulled automatically
10 tries
Failed attempts before a live engineer takes over

Carrier repair still runs on hold music.

When a Granite circuit drops, someone calls Granite, finds the child account, reads out the circuit and site contact, then calls back for updates. SmartTile opens the ticket through your own Granite API credentials, with no call placed.

What your team gets from the Granite Telecom integration

Repair tickets in seconds

On a confirmed outage, SmartTile opens the Granite repair ticket over the API. No phone call, no portal login.

Everything Granite needs, sent once

Summary, circuit, site address, outage time, the SmartChoice reference and the on-site contact.

The ticket number, logged for you

Granite’s ticket number is written to the SmartChoice ticket as an internal note, automatically.

Updates without calling back

Every 30 minutes SmartTile reads Granite’s status and notes, and posts them only when something changed.

A fallback that never drops the ball

If the API fails, SmartChoice’s voice agent calls Granite with the same details. Ten failed tries hands it to a live engineer.

Your credentials stay yours

Granite issues API credentials to you. They stay encrypted on your own SmartTile instance.

See how each of these works in the technical overview

What changes for a Granite circuit

The moment Today With SmartTile
A Granite circuit goes down Someone calls Granite, finds the account, reads out the circuit. The ticket opens by API with circuit, address, outage time and site contact.
The ticket number Copied by hand into the internal ticket. Written to the SmartChoice ticket automatically.
Keeping up with Granite Call back, or log in to the portal. Status and notes pulled every 30 minutes, posted only when changed.
The API has a bad day No plan B. The failure is logged and a voice call is placed instead.

Why IT leaders add it to their stack

CIO

Carrier repair without adding staff

Tickets open and update themselves, so your team works the fix, not the phone.

CTO

Granite’s customer REST API

Okta OAuth2 client credentials, held on your own SmartTile instance.

CISO

Credentials never leave your instance

Your Granite client ID and secret stay encrypted on your SmartTile. The platform only sees the answer.

IT director

No hold music, no portal logins

Every Granite outage is ticketed, numbered and tracked automatically.

Live with your Granite credentials

  1. 1
    Get your Granite credentials
    Your Granite account team issues an Okta client ID, secret, token URL and scope.
  2. 2
    Enter them in SmartTile
    On your own SmartTile, under CarrierAutomate and Granite.
  3. 3
    Run the Data Sync Test
    Confirms ownership of the circuits, a valid token, and a ticket read-back.
  4. 4
    Go live
    API-first is on by default.

API-first is on by default, and three switches stay in your control: API first, voice fallback and a kill switch.

Security and control

Credentials never leave you
Your client ID and secret stay on your SmartTile, encrypted at rest, with the token cached encrypted too.
Three switches
API first, voice fallback and a kill switch, plus the 30-minute update switch.
Nothing lost, nothing spammed
Every journal post is audited, and a note is posted only when Granite’s status or notes changed.
Failures counted
Each failed API attempt counts toward the hand-off to a live engineer.
SMARTTILE · CARRIERAUTOMATE
Granite Telecom technical overview

Learn exactly how it works

The two-page technical overview lists every Granite API call SmartTile makes, how your Granite credentials stay on your own instance, and what happens when the API has a bad day.

Read the technical overview

Granite Telecom integration FAQs

Does SmartTile close the Granite ticket?

No. Closing isn’t part of this integration. SmartTile records when Granite reports the ticket closed.

Does Granite push updates, or does SmartTile check?

SmartTile checks Granite every 30 minutes and posts updates when something changed.

What happens if the Granite API is down?

SmartChoice’s voice agent calls Granite with the same details, and the log says why the API wasn’t used.

Why does Granite repair ticket automation use our credentials?

Granite issues API credentials to the end customer, not to SmartChoice. They stay encrypted on your own SmartTile instance.

Which other carriers can SmartTile ticket with?

Verizon (beta), plus ticket clients for Lumen, Zayo and Spectrum, and portal automation for carriers without an API.

The Granite ticket is open, numbered and logged before anyone would have finished dialing

See carrier ticket automation in a 30-minute demo.

Protected by VPNGuard