Customer Documentation · Getting Started

MyOpsAgent Customer Onboarding Guide

MyOpsAgent works best when onboarding starts with a real business problem rather than an attempt to automate everything at once. This guide explains a safe, practical route from first configuration to live use.

1. Choose the First Useful Outcome

Start with one clearly defined use case, for example:

  • answering common customer questions from approved information;
  • helping staff find company procedures or technical knowledge;
  • handling bookings or another repeatable customer workflow;
  • connecting an internal business system for a defined question or action; or
  • modelling a controlled operational process in the Operations Centre.

Define what success means before enabling more capability. A focused first use case makes access, testing and governance substantially easier.

2. Add Approved Business Knowledge

Provide the information the agent is allowed to use for the chosen task. This may include public website content, FAQs, service information, policies, procedures, product documentation or other organisation-approved material.

Keep authoritative source material current. MyOpsAgent should not be used to compensate for conflicting or obsolete source documents.

3. Define Who Can Access What

Decide whether the first capability is public, customer-specific or internal. Public visitors should receive only information and actions intentionally exposed to the public. Internal users can be given a wider view according to identity, role and organisation policy.

  • Separate public and authenticated use cases.
  • Grant the minimum information and actions required.
  • Do not make an internal capability public simply because it is convenient to test.
  • Use approval gates where a person must remain accountable for the final decision.

4. Configure the Agent Experience

Configure the organisation's agent identity, greeting, supported prompts and public presentation. The agent should make the scope of what it can do clear rather than implying access to information or actions that have not been enabled.

5. Enable Only the Required Modules & Tools

Add the capabilities required for the use case, such as bookings, connected knowledge, operational tools or a custom integration. Tool access should be deliberate and organisation-scoped.

A module may make a capability available, but identity, permissions and workflow rules can still limit who is allowed to use it.

6. Connect Business Systems Where They Add Value

Keep existing systems that already perform their job well. Integrate only the context or action required to close the business gap you are solving.

  • Use server-side credentials for server integrations.
  • Use domain restrictions for browser-facing deployments where supported.
  • Test read operations before enabling write operations.
  • Confirm which system remains authoritative for each type of data.

7. Model Rules & Operational State When Required

For controlled operational decision workflows, add the relevant work, people or assets, capabilities, constraints, dependencies and current state. The platform can only evaluate consequences accurately when the underlying business model reflects reality.

Distinguish hard constraints from preferences. A hard rule defines an invalid outcome; a preference helps rank valid alternatives.

8. Test Before Going Live

Test the complete workflow, not just whether the agent produces a convincing answer.

  • Ask normal questions and ambiguous questions.
  • Confirm that unauthorised information is not returned.
  • Test unavailable resources, conflicting constraints and incomplete data.
  • Verify that approval is required where expected.
  • Confirm whether an action was actually executed rather than merely described.
  • Check that the resulting business state matches the approved action.

9. Go Live in a Controlled Scope

Release the validated use case to the intended audience, monitor the questions and workflows users actually bring to it, then improve the source information, rules or integration where evidence shows a need.

10. Expand Only When the First Capability Is Working

Add additional departments, modules, tools or connected systems when the existing capability is delivering useful results. MyOpsAgent is designed to expand around the business rather than requiring a large replacement programme on day one.