Commusoft + Memtro

Only when you ask, and only what it has been granted: create a customer; add a contact to a customer or work address; create a job; edit a job's notes, reference, quote or priority; mark a job complete; move a job to another stage; put a job on hold; take a job off hold; close a job free of charge; abort a job; delete a job (permanent); book an appointment for an engineer; delete an appointment (permanent); create an opportunity; move an opportunity to another stage; complete a scheduled activity. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.

A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.

Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded. An hourly sync anchors recently changed Commusoft records into memory as entities.

API key and region. In Commusoft, an administrator opens Settings → Private applications, creates a private application and copies its API key. Use a production key, since sandbox keys work only on a sandbox.

Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Commusoft, choosing the same kinds; the tab shows Commusoft's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.