Get an answer. Then get back to work.

Start with one useful problem rather than trying to automate the whole business. A good first step might be answering customer questions, helping staff find information, or handling bookings.

Add the business information your agent needs for that task, check who should be able to access it, and only enable the actions required for that use case.

Your website can load the MyOpsAgent widget using the connection details created for your organisation. The widget sends conversations into your organisation's own agent context rather than a shared generic chatbot.

Your configured website domain, organisation access and enabled capabilities determine what the public-facing agent can use.

No. Conversation is simply the interface people use to interact with it.

Behind that conversation, MyOpsAgent can use company-specific knowledge, recognise the context of the request and, where you have deliberately enabled them, use approved tools or connected systems to complete useful actions.

You choose the information supplied to your organisation's knowledge library. This can include services, products, FAQs, policies, technical information, procedures and other material relevant to your company.

The aim is not to make the agent guess how your business works. You decide what information it should have available.

First check whether the correct information exists in the organisation's knowledge and whether it is clear enough to answer the question being asked.

If the information is missing or ambiguous, update the source material rather than relying on increasingly complicated prompt instructions. Clear business information usually gives the agent a better foundation.

No. MyOpsAgent is deliberately built around information you choose to provide and capabilities you choose to enable.

This gives you a much clearer boundary around what the agent should know and what it should be allowed to do.

Scheduling is built around the information required to make a real appointment: calendars, customers, services, staff, availability and bookings.

Once configured, the agent can use approved scheduling tools to check availability, create a booking and support common booking changes.

Where those scheduling actions are enabled for the organisation, the agent can use the appropriate booking tools to help retrieve, reschedule or cancel an appointment.

The available action depends on the capability and permissions configured for that organisation.

Yes. Public visitors and authorised users do not have to receive the same access.

MyOpsAgent can use the user and organisation context available to it to determine which information and capabilities should be exposed for that interaction.

MyOpsAgent is designed as a multi-organisation platform. Organisation context is carried through data access, conversations, enabled modules and tools so one organisation's configuration is not treated as another organisation's context.

Access controls, organisation identifiers and server-side validation are used throughout the platform rather than relying on the language model to decide isolation.

No. Actions are deliberately exposed through approved tools and enabled capabilities. The agent does not automatically receive unrestricted access to your systems.

This separation allows conversation and interpretation to remain flexible while important operational actions can still be controlled by defined application logic, permissions and business rules.

A tool is a controlled function the agent can use when an action is required. A scheduling tool might check availability or create a booking. Another tool might retrieve approved information from a connected business system.

Tools are separate from normal conversation so the system can control which actions exist, which organisations can use them and where they are available.

MyOpsAgent is modular. Not every business requirement needs to exist as a standard feature before it can be considered.

If you have a repetitive process, existing system or operational bottleneck, we can look at whether an additional module, tool or integration would be a sensible way to support it.

Your MyOpsAgent account determines which modules and capabilities are active for your organisation. Payment processing can be handled through Stripe, while MyOpsAgent retains the organisation's subscription and entitlement state used by the application.

If something you expect to have access to is unavailable, ask MyOpsAgent to help identify the issue or connect you with us.

Useful checks include:

• The organisation is active and correctly configured.
• The website domain matches the domain authorised for the organisation.
• The widget is using the correct organisation connection details.
• The required module and capability are enabled.
• The browser is not blocking the request because of an origin or network issue.