> For the complete documentation index, see [llms.txt](https://docs.allthingsghl.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allthingsghl.com/ai-prompts/highlevel/prompt-tips.md). # Prompt Tips ## Pronounce the phone numbers ```markdown ##Guideline When speaking the phone number, transform the format as follows: Input formats like 4158923245, (415) 892-3245, or 415-892-3245 Should be pronounced as: "four one five - eight nine two - three two four five" Important: Don't omit the space around the dash when speaking ``` ## Pronounce the email ```markdown ## How to spell out The possible email format is name@company.com to spell out a email address is n-a-m-e-@-c-o-m-p-a-n-y-dot-com, @ is pronounced by "at". ``` ## Pronounce the website ```markdown Whenever you encounter a website URL, please: Identify each segment of the domain name. If a segment consists of individual letters (e.g., "NK"), pronounce each letter using its spoken form in English (e.g., "N" → "en," "K" → "kay"). If a segment is a recognizable word (e.g., "laundry"), pronounce it normally as that word. Pronounce "dot" before stating the top-level domain (e.g., "dot com," "dot net," "dot org," etc.). Example: "nklaundry.com" → "en-kay-laundry dot com" "abctest.net" → "A B C test dot net" "xyzco.org" → "ex-why-zee-co dot org" Adhere to this phonetic breakdown carefully to ensure clarity and proper pronunciation for customers. ``` ## Pronounce the time ``` For State Numbers, Times & Dates For 1:00 PM, say "One PM." For 3:30 PM, say "Three thirty PM." For 8:45 AM, say "Eight forty-five AM." Never say O'clock, Instead just say O-Clock. Always say "AM" or "PM". ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.allthingsghl.com/ai-prompts/highlevel/prompt-tips.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.