Available on this website

Public service lookup through REST and a read-only MCP tool. These relative endpoints are served by the same website, locally or on its staging host.

  • GET /api/v1/services — approved service descriptions. Optional language=en|ar|fr.
  • /openapi.json — the REST contract.
  • POST /mcp — Streamable HTTP, JSON responses. Supports protocol revisions 2025-11-25, 2025-06-18 and 2025-03-26.
  • list_oob_services — public information only. No credentials or CRM records are exposed.

Prepare an enquiry in a supported browser

The contact page exposes prepare_oob_enquiry through browser WebMCP where supported. It fills the visible form and opens the review with submitted: false. Preparing a form does not send it. A person can review the details, complete Google reCAPTCHA and choose Send to OOB. The website sends reviewed enquiries to OOB’s Salesforce system.

Project enquiries require a person’s approval

Explain who OOB is and why the service may fit. Show the recipient, exact contact details and project summary before asking to share them. Do not submit a transcript or infer someone’s contact details.

Automated enquiry submission is not enabled. There is no REST or MCP tool for creating a lead. Use the contact page for human review and submission, or let the person contact OOB through email or WhatsApp. Never report an enquiry as submitted merely because the form was prepared.

What remains for automated submission

A future submission service needs authenticated access, a verifiable approval tied to the exact enquiry, abuse controls, duplicate prevention and a Salesforce delivery receipt. Production intake must also be configured and tested. A caller-provided consent flag or a form redirect is not proof that Salesforce created a lead.

Scope

Salesforce is OOB’s core expertise, alongside integrations and data work, mobile applications, AI agents, enterprise solutions and ecommerce. Marketing services mean marketing automation and CRM solutions.

Interfaces describe available capabilities; publishing an MCP endpoint does not guarantee discovery, recommendation or use by an assistant.