When you are deciding which tools you keep
What GoTenix runs itself and what it connects to
GoTenix runs the work of your service desk itself, from tickets and time to device terminals and billing, and connects to the tools you already trust for accounting, screen control, documentation and Microsoft 365.
Browse
On this page
How to do it
Start with what runs inside GoTenix.
The service desk is yours end to end: tickets, boards, dispatch, SLA clocks and the time your techs capture as they work. Billing runs here too: the agreements and plans you sell, quotes, and invoices that are generated, approved and sent. For every managed device, the portal has a live terminal, saved scripts, patching, a software inventory and a Files tab. Your users get a Get Support page to raise a ticket. Elise, the assistant, works across the same records.
Connect your accounting software at the invoice.
Accounting is its own discipline: tax rules that change by place and year, payroll, purchasing, an audit trail your accountant has to defend. So GoTenix runs the operating side and QuickBooks Online stays your book. Customers, invoices and estimates are pushed to QuickBooks, and payments are pulled back from it every five minutes. Once QuickBooks is connected it owns tax, so any local tax rate is set to zero and you work with its tax codes instead.
Note: A client card payment that GoTenix collects through autobill is recorded into QuickBooks against the invoice.Bring a screen control tool you already like.
A screen session is its own product, built by companies that do nothing else. So GoTenix does not include screen control of its own. Splashtop Business is connected: turn it on under Integrations, then Remote Access, and the Control column on RMM, then Devices opens that device in the technician's own Splashtop Business app. The agent reads Splashtop's registry on the device, so no Splashtop password is stored. If you use ScreenConnect, you open it the way you do today; there is no launch for it inside GoTenix.
See where each kind of record comes from.
GoTenix reads each record from the system that owns it. Clients, contacts, tickets, replies and logged time come from Autotask or HaloPSA when you are switching. Invoices, customers and estimates sync with QuickBooks Online. Devices come from the GoTenix agent, and from NinjaOne where a shop already runs it. Microsoft 365 connects your tenant for client tenant sync and security monitoring. IT Glue and Hudu bring in documentation and passwords. ThreatLocker brings in application control. Pax8 brings in purchased seat counts and partner cost per client. Dell, Lenovo and HP warranty lookups fill in warranty dates. Mail connects through Microsoft 365 or forwarded mail.
Reach anything else with a webhook.
On the Webhooks card, New Webhook sends an HTTP POST to a URL you choose when the events you pick occur. A call to a generic endpoint carries a signature header you can verify, and Slack, Discord and email destinations are supported too. An endpoint that fails ten times in a row is switched off, so a dead endpoint never becomes a retry pile nobody reads.
Using a tool or platform we don't integrate with yet? Contact us because we want to add more integrations.
Write to [email protected] and name the tool and what you need to move. If it has an API, we can get your data out of it.
The pages behind each click
What you will have
- See what stays inside GoTenix: tickets, time, quotes and invoices, and for devices the terminal, scripts, patching, inventory and files.
- See what GoTenix connects to, and which system owns each kind of record.
- Know where the line sits with your accounting software, and what crosses it.
- Get a straight answer you can forward to a partner or an owner without editing it.
Why it works this way: What GoTenix runs itself and what it connects to
A platform that rebuilds what another system already does well hands you two copies of the same records and a reconciliation job nobody asked for. The system that owns a record should keep owning it, and the platform should read from it.
Every boundary on this page has a reason, so you can weigh it before you commit instead of meeting it in month three in front of a client.
A boundary is not a refusal. If a tool you use is not connected yet, the last step shows how to ask.
Was this helpful?