Developer Tools
Geotab MyAdmin
Connect your AI to Geotab MyAdmin
Geotab resellers, fleet managers, and billing administrators run device contracts, billing plans, and add-in enrollment through Geotab MyAdmin, but the answers they need sit across contracts, monthly billing runs, and databases that MyAdmin shows one screen at a time. AI can pull them together in seconds, but only if it stays inside the account it is signed in to and confirms before it changes a plan, terminates billing, or enrolls devices.
Why it matters
Capabilities that matter most for Geotab MyAdmin
01
Contracts and billing in one view
Join device contracts, billing plans and monthly billing runs into one list, instead of reading MyAdmin one screen at a time.
02
Billing beside accounting
Join MyAdmin billing with your ERP or accounting lists to reconcile what Geotab charged with what you invoiced.
03
Confirm before changing devices
AI tools stay inside the signed-in account and change plans, billing or enrollment only through approved actions.
Use cases
Example AI Use Cases for Geotab MyAdmin
scenario
-
Updating a group, promo code, comment or contact on many Geotab contracts at once is a form with paired switches: each value only applies when its update flag is on. Miss a flag and nothing changes, set an extra one and you blank a field on every device.
What popdock provides
--
Give the serials and describe the change in plain words. It reads each contract, skips devices not found or terminated, and maps your change to exactly the fields it needs, leaving every other field alone. You see old and new values per field before anything is saved. After you confirm it updates all the devices in one change and reads the first contract back to show the result.
Business outcome
---
Contract details change on every listed device in one confirmed step, with no fields blanked by mistake.
scenario
-
Blocking, deactivating or changing auto-enrollment on a Geotab add-in affects every enrolled device on that database, and the IDs it needs are spread across MyAdmin. A change made on the wrong installation is a support incident for a customer who did nothing wrong.
What popdock provides
--
Name the add-in and the change: block, unblock, deactivate, turn auto-enroll on or off, or add or remove auto-enrollment groups, with the database and group IDs where needed. It resolves the installation and account ID, shows the current state and what the change will do, and warns when it stops the add-in for every enrolled device. After you confirm it makes the one change and reads the installation back.
Business outcome
---
Add-in settings change on the right installation, with the impact understood before it happens.
scenario
-
When devices drop out of an add-in or get enrolled by mistake, the first question is who did it and when. The MyAdmin audit log has the answer, but reading it raw across databases and users is slow, and a bulk change by one person is easy to miss.
What popdock provides
--
Give a date range, the last 7 days by default, and optionally part of a user name or email. It reads the add-in audit log and reports totals by action, by user and by database, then the full list newest first with date, action, device and user. It points out bursts where one user changed more than 20 devices in a day. It only reads.
Business outcome
---
You know who changed add-in enrollment, when and on which devices, with bulk changes called out.
scenario
-
An add-in can be installed on several databases, each with its own enrolled devices, monthly fees and auto-enroll setting. Answering how many devices use it and what it costs means visiting each installation, then digging through the audit log to see who changed what.
What popdock provides
--
Name an add-in and optionally how far back to look, 30 days by default. It finds every installation of that add-in with its database, status, solution ID, auto-enroll and enrolled count, totals the monthly fees of the enrolled devices by currency, and lists recent enroll and unenroll activity with who did it. If the name matches several add-ins it lists them and stops. It only reads and never blocks, deactivates or unenrolls anything.
Business outcome
---
You see where an add-in runs, what it costs each month and how enrollment has changed, in one answer.
scenario
-
Scheduled device plan changes in MyAdmin can fail quietly or sit unprocessed for weeks. Unless someone reads the auto-request history and checks each error and processed date, the customer finds out first, when the plan they expected never took effect.
What popdock provides
--
Give a lookback window, 30 days by default, and optionally a status. It reads the device-contract auto-requests in that window and sorts them into failed (an error was returned), stuck (active, unprocessed and over 7 days old) and done. You get counts per class and status, a table of the failed and stuck ones with serial, plan, dates, requester, reason and error, and a suggested next check for each failure. It only reads.
Business outcome
---
Failed and stuck plan changes are found and listed before customers notice them.
scenario
-
Billing errors in Geotab hide in the volume: a device charged far more than usual, a terminated device still being billed, a credit with no charge behind it. Finding them means cross-checking contract, charge and credit exports by serial number, which rarely happens every month.
What popdock provides
--
Name a month and a charge threshold, or accept the current period and a default of 100. It lists the high charges, compares terminated contracts with the month of charges to find devices billed after termination, and finds credits with no matching charge. Each finding comes with the serial and amount, a count per table and a note on which look worth disputing. It flags rather than concludes, and it only reads.
Business outcome
---
Billing problems that would slip through a month end are listed by device, ready to check or dispute.
scenario
-
Customer records in MyAdmin drift over time: a primary contact with no email, a missing tax ID, an address without a country, the same company entered twice under slightly different names. Nobody checks until an invoice bounces or the wrong account gets the call.
What popdock provides
--
Optionally name a country, and choose active customers only, the default, or all. It reads the customer records and flags each one missing a contact email, phone or name, city, state or country, or tax ID, plus legal names that differ from the company name only by case or punctuation. You get counts per rule, a table of accounts and their issues, and likely duplicates. It only reads and never edits a customer.
Business outcome
---
Incomplete and duplicate customer records are listed in one pass, ready to clean up.
scenario
-
Knowing what is in a MyGeotab database means combining several MyAdmin views: which devices report there, which contracts point at it, which devices are shared out and which add-ins are installed. When those lists disagree, nobody notices until a customer asks why a vehicle is missing.
What popdock provides
--
Name a database and it lists the devices reporting to it and the contracts assigned to it, the devices shared out to other databases, and the add-ins installed with their status and enrolled counts. It reports counts by device plan, device type and termination, and lists devices that appear in one list but not the other. It only reads, and if no device is found it asks you to check the name.
Business outcome
---
A complete, cross-checked picture of a database, including the mismatches that cause support calls.
scenario
-
When a customer calls about one device, you open its contract in MyAdmin, then the database it reports to, then its sharing, add-ins, pending plan changes and this month of billing, each on its own screen. It is easy to miss the one detail that explains the problem, such as a terminated contract that is still being billed.
What popdock provides
--
Give a device serial number and it gathers the contract, plan, device type, current database, owner and shared databases, add-in enrollment, pending or failed plan changes, recent add-in activity and this month of charges and credits into one profile. Every section that has nothing in it says so instead of disappearing. It ends with the red flags worth checking, and it only reads, so nothing in MyAdmin is changed.
Business outcome
---
One request gives you the whole story of a device, with the problems called out, in place of a dozen MyAdmin screens.
scenario
-
Early termination fees show up on the Geotab bill as a line per device, with no context. To know whether each one is fair you have to look up its contract, compare the termination date to the contract end and work out the months that were left.
What popdock provides
--
Name a month, or accept the current one, and it lists the early termination fees billed. For each fee it reads the device contract and reports the rate plan, contract start and end, termination date, months remaining and fee, then the total. It points out any fee charged on a contract that had already ended. It reviews up to 25 fees, the largest first, and only reads.
Business outcome
---
Each termination fee is tied to its contract, so questionable charges stand out before you pay them.
scenario
-
Closing a month of Geotab billing means exporting device charges, credits and early termination fees separately, then pivoting them by rate plan and database to see where the money went. Totals get mixed across currencies and a partial export is easy to mistake for the whole month.
What popdock provides
--
Name a month and year, or leave them blank for the current period, and optionally one database. It pulls the charges, credits and early termination fees for that period and reports the totals and the net, a breakdown by rate plan and by database, and the ten largest charges. Currencies are never added together, and if the data hits the record cap it tells you the totals are partial. It only reads.
Business outcome
---
A month of Geotab charges, credits and fees summarized by plan and database, ready for review, without spreadsheet work.
scenario
-
Checking whether a fleet qualifies for OEM data means collecting the VINs for a database, removing blanks and duplicates, and submitting them for an eligibility calculation. Submitting a batch before anyone has looked at the results wastes a request and confuses the customer.
What popdock provides
--
Name the database and region ID. It collects the distinct VINs of the devices in that database and calculates their OEM eligibility, which changes nothing. You get a table of VIN, serial and result with counts of eligible, ineligible and unknown. Only if you asked it to submit, and you confirm the list, does it submit the eligible VINs as a batch, and it asks before requesting manual support for the ineligible ones.
Business outcome
---
You know which vehicles qualify for OEM data before anything is submitted.
scenario
-
Enrolling devices in a Geotab add-in needs the solution ID, the database, the numeric account ID and the device serials, each found on a different screen. Pick the wrong installation or unenroll every device by accident and customers lose features they pay for.
What popdock provides
--
Name the add-in, enroll or unenroll, and the serials, or none to apply to every device, plus the database when the add-in is installed on several. It resolves the installation, solution ID and account ID from MyAdmin, skips devices already in the target state and shows you everything before any change, with a warning first if you are removing every device. After you confirm it makes one change and shows the audit log entries it created.
Business outcome
---
Devices are enrolled or removed on the right add-in installation, with the IDs looked up for you.
scenario
-
Changing a Geotab device plan by hand means checking each device first, skipping terminated ones, and making sure a scheduled auto-request will not undo the change. Done in bulk without those checks, devices land on the wrong plan and the bill is wrong next month.
What popdock provides
--
Give one or more serials, the new device plan ID and optionally a promo code. It reads each device contract, drops any that are not found or already terminated, skips devices already on the target plan and lists pending auto-requests that could override the change. You see a table of current and new plans and nothing changes until you confirm. It then makes one change, single or bulk, and reads the contracts back to show the plan now recorded.
Business outcome
---
Devices move to the right plan in one confirmed change, with conflicts and terminated devices caught first.
scenario
-
Opening a Geotab support ticket for a device means gathering its serial, VIN, plan, device type and database by hand and writing it all up, or support asks for it again. Adding an update to an existing ticket means finding that ticket and retyping the context.
What popdock provides
--
Give the device serial and describe the issue, and optionally an existing ticket ID. It gathers the contract and database details for the device and drafts a subject and body with the issue, serial, VIN, device type, plan, database and what has been tried. You confirm or edit the draft, then it opens one new ticket or adds one comment to the existing ticket and reports the ticket ID. It does not close tickets or attach files unless you ask.
Business outcome
---
Support cases arrive with the device details already in them, so nobody asks for them twice.
scenario
-
Placing a Geotab hardware order means matching each item to an exact product code, entering a purchase order number that has not been used, and filling in a ship-to contact. A wrong code or a reused PO turns into a returned shipment or a billing query.
What popdock provides
--
Describe the items and give the purchase order number. It matches each item to exactly one orderable product, asking when several match, and warns if the PO number is already in use on devices. It builds the order, asks for the ship-to contact if needed and shows you the complete order. Nothing is placed until you confirm, then it places one order and reports the result, including how to cancel it.
Business outcome
---
Hardware orders go in with the right product codes and an unused PO, after one review.
scenario
-
Logging a Geotab install after the job is easy to put off and easy to get wrong: the serial is mistyped, the asset number goes on the wrong device, or the odometer reading is missing. Bad install records make later support and billing questions harder.
What popdock provides
--
Give the serial, the asset number and optionally the installer and odometer reading. It checks the device exists and is not terminated, and asks if the odometer is not a number. You see the install details and confirm, then it logs the installation once and reports the result.
Business outcome
---
Installs are recorded against the right device while the details are fresh, in one short exchange.
scenario
-
Returning Geotab devices means checking each serial, choosing the RMA type and ship-to contact, and entering items, quantities and reasons line by line. Mistakes mean a rejected RMA, and returned devices keep billing unless someone terminates them.
What popdock provides
--
Give the serials, the reason, the RMA type ID and the ship-to contact ID. It reads each device contract and skips serials that are not found. You see the account, devices, reason, RMA type and ship-to before anything is created. After you confirm it creates one RMA for all the devices and reports the result, with a reminder that billing continues until the devices are terminated.
Business outcome
---
Returns are raised in one confirmed request, with a reminder that stops returned devices billing by accident.
scenario
-
When a Geotab device is terminated by mistake, someone has to confirm it really is terminated, cancel the termination and check it took. Cancelling against the wrong serial, or one that was never terminated, adds confusion to an already wrong record.
What popdock provides
--
Give one or more serials. It reads each contract and keeps only the devices that are actually terminated, telling you which ones are not. You see the plan and terminated date for each and confirm, then it cancels the termination once for the confirmed devices and reads the contracts back to show the status now recorded. It never terminates anything.
Business outcome
---
A mistaken termination is undone for exactly the right devices, and you can see that it worked.
scenario
-
Finding the right Geotab product to order means scrolling the MyAdmin catalog, guessing at names and categories and copying product codes by hand. A wrong code means a wrong shipment.
What popdock provides
--
Describe what you are looking for by name and optionally a category. It searches the products your account can order and lists them grouped by category with their product codes and a count. If nothing matches it tries again with a shorter search before saying so. It only reads and never places an order.
Business outcome
---
You get the right product codes for an order in seconds, without browsing the catalog.
scenario
-
Sharing Geotab devices into another database means checking the owner database for each serial, avoiding devices already shared there, and setting who pays and who controls the device. Get the transfer setting wrong and ownership moves when it should not.
What popdock provides
--
Give the serials and the database to share into, and optionally a plan ID. It checks each device owner database and existing shares, skips those already shared to the target and groups devices by owner. It asks who pays and whether control transfers, defaulting both to no, and shows the plan before anything changes. After you confirm it shares once per owner database and reads the sharing back.
Business outcome
---
Devices appear in the right database without ownership changing by accident.
scenario
-
Terminating billing for a Geotab device is quick in MyAdmin, but the impact is not shown: an early termination fee when the contract has months left, and add-ins that stop working. Terminate the wrong serial and it has to be reversed by hand.
What popdock provides
--
Give one or more serials, the termination reason ID and optional comments. It reads each contract, drops devices that are not found or already terminated, and shows the contract end date, months remaining and whether an early termination fee is likely, plus any add-ins that will stop. Nothing is terminated unless you answer yes. It then terminates once, single or bulk, and reads the contracts back to confirm the termination date.
Business outcome
---
Devices are terminated knowingly, with fee exposure and add-in impact seen before anything changes.
scenario
-
Editing a Geotab customer means finding the right account first, then sending the whole record back with the changes. Send a partial record and other fields can be blanked; pick the wrong account and the wrong customer gets the update.
What popdock provides
--
Name the customer by account number or company name and describe the change. It finds exactly one matching account, or lists the candidates and asks. It builds the update from the current record plus your change, so nothing else is blanked, and shows old and new values per field. After you confirm it updates the customer or the contact once and reads the record back.
Business outcome
---
Customer details change on the right account, without wiping the fields you did not touch.
No items found.
Ready to unlock your data?
Start building tools that turn your business systems into AI superpowers
Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.