How you can let Claude read the GoMeddo docs for you

Here's something I regularly hear: "I know the answer is somewhere in your docs. I just can't find it."

You're setting up Zoom for your reservations. You find the overview page, then the install page, then a page about authentication. Twenty minutes later you have six tabs open and you're still not sure which permission set your users need.

Our documentation covers hundreds of pages across GoMeddo, Payments, Frontend Builder, Floorplan and all our integrations. That depth is useful. Navigating it isn't always easy. So we made it easy for an AI assistant like Claude to do the navigating for you.

‍

A Table of Contents Built for AI

‍

Both documentation sites now publish an llms.txt file. Think of it as a table of contents written for an AI instead of a person.

• GoMeddo: documentation.gomeddo.com/llms.txt
• GoTallo: documentation.gotallo.com/llms.txt

The index lists every page with its title and a link to a plain Markdown version. Add .md to a page URL and you get the same content without menus, scripts or layout. That's exactly what a language model reads best.

The result: the assistant doesn't have to crawl the site or guess. It reads the index, picks the pages that match your question, reads those pages and answers from them.
‍

The Prompt: Copy, Paste, Ask

‍

An index alone isn't enough. You also want the assistant to use it properly: read the docs before answering, admit when something isn't covered, and show you where it got its answer. This prompt does that.
‍

Prompt

You are helping me configure and troubleshoot GoMeddo and/or GoTallo in Salesforce.
Answer using the official public documentation, not memory.

**Documentation indexes**
- GoMeddo: https://documentation.gomeddo.com/llms.txt
- GoTallo: https://documentation.gotallo.com/llms.txt

Each index lists every documentation page with a title and a link to a Markdown version (ending in `.md`).

How to answer

1. Fetch the relevant index and pick the pages whose titles best match my question.
  GoMeddo sections: core GoMeddo (`/gmd`), Payments (`/pay`), Subscription Management (`/sub`), Floorplan (`/fp`), Frontend Builder (`/fb`), Integration & Widget (`/widg`), Google Calendar (`/ggci`), Outlook (`/goi`), Teams (`/gti`), Zoom (`/gzi`), Agentforce (`/gcp`).
2. Fetch those `.md` pages and read them before answering. If the first pages don't fully answer the question, fetch more.
3. Base your answer on what the pages say. If the docs don't cover something, say so plainly rather than guessing, and suggest contacting GoMeddo support.
4. **Always cite your sources.** For each page you relied on, link the normal web version: the same URL with `.md` removed (e.g. https://documentation.gomeddo.com/gzi/set-up-zoom-app).
5. Give setup steps in order, using the exact Salesforce menu paths, field names and permission set names from the docs.

‍

A few choices are deliberate. "Not memory" matters because a model's training data may describe an older GoMeddo version. The section list helps it pick the right part of the docs fast. And the citation rule means you can always click through and check.

‍

Where to Use It

‍

The prompt works with any assistant that can fetch web pages. A few ways to set it up:

• Claude.ai: create a Project, paste the prompt into its instructions, and make sure web search is enabled. Every chat in that project now starts from the docs.
• Claude Code: save it as a skill or in your project's CLAUDE.md. Fetching works out of the box, which is handy when you're building flows or Apex next to your config.
• Other assistants: ChatGPT or Copilot work too, as long as browsing is switched on. Paste the prompt at the start of the conversation or into custom instructions.

Then just ask your question the way you'd ask a colleague:

How do I connect our meeting rooms to Outlook calendars so bookings sync both ways?

The assistant opens the Outlook section, reads the authentication, field mapping and sync pages, and gives you the steps in order, with a link to each page it used.

‍

What This Isn't

‍

Let's be clear about the limits. The assistant isn't configuring your org, and it doesn't know how your org is set up. It reads the same pages you could read, faster, and summarizes them for your question.

Three things to keep in mind:

• Web fetch must be on. Without it, the assistant falls back on memory, which is exactly what the prompt tries to avoid. In Claude.ai, enable web search for the chat or project.
• Mention your package version. The docs describe the current release. If you're on an older version, say so in your question so the assistant can flag differences.
• Public docs only. Internal knowledge and roadmap details aren't included. If the docs don't cover your scenario, the assistant should tell you, and that's the moment to contact us.

And always click through on the cited pages before you change a production org. The links are there for a reason.

‍

Getting Started

‍

1. Turn on web search or fetch in your AI assistant
2. Paste the prompt into a Claude Project, your CLAUDE.md, or the start of a chat
3. Ask a setup question you'd normally answer by digging through the docs

That's it. No integration, no setup in your org, just a faster way to find an answer that was already in the GoMeddo or GoTallo documentation.

‍

If the docs leave a gap, reach out to your GoMeddo contact. We'd love to hear which questions it can't answer yet.

‍