How to Automate ConnectWise

Every hour an MSP sells starts life as a ticket

ConnectWise is the platform most managed service providers run their business on, and it is really several products under one name. PSA is the one people mean first, and it is old enough that plenty of engineers still call it Manage. Around it sit RMM and ConnectWise Automate for monitoring and managing endpoints, ScreenConnect for remote access, CPQ for quoting, WisePay for billing, BrightGauge for dashboards, SmileBack for customer feedback, and a security range covering SIEM, managed EDR, backup and vulnerability management.

PSA is where the money is made and lost. A ticket comes in, gets prioritised and worked, and the time entry on it either falls inside an agreement or gets billed. Projects, procurement, opportunities and the invoice all hang off the same record.

That means an MSP's whole commercial picture, what a client costs to serve and what they pay, is assembled from tickets. Which is why the parts that never become a ticket are the ones that hurt.

The queue is tidy, the vendor portals are not

A well-run service board looks under control. The work that never reaches it is what an account manager does on a Thursday with fourteen tabs open.

The failed switch at a client site may be under warranty, and only the manufacturer's own lookup page knows. The replacement is quoted at a lead time somebody guessed, because the distributor's stock page has to be checked by hand. Three tickets have arrived from one office and the honest answer might be on the ISP's status page. A client's domain and its certificate expire on a registrar nobody has signed into since onboarding. The licence count moved at the last renewal and the partner portal has the real number. The quarterly review deck is due Friday and half of what goes in it is not in any system you control.

None of that is difficult. All of it is a person, a login and a copied number.

ConnectWise

Warranty dates against the assets you manage Each manufacturer's own lookup checked for the machines on a client's list, so the replacement conversation starts before the failure.

Lead times before a date is promised Distributor stock and shipping estimates read before a quote goes out, so nobody commits a client to a switch that is eight weeks away.

Renewal dates nobody is watching Certificates, domains and licence counts read from the registrars and vendor portals that hold them, well ahead of the date.

ConnectWise RPA clicks the buttons it has been integrated with

ConnectWise automates a great deal of the MSP's own operation, and an MSP not using it fully has cheaper wins available than anything on this page.

PSA handles automated ticket intake and prioritisation, SLA tracking and automation, time tracking by client and project, procurement, and recurring agreement billing that runs without being started each month. ConnectWise RPA puts bots on the repetitive work, the button clicks and text box fills that used to need a technician, and those can be triggered from inside a PSA ticket. BrightGauge turns the result into dashboards, and SmileBack collects a rating when a ticket closes.

RPA is the interesting one, because it is genuinely the right idea: let something else do the clicking. ConnectWise says it automates across the products integrated with its platform, which is a real reach and a real boundary at the same time.

A manufacturer's warranty lookup is not integrated with your platform. Neither is a distributor's stock page, an ISP's status page, a registrar's expiry date or a client's landlord. None of them have any reason to integrate with an MSP's PSA, and none of them are going to.

Distributor stock and warranty dates belong on the ticket

A ticket is only as good as what the engineer knew when they opened it. The facts that decide how it goes are on other companies' websites, and they can be read on a schedule rather than when somebody remembers.

Warranty end dates read off each manufacturer's own lookup for the machines on a client's asset list, so the refresh conversation happens at the right time rather than the morning a laptop dies. Distributor stock and shipping estimates checked before a quote commits anyone to a date, so a promise is made against what is actually available.

The ISP's status page opened the moment several tickets arrive from one site, so the first reply says what is happening instead of asking the client to reboot the router. Certificate and domain expiry read from the registrars that hold them, listed by client, months ahead. Licence counts and renewal dates pulled from vendor portals before a renewal quietly rolls.

The numbers a quarterly review actually turns on, gathered from the places that hold them, so the meeting is prepared rather than assembled the night before.

The only integration these portals will ever get is a browser

That is the whole gap. The information is public or you already have a login for it, and there is no connector because there is no commercial reason for anyone to build one.

WebRun works those sites the way an engineer does. It drives a real browser, signed in with credentials you control, on a schedule, inside a policy that names which sites it may reach and what it may type. Nothing needs an API, nobody writes a script, and it does not care how old the distributor's portal is.

It also stops where it should. A ticket note, a client email or a renewal quote is prepared and left for a person, because the client relationship is the product. The reading runs unattended, the sending does not.

The cards below are the jobs service teams hand over first.