Moodle installations vary a great deal, with different plugins and versions, so each connection starts with a look at how yours is set up. The agent reads what it is allowed to see before it acts, so its replies match what your team would find if they looked themselves.
An agent could help learners find the right resource in a course, answer questions from the course material and flag a learner who has not been active. A tutor could use your content as its source. Where an action changes a record that matters, such as a grade or a place, the step can wait for a person to approve it.
Most delays come from not knowing exactly what is installed. Moodle sites differ by version, theme and plugins, and a connection that works on one site may need adjusting on another. Sharing those details at the start, along with who maintains the site, lets us plan the test properly and avoid surprises later.
Because setups differ, we test against your real instance and confirm what is possible on the discovery call rather than assuming standard behaviour. Decide who maintains Moodle, since updates to plugins can affect a connection. Keep write access narrow at the start. If your Moodle is hosted by a third party, they may need to approve access too, so ask early.