> For the complete documentation index, see [llms.txt](https://help.getmobly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getmobly.com/help-center/account-and-team/organization-profile.md). # Organization Profile Your **Organization Profile** is where you tell Mobly what your company is, what kind of leads you're chasing, and what kind of events tend to work for you. Two AI-powered features read from this profile, so the more accurate it is, the better they get: * **Scout** uses it to recommend industry events that match your audience and goals * **Lead scoring (ICP Fit)** uses it to score each lead's company against your ideal-customer profile \* This article is only relevant to Mobly Admins (with access to the Hub) \* ## When to fill it in * **At onboarding** — most orgs spend 10 minutes here on day one so Scout and lead scoring have something to chew on * **When your go-to-market shifts** — new product, new target persona, new industry focus — refresh the profile so the recommendations track with your strategy * **Quarterly check-in** — review whether the profile still reflects what your team's actually selling If Scout's recommendations look generic, or ICP scoring looks off, this is the first page to check. ## Finding it In the Hub, go to **Settings → Organization Profile**. ## What's in the profile A single form with the following fields. Most are required to get Scout and ICP scoring working well; a few are optional positive/negative signals. **Identity** * **Company Name** * **Industry / Sector** — the primary industry you sell into * **Company Size** — the typical buyer size band you target * **Primary Goal at Events** — lead generation, brand awareness, partnerships, etc. * **Annual Event Budget** **Target audience (chips lists — type and press enter to add each item)** * **Target Job Titles / Personas** — the buyer titles you're trying to reach (e.g., VP Marketing, CTO) * **Key Topics & Themes** — subject-matter areas that matter to your team (e.g., AI/ML, Cloud, DevOps) * **Industries You Sell Into** — the verticals you target **Event history & preferences (chips lists)** * **Events You've Attended Successfully** — positive signal for Scout's recommender * **Events That Weren't a Good Fit** — negative signal * **Categories to Avoid** — industries or event types Scout should skip entirely ## AI auto-fill You don't have to type everything by hand. Two AI shortcuts: * **Auto-Fill from URL** — give the AI your company website URL and it drafts a profile from your public content. Review and edit before saving. * **Let AI Fill This For Me** (per-field) — a button next to each field that drafts a value using the surrounding context. **Undo AI Fill** restores the previous value if you don't like the suggestion. The AI is a starting point, not a substitute for judgment. Always review what it generates — especially the chips lists — before saving. ## Saving The page has explicit **Save** and **Cancel** buttons (no save-on-blur). Hit Save to commit. The next Scout chat or ICP-fit scoring pass uses the updated values immediately. ## Related articles * [How to find new events to go to](/help-center/scout/how-to-find-new-events.md) — Scout, which reads from this profile --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.getmobly.com/help-center/account-and-team/organization-profile.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.