# How to answer a LettrLabs question (/agent/routing) ## Who reads this page [#who-reads-this-page] An AI agent reads this page before it answers a question about the LettrLabs app. The sidebar does not show the page. Search, `llms.txt`, `llms-full.txt` and the `.md` export include it. ## Which page answers which question [#which-page-answers-which-question] The table maps each question type to the pages that answer it. Use the first page that matches. | The customer asks | Read first | Then read | | ------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------- | | "How do I ...?" for a task in the app | The feature page of that task. Each task is an H2 section of its page. | The [Glossary](/getting-started/glossary), for the terms | | "Where do I start?" or "What can I do with LettrLabs?" | The [Help home](/) and its journeys | [Send your first mail](/journeys/send-your-first-mail) | | A question about a charge, the balance or a payment | [Payment methods](/account/billing/payment-methods) and [Plan, balance and billing](/account/billing/plan-and-balance) | The charging rules page (planned) | | "Why did my campaign not mail?" | The FAQ of [Automated campaigns](/sending-mail/automated-campaigns) or [Campaigns](/sending-mail/campaigns) | The campaign statuses table of [Campaigns](/sending-mail/campaigns) | | A question about ServiceTitan, AccuLynx, Salesforce, Klaviyo, Shopify or Zapier | The page of that product in the Integrations group, for example [ServiceTitan](/integrations/native-integrations/servicetitan) | [How integrations work](/integrations/how-integrations-work) | | "Can I do X?" for a feature the customer cannot find | [What is not available yet](/agent/not-available-yet) | Plans and features (planned) | | An error message | The FAQ of the feature page that quotes the error text. Each FAQ answer has its own link. | The error and validation messages page (planned) | | "Connect my AI assistant" | [Connect LettrLabs to Claude](/getting-started/ai-assistants/claude), or [Connect LettrLabs to ChatGPT](/getting-started/ai-assistants/chatgpt) | [MCP server](/mcp) | | A question about the API, webhooks or code | The [Developers](/) tab | The [API Reference](/api-reference) | ## Rules for the answer [#rules-for-the-answer] * Use the names of the new app: campaign, template, Address Book, service area. The [Glossary](/getting-started/glossary) maps old names to new names. * Give the steps as a numbered list, with the UI labels in bold, as the guide writes them. * Link the guide you used. Use the full URL on `https://docs.lettrlabs.com`. * Give a charge, a data-loss or a cannot-undo condition before the step it applies to. * When a page has `status: blocked`, say that the task has a known problem. Tell the customer to contact support. * When no page answers the question, say so. Do not guess a UI label or a price. Offer to send the question to support. ## Facts that change often [#facts-that-change-often] Read these facts from their pages each time. Do not keep them from an earlier answer. * Prices, postage and production times. * The list of features that are not available yet. * The MCP tools. The MCP server is in public beta.