The deal and the development roadmap
MSP Process announced September 22 that it acquired Triggr, adding service-desk automation to its identity-verification and communications platform. Financial terms were not disclosed. The company says it will continue supporting existing Triggr customers while progressively integrating capabilities. Its announcement describes Triggr Core and Studio, and a natural-language control layer, Triggr OS, that remains in development. Customers should distinguish that roadmap from capabilities available for immediate use.
Faster service raises an authorization question
The buyer presents the combination as a way to reduce repetitive work and improve service delivery. Those are company expectations, not performance results independently measured by this publication. Our analysis is that the most useful evaluation would follow a complete request from arrival to closure. Who is asking? What change is permitted? Which system carries it out? Can a technician explain the result? A smooth conversational interface should not make those decisions harder to inspect.
What small-business clients should ask
A small business should ask its MSP which requests may be fulfilled automatically and which require an authorized approver. A professional-services client may want different controls for access to shared client files than for a routine software request. We recommend agreeing those distinctions before introducing new automation. This gives the provider a clear operating boundary and gives the customer a way to understand what service has been delegated. It also avoids treating every employee’s request as permission to change a sensitive account.
Use a pilot with an exception path
Providers assessing the combined offering should test an ordinary request, an ambiguous request and a request that must be refused or escalated. Use an approved test environment and record the evidence created in each case. Ask how the system behaves when verification fails or a connected service is unavailable. A credible demonstration should show what the automation stops as clearly as what it completes. For clients, the outcome worth buying is consistent, explainable service—not simply a shorter conversation before a change is made.
Sources & further reading
Our practical suggestions are editorial guidance. Verify applicability against current source and vendor instructions.
